Duet 3 SBC DCS has stopped
-
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
Sounds like a good plan to me. As with any beta, exercise caution - I suggest you baby-sit the print, at least for a while.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
So last night I swapped to standalone mode completely disconnecting the pi. I was able to print the same file I had issues with. So sounds like the issue is with the communication between the Pi and the Duet 3.
I'm going to try the beta 3.2.3 with SBC and try again.
I did try to tell you a few days ago.....
Nice to be proven correct again....
It must be noted that I had the same problem on 3.1.1 firmware too
-
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
-
After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))
The error exists even after swapping back to the original 3.1.1 pi.
-
What version is on the Duet itself?
See this thread for downgrading instructions.
https://forum.duet3d.com/topic/19257/downgrade-from-3-2beta2-to-3-1-1/
-
@Phaedrux thanks. I ran
sudo wget -O /opt/dsf/sd/sys/Duet3Firmware_MB6HC.bin https://github.com/Duet3D/RepRapFirmware/releases/download/3.1.1/Duet3Firmware_MB6HC.bin sudo apt -y --allow-downgrades install duetsoftwareframework=3.1.1 duetcontrolserver=3.1.1 duetruntime=3.1.1 duetsd=1.0.6 duettools=3.1.1 duetwebcontrol=3.1.1 duetwebserver=3.1.0 reprapfirmware=3.1.1-1Unpacking duetruntime (3.1.1) over (3.2.0-beta3) ... Setting up duetruntime (3.1.1) ... Setting up duetwebcontrol (3.1.1) ... Setting up duetcontrolserver (3.1.1) ... Installing new version of config file /opt/dsf/conf/config.json ... Setting up duettools (3.1.1) ... Setting up duetwebserver (3.1.0) ... Setting up duetsd (1.0.6) ... Setting up reprapfirmware (3.1.1-1) ... [fatal] Could not connect to Duet (Board is not available (no header)) Setting up duetsoftwareframework (3.1.1) ... -
The cable is good. I used a continuity tester to check each pin from the duet board to the pi. Every pin had a connection to it's corresponding one. I'm starting to suspect there's an issue with the board
-
@dc42 any ideas? everything i've tried has failed. The board will work in standalone but the reason I bought it is for the benefits of with the SBC
-
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass
-
@CaLviNx said in Duet 3 SBC DCS has stopped:
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx Yea you're correct but why did you feel the need to say it like that? I was troubleshooting. I started focusing on the firmware side. When all options were exhausted i eliminated the Pi
I was trying to help you and save you time, instead of listening to reason you blew it off and acted like I was speaking out of my ass
How bout you save us all some time and just exit the thread please.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
After upgrading to the latest beta 3.2.3 I get the error Could not connect to duet (Board is not available (no header))
The error exists even after swapping back to the original 3.1.1 pi.
Can you try beta 3 again? It seems like something might have gone wrong on the update.
-
@Phaedrux said in Duet 3 SBC DCS has stopped
How bout you save us all some time and just exit the thread please.
What why? Don't you don't like the fact that I pointed out the problem days ago, a problem that has been proven to be true, just because you don't like the fact its still a fact none the less.
-
@Phaedrux If you're referring to the v3.1.1 in the pic that's from when I did it after switching back. when I went to the beta it showed the same error but v3.2.3
I can try again to verify if you'd like
-
@CaLviNx said in Duet 3 SBC DCS has stopped:
@Phaedrux said in Duet 3 SBC DCS has stopped
How bout you save us all some time and just exit the thread please.
What why? Don't you don't like the fact that I pointed out the problem days ago, a problem that has been proven to be true, just because you don't like the fact its still a fact none the less.
You seem to have mistaken my use of the word please as a request.
-
@Phaedrux said in Duet 3 SBC DCS has stopped:
@CaLviNx said in Duet 3 SBC DCS has stopped:
@Phaedrux said in Duet 3 SBC DCS has stopped
How bout you save us all some time and just exit the thread please.
What why? Don't you don't like the fact that I pointed out the problem days ago, a problem that has been proven to be true, just because you don't like the fact its still a fact none the less.
You seem to have mistaken my use of the word please as a request.
Excuse me? Is that a threat
-
@CaLviNx I'm trying to figure this out and some people are trying to help. you posted you swapped to standalone and i acknowledged the error went away but it didn't solve the problem. The point was to troubleshoot the firmware on the RPI because other members were trying to help with that.
If you want to argue do it on someone else's post.
-
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx I'm trying to figure this out and some people are trying to help. you posted you swapped to standalone and i acknowledged the error went away but it didn't solve the problem. The point was to troubleshoot the firmware on the RPI because other members were trying to help with that.
If you want to argue do it on someone else's post.
I'm not arguing with you. The gentleman in question thinks that just because he is a certain position that means he can dictate things I was trying to assist you days ago, I pointed out that there is a provable issue running the duet-3 in conjunction with an sbc, again that's a fact. The gentleman doesn't seems to like the fact of that fault (where ever it lies) being pointed out
-
@CaLviNx said in Duet 3 SBC DCS has stopped:
The gentleman doesn't seems to like the fact of that fault (where ever it lies) being pointed out
Not at all. It's your attitude that I take issue with. If you don't have anything helpful to add to a troubleshooting thread, you are welcome to stop posting to it.
-
@Phaedrux said in Duet 3 SBC DCS has stopped:
@CaLviNx said in Duet 3 SBC DCS has stopped:
The gentleman doesn't seems to like the fact of that fault (where ever it lies) being pointed out
Not at all. It's your attitude that I take issue with. If you don't have anything helpful to add to a troubleshooting thread, you are welcome to stop posting to it.
I don't really care what you think of my attitude. I have already added the most helpful solution (you just don't like it) and that is to use the duet in standalone mode until such a time as that the provable issue is recognised and a solution to the problem is found
