Bluetooth loopback test already active

Что такое Loopback Test(s)?

Есть проблемы с интернетом (упала скорость в 10 раз). Провёл тесты интеловским драйвером и есть вот такая ошибка. Что она означает? Что такое Loopback Test(s)?

Это ошибка означает, что для теста адаптера (который скорее всего совсем ни при чём), нужно сделать специальный loopback кабель, который и вставить в коннектор тестируемой карточки.
(отсюда, но в других местах тоже есть разводка https://www.juniper.net/documentation/en_US/junos/.
Если есть проблемы с интернетом, то вызывайте провайдера на разбор полетов.

Спасибо за ответ!
В ТП звонил. Там товарищ изменил с их стороны режим «авто» на принудительные 100 мегабит и интернет пропал. Из чего был сделан вывод, что проблемы у меня. Мол больше 10-и мегабит не пропускает именно моё железо.
Что в принципе возможно, как я понимаю (прошарил сеть, такая проблема нередко бывает). И к несчастью, нет возможности проверить (подключить другой провод или другую сетевую).
Со своей стороны я пытался делать тоже самое (ставить 100 принудительно). Результат аналогичный.

noob, так, у вас проблема со скоростью соединения? Или проблема с интернет скоростью?
Если выключаете автоопределение скорости, то желательно принудительно выставлять скорость с двух концов, на плате и на коммутаторе. Причем дуплекс/полудуплекс должны быть в одинаковых значениях.
Еще, многие провайдеры не придерживаются правила 100 метров кабеля, если он длиннее, или есть скрутки и удлиннители, то эффект будет похожий. Также будет влиять качество обжима коннекторов. И чем длиннее кабель, тем сильнее проявляются все дефекты.
Ну и как минимум погут подгореть порты на коммутаторе, в этом случае хоть объизменяйся, только принудительно в другой порт вставлять.

Из своего богатого опыта скажу вот такую последовательность
1) качество обжима 60%
2) качество линии 30%
3) подгорел порт у провайдера 8%
4) виновата карточка 2%

Источник

SCO loopback in bluetooth [closed]

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Description: I have a small in-house device with bluetooth capabilities. At the moment , other devices connect to that box. we play music in our box and via bluetooth we stream it on connected devices. we use » aplay -D btheadset » command to play music. Requirement:
I want to know what i sco loopback? and how to check if my bluetooth supports it? My investigation:
what I know is that we can stream music either via SCO link or ACL. how would i make sure its SCO? I havnt got any idea related to loopback. Additional Information: The application uses Bluez libraires to send command to firmware/hardware and we extensively use HCItool. Operating system : Fedora. Any help will be beneficial to us. Thanks

1 Answer 1

SCO stands for Synchronous Connection Oriented. An SCO link was primarily designed for audio, and provides dedicated time slots for packets to arrive. This is what makes it suitable for audio (Remember — BT is packet based transmission).

SCO Loopback is, for want of a better description, a device playing audio to itself. By it’s very nature, I doubt that this would be possible. I think, however, what you want is an SCO link.

Now, when a device initiates an SCO connection with another, it must first initiate the connection by sending ACL packets. This is to make both devices aware of each other.

ACL is master-slave oriented. This means that neither device expects a packet in any particular frame.

Now, as for ensuring play in SCO mode:
This is very likely already the case. Now that we are using higher quality audio, BT devices have become very dependant on a constant stream of packets at regular intervals. An SCO link is a good way of ensuring this.

Edit: This is a test for SCO. Any devices that don’t support it will be skipped.
Edit2: In Fedora, disable SCO links support (CONFIG_BT_SCO) (I’m sorry, I don’t know the parameter in Fedora to disable) and see if your working device now fails.

As for passing audio files to and from the device, is the device capable of playing it’s own audio? If so, mount it as a USB device (Remember, Bluetooth uses the USB bus(I think))

Emerge or apt-get bluez-utils and obexfs. Should pull all the other libs as dependencies.

modify /etc/bluetooth/hcid.conf like so

# modprobe fuse # modprobe bluetooth # modprobe ehci-hcd # modprobe uhci-hcd # modprobe hci_usb # modprobe l2cap # modprobe rfcomm 

Activate BT, start, and get the MAC of the device

# echo enable >/proc/acpi/ibm/bluetooth # /etc/init.d/bluetooth start # hcitool scan 

# mkdir /mnt/player # mount -t fuse "obexfs#-b -B6" /mnt/player 

If you want a more user-friendly interface, try launching
kbtobexclient
And in the Location put
obex://[00:01:02:03:04:05]

I hope this meets your requirements.

Источник

Bluetooth Telemetry radio¶

