-
What issues exactly are you having? What isn't working? Or rather, what is it actually doing? Does the screen light up at all?
When you have flashed the firmware with Bossa does the screen let you interact with it? Does it display the normal menu items when powered by USB?
Your Duet firmware should be 3.3.
Your PanelDue firmware should be either 3.2.11 or 3.3 RC3 if you want to try testing.
Which firmware file specifically did you use to flash the Panel?
M575 P1 S1 B57600 must be in config.g for it to work.How are your wires ordered for the 4 pin connector? Did you make the cable yourself or did it come with the Panel? When you plug it in and power on does it power up as well?
-
@phaedrux Thanks for the help, I'm going to flash the paneldue firmware to 3.3 RC3 and check up on it.
The problem i'm facing with the paneldue is that it boots up, shows me the logo, and then displays the 'connecting' status in the upper right hand corner, as if it's not receiving any data from the duet.
It should be noted that I can home axes from the paneldue, but that appears to be all I can do. I can't heat the extruder.
The cable is one I got with one of my stepper motors that I terminated with the connectors I got with the duet. I've checked the continuity and wire configuration of the cables multiple times, everything is as presented in the paneldue guide.
I'll follow up on this soon, I've got a fairly long job on the printer at the moment, I'd like to try everything you suggested before I ask for any further help.
Again, thanks a million for any help,
RBIII -
Hey @redrout, this problem sounds a little strange. If g-codes are working in general, i.e. homing gcodes, then other communication should work as well.
You are using Paneldue firmware 3.3.0-rc3 on a Paneldue 7.0i.
Please upload a copy of your configuration.
And please test the following commands and post the reply.
M115Visit me on github at https://github.com/mfs12/
-
Right, thanks a ton for waiting lol.
The output of the M115 command is as follows:
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03
My config file is as follows:
.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 23:51:34 GMT-0500 (Central Daylight Time); General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"*****" ; set printer name; Network
M551 P"*****" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1590.00 E420.00 ; set steps per mm
M566 X90.00 Y90.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X50.00 Y50.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1100 Y2200 Z800 E700 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X640 Y540 Z1000 S0 ; set axis maxima; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"!zstop" ; configure active low endstop for low end on Z via pin zstop
; M574 Z1 S2 ; configure z to use a probe at the min; Z-Probe
;M558 P9 C"^zprobe.in" H3 F100 T2000 ; specify probe and input pin, also enable pullup resistor
;M557 X15:20 Y15:195 S20 ; define mesh grid
;G31 P100 X10 Y10 Z2 ; define offset and sensitivity for bltouch
;M950 S0 C"exp.heater3" ; create servo pin index; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit
M140 H0 ; map heated bed to heater 0
M143 H0 S120 ; set temperature limit for heater 0 to 120C
M308 S1 P"e0temp" Y"pt1000" ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H3 A-1 C-1 D-1 ; unbind heater pin 3 for use in bltouch; Fans
M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
M106 P0 S1 H-1 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
M106 P1 S1 H-1 ; set fan 1 value. Thermostatic control is turned off; Tools
M563 P1 D0 H1 F1 ; define tool 1
G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets
G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C; Custom settings are not defined
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDueI'm still learning a lot, so let me know if I've botched the configuration.
Thanks
-
@redrout said in Persistent PanelDue Trouble:
; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue
I'm still learning a lot, so let me know if I've botched the configuration.Well the only line that matters for PanelDue is the enable command which you already have, so no problem there.
-
-
@redrout if you can send commands to the Duet then transmission from PanelDue to Duet must be working. So most likely there is a problem with the wire that connects UTXD on the Duet to DIN on the PanelDue.
-
Thanks for the replies, I did some more reading, and replaced the cable with a shorter one (4 feet before to 6 inches or so now). I tested the current cable and it looks good, but the issue still persists (can still send commands but stuck connecting). On the off chance I had a bad wire again I swapped the UTXD - DIN wire with the URXD - DOUT wire on the terminals and tried again, but the same problem happens. I looked at some of the traces on the duet and the paneldue, but nothing looks obviously amiss.
-
Hey @redrout,
- are there errors in the console tab?
- what state does paneldue report in the top right corner?
Visit me on github at https://github.com/mfs12/
-
@mfs12 The console tab doesn't display anything, even if I do send commands to the board via the PanelDue. The PanelDue reports "Connecting"
thx
-
It definitely sounds like it's just not connecting, though seems to be functional otherwise and you're able to flash the firmware, etc.
Your config looks ok, it just needs the command to enable it and set the baud rate. Have you verified in the setup page of the paneldue that the baud rate is set to match the config? 57600?
-
Hey @redrout, did you send the M115 command from DWC or PanelDue?
If PanelDue reports "connecting" the connection was not yet established. This points to either a physical connection problem (cabling or sockets) or not matching uart configuration of the Duet3d board and PanelDue.
To improve debugging such problems in future i will consider improving error reporting about connection issue in PanelDue's message log.
Visit me on github at https://github.com/mfs12/
-
@mfs12 I appreciate the improvement potential, but is there any way for me to resolve this issue on my end? I just don't know what to do with my paneldue now, since it doesn't receive information it seems to be little better than a paperweight.
-
Are you able to test with a new shorter 4 wire cable and/or the 10 pin ribbon cable?
When and where did you purchase the PanelDue?
-
Hey @redrout,
closing this thread due to inactivity. Please re-open if your issue persists with newer version of paneldue.
