SBC loses network connection, alot!
-
Hey guys,
This is really pissing me off. The SBC, which is directly connected to the 6HC controller, keeps losing connection. Which means, I lose the ability to interact with the print completely!
I don't understand how something that is directly connected can lose connection. This keeps happening more and more, and is now a major issue. The SBC is connected to it's own power supply, which is plugged into the wall. So power should not be an issue.Also the voltage on the controller is 24.4, so no power issues there either.
I there anyway to restart the sbc while the print is running? Is there anyway I can connect a real PC to the controller? These sbc's suck and are really slow and unreliable anyway. (not to mention, hard to get these days)
Below is my config:
-
@Jered have you considered running in standalone mode?
Can you post an M122 output when you see a disconnection?
Can you also post a photo of your wiring? Concentrating on the area where the ribbon cable is -
@jay_s_uk
I would post an M122, just can't due to no connection at the moment. I would need a display to run in standalone mode, which I don't have. Perfer sbc since it is really convenient and one of the feature I got this for. The only way I have to see into what this thing is doing is through the sbc.
The cable runs from the bottom left up to the top right.
-
@Jered wow, that cable is stupid long.
I think duet recommend around 150mm long.
That cables just too long for an SPI connection -
@jay_s_uk
So, no reboot during printing? Or using a more robust computer with it. Something without cable limits? -
@Jered if it's lost the connection enough that it can't recover then the prints failed.
I suggest moving the raspberry pi closer to the 6HC and using the supplied cable.
This isn't something you can fix by using a different SBC -
@Jered said in SBC loses network connection, alot!:
I would need a display to run in standalone mode,
You mean you're using an HDMI touch screen with the SBC?
@Jered said in SBC loses network connection, alot!:
keeps losing connection
What errors are you getting? Is it DWC that is losing connection?
@jay_s_uk said in SBC loses network connection, alot!:
I suggest moving the raspberry pi closer to the 6HC and using the supplied cable.
Definitely try this and see if it helps your situation. You MIGHT be able to get away with longer length if you used a shielded twisted pair cable instead of a flat ribbon, but even so, SPI isn't meant for long runs.
-
@Phaedrux
The machine is still printing even though connection has been lost for awhile now.I will look into sheilded cables and what not before moving the sbc. As you can see from the pic, moving it will not be easy as space is limited.
Are there any plans to allow the Duet controller to use regular PCs?
-
@Jered said in SBC loses network connection, alot!:
Are there any plans to allow the Duet controller to use regular PCs?
No.
I still don't know exactly what you mean by losing network connection.
Network connection sounds different than an SPI connection issue. What exactly are you seeing?
-
@Phaedrux
Attached is photo taken of the monitor that is connected directly to the sbc.
I haven't really had any problems until just recently. So this is baffling to me.
Print is still going, but I need to cancel it. Since the sbc is not responding, I will have to just power down.
-
Where is that error displayed though? On a computer browser connected to DWC or on an HDMI touch screen to the SBC?
Are you still able to ping the IP address of the SBC?
Can you reach the SBC over SSH? -
@Phaedrux
The error is displayed on the monitor connected to the hdmi port of the sbc.
Here is a zoomed out pic.
I can operate the sbc just fine. I can minimize the duet interface and operate the sbc normally, it's just that the sbc is no longer talking to the Duest controller. DWC is seems to be not connected somehow.
Not sure I need to ping anything. Also, not sure how to ping.
-
Ok, can you close the DWC interface and relaunch it?
Can you grab a log from the SBC?
https://github.com/Duet3D/DuetSoftwareFramework/wiki/SBC-Setup-Guide#increasing-log-level
-
@Phaedrux
I'll try. How to I retrieve the log? -
To obtain more data for potential debugging it is possible to adjust the log level of the DCS service. This can be done by changing LogLevel in /opt/dsf/conf/config.json from info to debug.
Once this change has been made, restart the DCS service to apply it (sudo systemctl restart duetcontrolserver). After that you can follow potential debug messages in a terminal by running journalctl -u duetcontrolserver -f.
-
@Phaedrux
I can give that a try. I am not familiar with that, but there's no time like the present.I did close the browser on the sbc and re-open it. It works now. Remoted in from my other computer and I can see it there as well. So by closing the browser on the sbc and re-opening it, I now have full control from anywhere again.
I will try the debugging thing when I get a chance.
-
@Phaedrux "You MIGHT be able to get away with longer length if you used a shielded twisted pair cable instead of a flat ribbon, but even so, SPI isn't meant for long runs."
I dont think shielding will help. The issue is increased capacitance and resistance with long wire runs and screws up the spi signal timing. The quickest check would be what others have suggested. Simply move the SBC closer to the 6HC using the original cable. If that fixes your issue no amount of shielding is going solve your problem. You will need to relocate the SBC next to the 6HC.
-
@wayneosdias In this case it doesn't seem like an SPI issue because the print continued, so the connection between SBC and Duet was still active.
Network connection error coming up in DWC is something else. Restarting DWC re-connected successfully.
-
@Phaedrux interesting. I have no experience using sbc. So the sbc acts as sender?
-
@wayneosdias Yes, but not in the sense of a traditional USB gcode sender would.