` A Bluetooth Data Link , such as an HC-06 module can be used to connect your Pixhawk (or other controller) to your Bluetooth enabled PC or Android Ground station at distances up to 50m.

Connecting to the Autopilot¶

The Bluetooth data link comes with both a DF13 6 pin and 6-to-5 pin connector which make it easy to connect to the Pixhawk Telem1 or APM2.x’s Telem ports. Note that for the Pixhawk, although Telem1 is the recommendation, Telem2 or even Serial 4/5 will work.

Once you have connected the Bluetooth data link you can power up the board. It is OK to use USB connected power while using the Bluetooth module connected to the autopilot as the USB connection can supply enough power BUT YOU MUST USE A WALL WART with Micro or Mini USB).

Bluetooth data link’s LEDs:

• Red LED blinks at 1hz : device is working, not connected
• Red LED blinks at 0.5z : pairing
• Red LED solid : connected

Quick Start connecting with Mission Planner¶

If you are familiar with Bluetooth, search for Bluetooth Device HC-05 or 6 (some may have Linvor as well) , Pair with device (code 1234 or 0000) check it’s properties and look at the services tab. Make sure SPP com port box is checked (only there if your Bluetooth device is active) Look in Device Manager (Windows) and make sure there is a Com Port for the Bluetooth and in the com port properties set the baud rate to 57600 (note the Com Port number).

For use with Mission Planner on the Configure/Tuning tab make sure and UNCHECK the box Reset on USB Connect:

The default Baud Rate for the Bluetooth Module is 57600 (most other modules are 9600) Be sure when you connect it is at 57600 and for the new Com Port you saw in Device Manager.

When you power up the PixHawk or APM with the Bluetooth the module will flash at 1hz the red LED when not connected. When Paring it will flash at .5 Hz and when connected it will be steady on.

And you’re done! You can now use your Bluetooth telemetry for up to about 50m range. (your range may vary depending on back ground noise and conditions in your area)

If you have problems connecting or you don’t know Bluetooth very well or you want to change the default Baud Rate or Device Name, read on for the step by step process.

Detailed connecting with Mission Planner¶

Many PCs and Laptops have bluetooth adapters built in but if not then you can use a generic USB Bluetooth dongle (pic above) or use an additional Bluetooth data link connected via an FTDI Cable.

After first making sure your autopilot is powered on, and your PC’s bluetooth dongle is plugged in and installed, click on the Windows task bar’s little up triangle (aka “show hidden icons”) which should be on the bottom right of the screen.

The “hidden icons box” should appear. Right-mouse-button-click on the BlueTooth icon and select “show Bluetooth devices”

Windows should bring up the devices box. Any devices you may already have connected by Bluetooth will be in this box. If you have not connected any BT devices before this box will be empty. Select “Add a device”.

Windows will search for BT devices for you. If you have any BT devices turned on they will show up here (like perhaps your cell phone) ignore any other devices and select the HC-05 or HC-06 (or Linvor) .

Select Paring using device code.

Enter the device code (1234 or 0000) this is the default code.

Once paired right click the device and select “properties” The check box for Comm Port SPP should be checked (also note the com port number).

In device manager select Com Ports

Choose the comm port you noted in the above step.

Right click and select “properties”

Change baud rate to 57600

Once again start Mission Planner and go to the Configure/Tuning tab and make sure you UNCHECK the box “Reset on USB connect”

Your Bluetooth device should now be ready and you can connect to the proper port at the proper baud rate of 57600 (red LED steady on and not flashing)

Connecting From your Android ground station¶

These instructions will show you how to connect to your vehicle from AndroPilot or DroidPlanner 2 running on NExus 7 tablet using the Bluetooth module.

Open the Android device’s settings application and turn Bluetooth connectivity ON (usually by sliding a slider to the right). In the same settings screen click on “Bluetooth” which should cause a list of AVAILABLE DEVICES to appear

Power the vehicle and the “HC-06” device should appear. Click on it and enter “1234” or “0000” as the PIN to pair with the device, then select OK.

The device will appear under “PAIRED DEVICES”

• open the Droid Planner settings, and select Telemetry Connection Type, Bluetooth.
• In the main DroidPlanner interface, select Connect, and select the paired Bluetooth device.

When live data appears on the screen, you’re ready to start mission planning.

How to Change Baud Rate, Device Name and Device PIN¶

You will need a FTDI to USB cable to change any of the configurations of the device (not supplied) It is not necessary to change anything in order for your BT device to function properly it will function quite well as supplied. This is for reference and your convenience only!

To change the above you need a “Terminal” emulator program. You can not use “Putty” (a popular serial port tool) because it will not accept “line” commands. The Bluetooth Modules read the input at a rate of once per second therefore you must use an emulator that will allow you to input an entire line before hitting “send”. You can use the Arduino IDE to send commands to the com port if you are familiar with that. I use “Advanced Serial Port Terminal” but any terminal emulator that allows you to type in a line of text before hitting send will work just a good.

Change the baud rate¶

The index after the command AT+BAUD corresponds to the following baud rate:

There are additional baud rates. Warning! do not set these baud rates unless you have a special fast UART chip. If you don’t know do not use these rates they are beyond the standard PC UART speed and once set you will loose communication with the device and the only way to contact the device after that will be with a high speed UART. (these are for reference only)

The change of Baud rate takes effect immediately after the command is sent. So if you want to keep configuring the Bluetooth module, you need to set the Baud rate of your terminal program to the new Baud rate the Bluetooth is using. To test it, send AT again, you should receive ‘OK’

Change the Device Name¶

This example show you how to change the name of the Bluetooth module to ArduPilot: In the terminal program, send the command (case sensitive):

The Bluetooth should reply:

Change the Device PIN¶

The following example shows how to change the pairing code to 5566 In the terminal program, send the command (case sensitive):

The Bluetooth should reply:

Troubleshooting¶

You can test the device by making a loopback from TX to RX.

Open your terminal program select the correct comm port and in terminal type anything you like. If you see the test displayed then your device is working properly. If you do not see the text you typed and you have selected the correct comm port and your device is paired and connected (red LED solid on not flashing) then you may have a problem with your device.

Specs¶

Dimensions : 1.4” x 0.6” x 0.17”

Operation voltage: 3.6 to 6 V

Typical -80dBm sensitivity

Up to +4dBm RF transmit power

UART interface with programmable baud rate

Supported baud rates: 1200, 2400, 4800, 9600, 19200,38400, 57600, 115200, 230400, 460800

Pairing code: 1234 or 0000

Auto-connect to the last device on power as default

Permit pairing device to connect as default

Questions, issues, and suggestions about this page can be raised on the forums. Issues and suggestions may be posted on the forums or the Github Issue Tracker.

© Copyright 2023, ArduPilot Dev Team.

Источник