Got my paneldue... It says "connecting" and controls nothing...
-
I do PCB Repair, and under my scope, there is no break, or bad solder joint... Aside from that, both interfaces do not work.. (ribbon cable, or 4 pin) I have several of each, so it's not the cable, and I have continuity from the solder joint on the duet to the solder joint on the paneldue..
-
@Steve-Lynch whats the story with the lifted pad / pin in the top left corner, close to RA2/RA7?
Since you seem to be familiar with the topic: do you have a scope? Can you probe the UART pins of the SAM4S directly? just to make sure the traces are all fine.
-
That connector, the (X4 connector) was broken off in shipping. While I did email filastruder, I've been told by others that the connector isn't used, so It should not be an issue. The traces leading to the pads are fine, but the pads themselves were ripped off it seems.
I have a Microscope, not oscilloscope.. lol. I replace blown capacitors and power supplies and repair traces and stuff, I'm wasn't trying to be "mr. know it all", I just was establishing that I had checked beyond the obvious...
And I tried swapping din dout, that didn't do anything as expected (rx to rx - Tx to Tx)
-
@steve-lynch said in Got my paneldue... It says "connecting" and controls nothing...:
Tried it with the ribbon cable interface as well.. it powers it, it shows firmware upgrade status, but it does not "connect".
Do you mean it shows a progress bar when you upgrade the DuetWifi firmware?
This would mean the connection DOES work... -
@steve-lynch said in Got my paneldue... It says "connecting" and controls nothing...:
That connector, the (X4 connector) was broken off in shipping. While I did email filastruder, I've been told by others that the connector isn't used, so It should not be an issue. The traces leading to the pads are fine, but the pads themselves were ripped off it seems.
With all the troubleshooting you have done so far, I would open a warranty claim & ask for a replacement, due to damaged during shipping.
One last thing maybe:
how long are your wires? I suppose you are not trying to run a 10feet long cable...?
Maybe try a really short one / newly crimped just to make sure. -
yes... When I upgrade firmware, it is showing me the progress on the screen...
-
@resam both wires are about 330mm long. (ribbon and 4 pin)
I'll try some of the Jumpers out of my Arduino kits real quick..
-
Yeah, same deal.. no luck... I'll start a replacement... If it was that badly handled prior to shipping, then god only knows what could have happened to it.. Without probing the entire board, I cannot be positive that there isn't a crack, or open.
Luckily filastruder is 20 min. from me here in Ga. hopefully they'll just let me swing out and swap it.
Thanks for the help!
The stuff I repair is mostly guitar and pro audio amps that get the smoke let out of them because people short the output stage, or cook a power supply. If I can't troubleshoot it with my fluke and a magnifying glass, it goes off to the Ham Radio repair guys down the road..
-
Ok! revealation!
When I ran firmware update again, it said "trying to connect at "23000 baud" or something like that really quickly, then went through all of the other messages..
Based on the command in my Config.G, am I setting the baud?
In my general preferences section in my Config, I inserted this line:
M575 P1 B57600 S1 ;Set baud rate Duet Board.
Based on this, P1 should be the proper interface, right? P0 says it's USB.. B57600 should set the baud to match the paneldue, and S1 is just checking...
It doesn't seem that it's properly setting my Baud. Is there a G command to list the current baud rate?
Or a G command I can simply send to set it?
-
I have this in my
config.g: M575 P1 B57600 S1
You can also send it again via DWC at any time.Make sure your PanelDue is configured to the same, go to the setup tab and double-check.
-
yep same here... I just ran it again.. the message says trying to connect at 230400 Baud
That's way too much. I sent it manually as well.It's not taking it. Oh well... maybe @dc42 might chime in on this matter..
-
@steve-lynch Have you also got it set on the PanelDue as well that is not controlled by the M575 see RESAM's pic above
-
yes
-
-
Looks like it's receiving but not transmitting. The fault could lie in the PanelDue or the Duet. You could check that RA4 and RA5 on the PanelDue look correctly soldered, but assuming they do then I suggest you submit a warranty claim.
-
It's doing the same thing for both types of connections, so it's unlikely that the duet has an issue.. I'm guessing the paneldue has a deeper issue. R4 & R5 look fine under the scope.. I'll just wait for filastruder I guess..
-
@resam said in Got my paneldue... It says "connecting" and controls nothing...:
M575 P1 B57600 S1
@DC42 I just got my new Paneldue from Filastruder... Same thing... It only says "connecting". This is both with 4 wire or 10 pin ribbon. Please.. Can you think of anything?
6 different cables now, including some new 12" 4 pin cables I just picked up today.
I have set the board Baud as instructed, but is there a way to check the Duet's baud through G code or anything?
I tried it straight out of the package as it was... it would not connect.. I updated it's firmware with Bossa... It would not connect. I ran the Duet 2 wifi firmware update, and the paneldue shows the entire progress, but starts off with a message saying "trying to connect at 230400 Baud"
I am just not convinced that the Duet's Baud is changing.. And though I've asked several times, no one has told me how I can actually check it.
Can you please help me? This should not be this difficult.
-
Another question: The M575 command....
I'm using this: M575 P1 B57600 S1
What is the proper port (p value) for the 4 pin paneldue interface?
The instructions say Paneldue USB is P0, but does not list P values for the 10 Pin connection, or the 4 Pin connection. I am simply assuming it's P1? I've tried every P value from 1 to 9.
-
M575 P1 is correct for both connections. Send M575 P1 with no other parameters to verify the baud rate being used on the Duet.
Assuming that confirms the baud rate is 57600, it sounds like there may be a soldering problem with the URXD0 pin on the SAM processor (pin 75), or another problem with that pin. Unless you can see that the pin is badly soldered and you are confident of your ability to re-solder it, I suggest you ask Filastruder to exchange the Duet.
-
@steve-lynch Per the firmware (and the documentation), there are only two options for P: 0 and 1.
https://duet3d.dozuki.com/Wiki/Gcode#Section_M575_Set_serial_comms_parameters
https://github.com/dc42/RepRapFirmware/blob/6b835cb3c8e9aa10113ae750151d9f9065116cd4/src/GCodes/GCodes2.cpp#L3291The documentation does not say "Paneldue USB is P0", it says the main serial interface, typically a USB port [of the Duet] is P0. The correct setting for use with a PanelDue is P1.
Also per the firmware, if a M575 P1 is sent, the reply will be the baud rate that the Duet is set to communicate with the PanelDue at.
The 230400 baud rate that you saw during the firmware update is with regard to the baud rate that the firmware update is occurring onboard the Duet. The fact that this is happening is an indication that the Duet is able to send data to the PanelDue, and the PanelDue is able to receive it. That is also an indication that the baud rate is correct.
