Duet 3 SBC DCS has stopped
-
@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
-
@CaLviNx again that's not a solution that's a work around
-
@dhusolo said in Duet 3 SBC DCS has stopped:
@CaLviNx again that's not a solution that's a work around
Anything that gets you printing is a solution
-
@CaLviNx said in Duet 3 SBC DCS has stopped:
Ihave already added the most helpful solution (you just don't like it)
I haven't said a thing about your solution. Yes you're correct it works in standalone. Great. We'd like to do some more testing to see what's going on in SBC mode with the new beta. If that disinterests you, find another thread.
-
@dhusolo
Did you downgrade the firmware on the duet 3 manually to 3.1.1 before downgrading the software on the Pi?
The connection between the two was changed significantly at beta 2 and a board running beta 2 or 3 can't connect to a lower version of DSF and vice versa. -
@jay_s_uk I can't remember 100% because I did a few different things in standalone and SBC. I think I used the erase jumpers and powered on the board.
-
It would be good if we could get beta 3 on there and see if it's working at all. It sounded like you lost communication between the duet and pi entirely when you tried to update to beta 3. Is that right?
-
@Phaedrux Correct. Just making sure I'm doing it right, Is there a different way to erase the firmware on the board besides the erase jumpers or would even using a different SD card do the trick?
-
Well you normally don't need to erase the firmware, but yes the jumper is the way to do that. Once erased you will need to use usb to flash a firmware again.
A different SD card won't help since the firmware is flashed to the board itself. The firmware bin file on the sd card is just there for storage during in place flashing.
What version is flashed to the duet right now?
What version is the Pi running?If you're completely back on 3.1.1 right now, are you on the unstable branch for apt-update? How did you originally try to update to the beta?
-
@Phaedrux I think I got it back to 3.1.1.
What's the command to verify version info including DWS and DWC?
-
From the gcode console send M122 and post the results please.
Additionally send M122 "DSF"