PanelDue DOA?

SupraGuy

So... this is what I see connecting my new PanelDue. WTF? Did I get one DOA? I only connected the controller and LCD, didn't force anything, and connected the 4 pin serial. Kinda bummed...

Phaedrux

I'd try reseating it again and then try flashing the firmware to 1.24 just in case. If that doesn't work, then an exchange with the vendor I think.

SupraGuy

whew. From this, I surmise that the firmware mine came with was for the wrong LCD. Now to connect it to the Duet and see if it looks more reasonable

Phaedrux

It would appear that when you buy a controller separately it has the 4.3 inch firmware flashed. Hence the mismatch. We're gonna look into getting a sticker or something on those.

Generally with the PanelDue though, if in doubt, double check your firmware version and reflash.

SupraGuy

It appears that the PanelDue connects, then stops responding. I suspect that it needs to be enabled in the config.g. I'm not panicking about it.

I knew that I was out of date with my backup config, but it's astounding to find out exactly how far out of date I was, including having the machine home in the wrong direction, build size parameters incorrect... I'm sure that I have a more recent backup than this, but I can't find it.

Back up your SD cards regularly, folks!

I'll work on getting that PanelDue working, but first I need to get the basic printer working so that I can print a mount for the PanelDue.

Fan wires and motor wires seem to be all that was damaged. I don't have motors with clips at the motor end, considering soldering new silicone insulated wires in.

Phaedrux

@SupraGuy said in PanelDue DOA?:

I suspect that it needs to be enabled in the config.g.

M575 P1 B57600 S1

SupraGuy

Well, the PanelDue appears to be working now, but I can't home Z. The IR sensor light flashes, but it doesn't seem to trigger. I'll have to trouble-shoot it.

Everything else appears to be okay now. I wired my Z motors backwards initially, because they don't have the KK connectors on them, so the plugs can be reversed, and of course I did.

I think that the kinematics are all configured correctly, I get sane readongs for nozzle and bed temperature (Had to re-configure the nozzle sensor as a PT1000) and I have new fan wires in. I also have wires in (finally) for a part cooling fan. I was going to replace fans with 12V versions, but I haven't done it yet, so I did not install the 12V DC converter.

I'm not sure why the PanelDue wasn't working. I havent changed anything, but after getting everything wired up again, it seems to work. No looking the gift horse in the mouth, I'll take it.

SupraGuy

Ugh. I know better, but I really wish that I had a more recent backup of my working config.

Only a few more things to tune really, the printer is basically working now.

The PanelDue... It works for a while after power on, then stops. I was playing with it last night, and it's consistent. Power on, and it works. Use it or not makes no difference, it stops responding after a while. Using the 10 pin connector or the 4 pin, makes no difference.

wilriker

@SupraGuy said in PanelDue DOA?:

The PanelDue... It works for a while after power on, then stops. I was playing with it last night, and it's consistent. Power on, and it works. Use it or not makes no difference, it stops responding after a while. Using the 10 pin connector or the 4 pin, makes no difference.

More details are required here:

RRF version
PanelDueFirmware version
M122 before and after it stopped working (I don't think catching the exact moment is crucial)
config.g (never hurts)

SupraGuy

@wilriker
Board: Duet WiFi 1.02 or later
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)
Duet WiFi Server Version: 1.23
PanelDue firmware 1.24 (As @Phaedrux suggested when I first powered it up and got the technicolor crap.)

; Configuration file for Duet WiFi (firmware version 1.20 or newer)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool on Tue Jun 26 2018 20:51:43 GMT-0600 (Mountain Daylight Time)
; Modified by DMG 09/2/2020

; General preferences
G90                              ; Send absolute coordinates...
M83                              ; ...but relative extruder moves

; Custom configuration
M584 Z2:4 E3                     ; Set Z motors on drives 2 and 4 DMG 08/30/2018
M671 X-43.0:309:0 Y137.5:137.5   ; Set the Z motor relative locations DMG 08/30/2018

; Network
M550 PDMG3D01                    ; Set machine name
M552 S1                          ; Enable network
M586 P0 S1                       ; Enable HTTP
M586 P1 S1                       ; Enable FTP
M586 P2 S0                       ; Disable Telnet
M575 P1 B57600 S1                ; Enable PanelDue


; Drives
M569 P0 S1                       ; Drive 0 goes forwards
M569 P1 S1                       ; Drive 1 goes forwards
M569 P2 S1                       ; Drive 2 goes forwards
M569 P3 S1                       ; Drive 3 goes forwards
; DMG 08/30/2018 I think the following line need to be configured
M569 P4 S1                       ; Drive 4 goes forwards
M350 X16 Y16 Z16 E16 I1    ; Configure microstepping with interpolation
M92 X400 Y400 Z400 E102.8        ; Set steps per mm
M566 X900 Y900 Z12 E120          ; Set maximum instantaneous speed changes (mm/min)
M203 X7500 Y7500 Z480 E1200      ; Set maximum speeds (mm/min)
M201 X500 Y200 Z250 E250         ; Set accelerations (mm/s^2)
M906 X800 Y800 Z800 E800 I30     ; Set motor currents (mA) and motor idle factor in per cent
M572 D0 S0.22                    ; Set Pressure Advance to 0.22
M84 S30                          ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                 ; Set axis minima
M208 X248 Y285 Z190 S0           ; Set axis maxima

; Endstops
M574 X2 Y2 S0                    ; Set active low endstops

; Z-Probe
M574 Z1 S2                       ; Set endstops controlled by probe
M558 P1 H5 F720 T6000            ; Set Z probe type to unmodulated and the dive height + speeds
G31 P500 X-15 Y0 Z2.22            ; Set Z probe trigger value, offset and trigger height
M557 X15:205 Y15:205 S20         ; Define mesh grid

; Heaters
M305 P0 T100000 B4138 C0 R4700   ; Set thermistor + ADC parameters for heater 0
M143 H0 S120                     ; Set temperature limit for heater 0 to 120C
M305 P1 X501 R4700               ; sensor 1 PT1000
M143 H1 S300                     ; Set temperature limit for heater 1 to 300C

; Fans
M106 P0 S0.0 I0 F500 H-1         ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S1 I0 F500 H1 T45        ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned on
M106 P2 S1 I0 F500 H1 T45        ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned on

; Tools
M563 P0 D0 H1                    ; Define tool 0
G10 P0 X0 Y0 Z0                  ; Set tool 0 axis offsets
G10 P0 R0 S0                     ; Set initial tool 0 active and standby temperatures to 0C

; Automatic saving after power loss is not enabled

; Custom settings are not configured

wilriker

@SupraGuy So there's nothing obviously wrong/problematic in config.g. Still I'd like to see the output of M122 before and after.

What I can tell you is that I have not seen any connection issues with PanelDueFirmware 1.24 and RRF 3.1+. Maybe it's an issue the has been fixed meanwhile. Have you considered upgrading to 3.1.1/3.2-beta1?

SupraGuy

Well, I took the plunge and updated to firmware 3.1.1

A few things were a royal pain, things that I'd tuned that needed finding and re-entering. Like extruder steps that were entirely wrong. There didn't seem to be a spot in the configurator for using 2 motor drives for the Z axis, Pressure advance needed tuning, and it scared the crap outta me when it said that the heat bed was faulting. (PID tuning needed to happen again.) All that stuff I figured out 2 years ago and have since forgotten.

So far, so good.