Error in Reach Crash log

Reach Module / M+ / M2 Hardware integration
1

My Reach rover has been acting up, so I decided to ssh in and see what it might be telling me. It has been intermittently disconnecting from my Pi (its connected via USB). I’m seeing this, any thoughts? :

Jun 04 15:02:26 reach systemd[1]: Starting Emlid Reach setup...
Jun 04 15:02:27 reach systemd[1]: Started Emlid Reach setup.
Jun 04 15:02:30 reach reach_setup[250]: u-blox:true,mpu:true,ltc:false,stc:false,lora:false
Jun 04 15:02:30 reach reach_setup[250]: Reach
Jun 04 15:02:37 reach reach_setup[250]: Network mode: client
Jun 04 15:02:43 reach reach_setup[250]: [Errno 2] ENOENT
Jun 04 15:02:46 reach reach_setup[250]: (646) wsgi starting up on http://0.0.0.0:5000
Jun 04 15:02:49 reach reach_setup[250]: (651) wsgi starting up on http://0.0.0.0:80
Jun 04 15:02:55 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54493)
Jun 04 15:02:55 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54494)
Jun 04 15:02:55 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54495)
Jun 04 15:02:56 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54497)
Jun 04 15:02:57 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54498)
Jun 04 15:02:57 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54499)
Jun 04 15:02:57 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54500)
Jun 04 15:05:04 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54529)
Jun 04 15:05:04 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54530)
Jun 04 15:05:04 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54531)
Jun 04 15:05:06 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54533)
Jun 04 15:05:07 reach reach_setup[250]: (651) accepted ('192.168.1.68', 54534)
Jun 04 15:05:07 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:07 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:07 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:08 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:08 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:08 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:08 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored
Jun 04 15:05:08 reach reach_setup[250]: Exception AttributeError: AttributeError("'_DummyThread' object has no attribute '_Thread__block'",) in <module 'threading' from '/usr/lib/python2.7/threading.pyc'> ignored

It also looks like an error is being generated on the pi side, this is from dmesg:
[ 7495.461522] cdc_ether 1-1.5:2.0 usb0: unregister ‘cdc_ether’ usb-3f980000.usb-1.5, CDC Ethernet Device
[ 7495.506149] cdc_acm 1-1.5:2.2: failed to set dtr/rts
[ 7496.974992] usb 1-1.5: new high-speed USB device number 76 using dwc_otg

2

Anyone?

Basically, I’ve got my reach hooked to Navio2 over USB-to-PC, the serial port keeps disappearing after a few seconds and reappearing with another name. It doesn’t even stay connected long enough for APM Planner to see it as a second GPS. I am NOT embedding the corrections in telemetry with Mission Planner, just tryign to get my setup to see it as a second GPS currently.

4

Hello Bill,

Is there a chance your setup does not provide enough power for Reach and it reboots from time to time?

This might be related to a USB-Ethernet connection and not the disappearing USB-serial device. Would you mind posting a more complete dmesg log?

5

I’m powering it from my Pi3 so it looks like it should have enough power. I’ve isolated the USB bus to only my reach with no change. I’ll try and grab some more logs this weekend.

In the short term, I’ve hooked it up via uart which is not ideal since I use telemetry radios and NOT missionplanner. I also picked up a UART to USB so I’ll see if that changes anything. Worst case, I can stick my telemetry on USB instead I suppose.

6

If the led goes back to magenta from time to time, then it’s a power issue. Rather than a connector issue it’s probably related to your PI’s power source. Are you able to get a stable stream of position data?

Although sometimes USB-Ethernet link is not always stable with a Linux host, we’ve never experienced anything with a USB-Serial connection.