Unable to use TWR on dwusb_gui 0.5.0.4

[mblankenship]

@hpolido2

1. The anchor, 01:00:04BD, is flashing a white light every 5 seconds. The master, that is connected to the computer, 01:00:04BE, is flashing a green light every 5 seconds. What does that mean?

Just so you know, the current release firmware (REL-0.5.0.3) has the following LED blink patterns:

1. Periodic green blink indicates that the device is off network.
2. Periodic yellow blink indicates that the device has connected to a network as an anchor.
3. Periodic purple blink indicates that the device is the master running a network.
4. Periodic blue blink indicates that the device is a tag being tracked on a network.
5. Periodic red blink or static red LED indicates that the device is malfunctioning.

The above are all the intended states of the DWUSB LED, and as such, I do not believe there is a case where the DWUSB should blink white.

However, this suggests that there’s another thing we need to check. Can you plug in your master DWUSB, then open a serial terminal (such as cutecom), and connect to the first port associated with the connected DWUSB, which in your case should be /dev/ttyACM0 (or /dev/ttyACM2)? After doing the previous steps, type in the command “get version”. At this point, the DWUSB should respond with a message saying “DWUSB FIRMWARE REL-0.5.0.3”. After you have verified that your master is running the proper version of firmware in this way, please double check your anchor as well.

@hpolido2

2. The devices are not more than 1 foot apart, sitting on my desk.

That sounds like a good setup for this testing.

@hpolido2

3. When I connect the device, it creates /dev/ttyACM0 and /dev/ttyACM1.
   Neither seems to work. (Or sometimes /dev/ttyACM2 and /dev/ttyACM3). I
   performed a full computer reboot between each test.

Just so you know, the host software always needs to communicate with the latter of the two ports associated with a DWUSB. In this case, it should be /dev/ttyACM1 (or /dev/ttyACM3) that the host software will want to use.

@hpolido2

Another observation, when I am on the “TWR” tab, and I switch back to the “Config” tab, the application might freeze, and the last terminal message is “host shutting down…”

When you say the application might freeze, do you mean it completely crashes, or that it just pauses for a few moments? It sometimes takes a couple seconds for the host software to stop a network that is in progress, which is what happens when you switch back to the “Config” tab, so it is likely that the system will pause when switching to that tab.

@hpolido2

Would you like to setup a remote desktop session to debug?

Unfortunately, it is unlikely that that would be particularly helpful. It sounds like your host software is functioning correctly, but something seems to be off with your DWUSBs, which is not something that can be adequately addressed with a remote desktop session.

If you are still unable to get your system working, you will likely have to run the system in Ubuntu 14.04. We have never had anyone try to run the system in Ubuntu 15.04. However, we had a user attempt to run the system in Ubuntu 14.10 before, and the serial port libraries available in that version of Ubuntu appeared to be unable to properly connect to our firmware. For now, the system is only supported in Ubuntu 14.04. For more information, please view the following thread: https://forum2.ciholas.com/t/does-the-dwusb-gui-run-in-windows/69.