I have a RPI B+ with Astroprint flash – when I try to connect to printer, it connects and then promptly disconnects. I have tried different usb cables and usb slots. The camera feed works and connecting to the internet works, just can’t get it to maintain connection to our Lulzbot Taz 5. Any ideas? Thanks
Just saw the other post about insufficient current on the power supply. Mine is 2A at 5 volts so that should be enough?
Could you follow the instructions here: https://astroprint.zendesk.com/hc/en-us/articles/203828935-Debug-Serial-Connection-to-Printer
and provide us with a serial log using our support system at: https://astroprint.zendesk.com
Did you try to connect with just the pi connected to the printer, No other usb peripherals connected? Did you try connecting a powered USB hub to your Pi and then plugging your printer into the hub? If your power is the problem, a multimeter and 3 minutes of your time you can find out. google raspberry pi tp1 tp2 test. There are test procedures for checking voltage. Does the Taz connect fine to other computers? If that isnt the problem you need to view the astroprint logs. They are contained within /var/log/astrobox
Thanks for you quick response. I have tied various usb connections and sequence as you suggested. No change. The Taz works fine when connected to my Mac using Simplify3D.
I will have to try volt meter tomorrow but I did record the serial.log. It just tries to connect:
pi@astrobox-Lumenium /var/log/astrobox $ head serial.log -n200
2015-04-15 04:41:31,134 - SERIAL - DEBUG - Enabling serial logging
2015-04-15 04:42:21,197 - SERIAL - DEBUG - Changing monitoring state from ‘Offline’ to ‘Opening serial port’
2015-04-15 04:42:21,207 - SERIAL - DEBUG - Connecting to: /dev/ttyACM0
2015-04-15 04:42:21,230 - SERIAL - DEBUG - Connected to: Serial<id=0x1cbbd70, open=True>(port=’/dev/ttyACM0’, baudrate=115200, bytesize=8, parity=‘N’, stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2015-04-15 04:42:21,233 - SERIAL - DEBUG - Changing monitoring state from ‘Opening serial port’ to ‘Connecting’
2015-04-15 04:42:23,262 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:25,268 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:27,274 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:29,280 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:31,287 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:33,293 - SERIAL - DEBUG - Send: M105
2015-04-15 04:42:35,299 - SERIAL - DEBUG - Send: M105
There’s no response from the printer. Have you tried different baud rates?
Got it working – it was a silly stupid fix! Not sure why this is the case, but simply removing the SD Card from my Taz 5 allowed the Astrobox to connect and stay connected.
Background: I tried several 2 amp plus supplies, camera connected / not connected and RJ45 or Lan stick. Non of those made a difference. Just remove the SD card. This is kinda bizarre since I can run jobs from my laptop direct connected with the SD card in. But a small price for remote printing!
A clue for you Daniel!
In order to connect at power up, the SD must be removed. But after it connects the SD card can inserted without any issues. It seems that the first connection is the issue.
I’m having a similar issue with my Taz 4 after upgrading it to Taz 5 firmware.
When I connect via picocom from the astrobox (after doing service astrobox stop) I get the following output:
Terminal ready
start
echo:Marlin 1.0.0
echo: Last Updated: Jul 11 2015 21:18:00 | Author: (Aleph Objects, Inc, TAZ config)
Compiled: Jul 11 2015
echo: Free Memory: 3332 PlannerBufferBytes: 1296
echo:Hardcoded Default Settings Loaded
Then, there is a pause of about 2-5 seconds, the case fan in the Taz spins up and spins down, and then I get:
echo:SD init fail
At this point, I can sent G-Code commands manually and the M105 command works:
M105
ok T:24.1 /0.0 B:21.3 /0.0 T0:24.1 /0.0 @:0 B@:0
After turning on serial logging, I re-enabled astroprint with “service astrobox start”, and what the serial log shows is:
2015-07-12 17:34:21,056 - SERIAL - DEBUG - Enabling serial logging
2015-07-12 17:34:24,910 - SERIAL - DEBUG - Changing monitoring state from 'Offli
ne' to 'Opening serial port'
2015-07-12 17:34:24,913 - SERIAL - DEBUG - Connecting to: /dev/ttyACM0
2015-07-12 17:34:24,918 - SERIAL - DEBUG - Connected to: Serial<id=0x244eab0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2015-07-12 17:34:24,919 - SERIAL - DEBUG - Changing monitoring state from 'Opening serial port' to 'Connecting'
2015-07-12 17:34:25,972 - SERIAL - DEBUG - Recv: start
2015-07-12 17:34:25,974 - SERIAL - DEBUG - Recv: echo:Marlin 1.0.0
2015-07-12 17:34:25,982 - SERIAL - DEBUG - Recv: echo: Last Updated: Jul 11 2015 21:18:00 | Author: (Aleph Objects, Inc, TAZ config)
2015-07-12 17:34:25,984 - SERIAL - DEBUG - Recv: Compiled: Jul 11 2015
2015-07-12 17:34:25,989 - SERIAL - DEBUG - Recv: echo: Free Memory: 3332 PlannerBufferBytes: 1296
2015-07-12 17:34:25,992 - SERIAL - DEBUG - Recv: echo:Hardcoded Default Settings Loaded
2015-07-12 17:34:27,995 - SERIAL - DEBUG - Send: M105
2015-07-12 17:34:29,998 - SERIAL - DEBUG - Send: M105
2015-07-12 17:34:32,005 - SERIAL - DEBUG - Send: M105
2015-07-12 17:34:32,777 - SERIAL - DEBUG - Recv: echo:SD init fail
2015-07-12 17:34:32,780 - SERIAL - DEBUG - Changing monitoring state from 'Connecting' to 'Closed'
2015-07-12 17:34:32,781 - SERIAL - DEBUG - Connection closed, closing down monitor
Is is possible that astroprint is sending the M105 before the firmware fully boots (e.g. before the SD slot completes whatever takes 2-5 seconds) and then sees the SD initialization message as the response to M105 and shuts down?
I’m not sure, however, why the firmware update precipitated this change, since from what I can tell, none of the SD or LCD related hardware or configuration changed.
I made a quick change to Marlin to remove the SD init failure log message (I couldn’t disable the SD initialization altogether since that seems closely tied to the whole implementation of the LCD panel).
This seems to have worked-around the connection problem and my Astrobox can now consistently connect to my printer.
The serial.log output now looks like:
2015-07-12 18:06:22,967 - SERIAL - DEBUG - Enabling serial logging
2015-07-12 18:06:29,172 - SERIAL - DEBUG - Changing monitoring state from 'Offline' to 'Opening serial port'
2015-07-12 18:06:29,176 - SERIAL - DEBUG - Connecting to: /dev/ttyACM0
2015-07-12 18:06:29,193 - SERIAL - DEBUG - Connected to: Serial<id=0x30a9ab0, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2015-07-12 18:06:29,195 - SERIAL - DEBUG - Changing monitoring state from 'Opening serial port' to 'Connecting'
2015-07-12 18:06:30,236 - SERIAL - DEBUG - Recv: start
2015-07-12 18:06:30,238 - SERIAL - DEBUG - Recv: echo:Marlin 1.0.0
2015-07-12 18:06:30,245 - SERIAL - DEBUG - Recv: echo: Last Updated: Jul 12 2015 11:00:40 | Author: (Aleph Objects, Inc, TAZ config)
2015-07-12 18:06:30,247 - SERIAL - DEBUG - Recv: Compiled: Jul 12 2015
2015-07-12 18:06:30,251 - SERIAL - DEBUG - Recv: echo: Free Memory: 3332 PlannerBufferBytes: 1296
2015-07-12 18:06:30,254 - SERIAL - DEBUG - Recv: echo:Hardcoded Default Settings Loaded
2015-07-12 18:06:32,257 - SERIAL - DEBUG - Send: M105
2015-07-12 18:06:34,261 - SERIAL - DEBUG - Send: M105
2015-07-12 18:06:36,265 - SERIAL - DEBUG - Send: M105
2015-07-12 18:06:37,041 - SERIAL - DEBUG - Recv: ok T:0.0 /0.0 B:0.0 /0.0 T0:0.0 /0.0 @:0 B@:0
2015-07-12 18:06:37,043 - SERIAL - DEBUG - Changing monitoring state from 'Connecting' to 'Operational'
There’s still a nearly 5 second delay between when the first M105 is sent and when the response comes back due to the delay in SD initialization, but since there’s no error message, the astrobox seems okay with it.
1 Like