UWB anchor LED error and picocom not connected

All discussions related to the Loco Positioning system
Post Reply
chuhao
Beginner
Posts: 27
Joined: Sat Apr 29, 2017 6:25 am

UWB anchor LED error and picocom not connected

Post by chuhao »

Hi

I have problem during flashing uwb anchor firmware.

1. LED error
DWM controlled LED: RX,SFD,RXOK are keep blinking once power on. After entered DFU mode, DWM controlled LED are all turned off, including RX.
After firmware flashed, anchor info showed as below,
nodefalsu.png
It says "anchor position enabled: false". I tried several times to reflash. There are two anchors are in this mode.

2. picocom failed sometimes
After type,

Code: Select all

sudo picocom /dev/ttyACM0
There are some certainties doesn't show any data,
nodefalsu.png
Normally, it happens within 10 seconds after power on. If wait for more than 10 seconds, anchor can be connected correct.

Thanks
Attachments
node_error.png
arnaud
Bitcraze
Posts: 2538
Joined: Tue Feb 06, 2007 12:36 pm

Re: UWB anchor LED error and picocom not connected

Post by arnaud »

Hi,

1. It looks like you have a Crazyflie or other UWB tag currently switched ON, this is why all LED are blinking. Your node is in TWR mode so if no tag is present only the RX led will blink (and will most likely continue to blink in DFU mode).

The anchor position=false means that you have not programmed an anchor position using the new loco pos tab. This is not a problem if you have compiled your Crazyflie with the anchor position hardcoded. The new tab is still in development but the latest version from the master branch should work fine to write anchor position in the anchors, this will allow you to run the system with a Crazyflie compiled dirrectly from master.

2. This is a known problem with Ubuntu: Ubuntu is trying to detect a modem (this is done by a package called modemmanager) and to do so it is automatically opening the serial port and writing AT commands to it. This usually last for about 10-20 seconds. After this time there should be no problem to access the serial port as you noted.
Post Reply