PanelDue 4.3" never connects



  • Hi *,

    My PanelDue 4.3" do not connect to my Duet2 anymore. Both have the most recent FW running (1.24/3.01-RC12). The connection worked till some hours ago with the same firmware. I played with the BLTouch config only.

    The PanelDue is connected via the 4 wire cable. I replaced it with a other one. I tried the ribbon cable which came with the Panel. I used a 7" PanelDue via the 4 wire cable. I tested with both cables in parallel. All with the same result, the display stays at "Connecting"

    I learned from a other thread that "M575" is important here.
    After reboot:

    11/05/2020, 00:57:42	M575 P1
    Channel 1: baud rate 57600, requires checksum
    11/05/2020, 00:57:37	M575 P0
    Channel 0: baud rate 115200, does not require checksum
    

    The display is at 57600, so I changed it:

    11/05/2020, 00:59:08	M575 P1
    Channel 1: baud rate 57600, requires checksum
    11/05/2020, 00:58:54	M575 P0 B57600 S1
    

    Nothing helped.

    I'm a bit lost now. Any ideas?

    Cheers, Chriss



  • @Chriss said in PanelDue 4.3" never connects:

    11/05/2020, 00:58:54 M575 P0 B57600 S1

    M575 P1 B57600 S1 is the config you want, P0 is for the USB conside console afaik.



  • @bearer said in PanelDue 4.3" never connects:

    M575 P1 B57600 S1 is the config you want, P0 is for the USB conside afaik.

    And that is what I have, the "P0" was just to be on the save site for testing.

    Any other idea?

    Cheers, Chriss



  • Any other idea?

    IIRC having two identical M575 commands was just a work around for non-standard baud rates and fixed in RC12, but you could try it.

    Maybe post the complete config, maybe someone spots any changes the BL touch stuff could have done to IO_0?

    Btw, you only need the 4 pin wire to get past "connecting", the ribbon is just for the SD card.



  • @bearer

    That with the cable is clear, I just wanted to mention what I tried already.

    I created a new configuration from scratch with the configtool to make sure that I did not messed up the configuration during my BLTouch journey (I used the "Creality Ender 3 Pro".) Still with the same problem.

    config.g

    ; Configuration file for Duet WiFi (firmware version 3)
    ; executed by the firmware on start-up
    ;
    ; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue May 12 2020 16:59:30 GMT+0200 (Central European Summer Time)
    
    ; General preferences
    G90                                            ; send absolute coordinates...
    M83                                            ; ...but relative extruder moves
    M550 P"Ender 3 Pro"                            ; set printer name
    M918 P1 E4 F2000000                            ; configure direct-connect display
    
    ; Network
    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 S0                                     ; physical drive 3 goes backwards
    M584 X0 Y1 Z2 E3                               ; set drive mapping
    M350 Z128 I0                                   ; configure microstepping without interpolation
    M350 X16 Y16 E16 I1                            ; configure microstepping with interpolation
    M92 X80.00 Y80.00 Z400.00 E93.00               ; set steps per mm
    M566 X1200.00 Y1200.00 Z24.00 E300.00          ; set maximum instantaneous speed changes (mm/min)
    M203 X9000.00 Y9000.00 Z180.00 E6000.00        ; set maximum speeds (mm/min)
    M201 X500.00 Y500.00 Z100.00 E5000.00          ; set accelerations (mm/s^2)
    M906 X800 Y800 Z800 E1000 I50                  ; 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 X310 Y310 Z400 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 S2                                     ; configure Z-probe endstop for low end on Z
    
    ; Z-Probe
    M950 S0 C"duex.e5heat"                         ; create servo pin 0 for BLTouch
    M558 P9 C"zprobe.in+zprobe.mod" H5 F120 T6000  ; set Z probe type to bltouch and the dive height + speeds
    G31 P500 X0 Y0 Z2.5                            ; set Z probe trigger value, offset and trigger height
    M557 X15:215 Y15:195 S20                       ; define mesh grid
    
    ; Heaters
    M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; 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
    M143 H0 S150                                   ; set temperature limit for heater 0 to 150C
    M307 H0 B0 S1.00                               ; disable bang-bang mode for the bed heater and set PWM limit
    M140 H0                                        ; map heated bed to heater 0
    M308 S1 P"e0temp" Y"thermistor" T100000 B4092  ; 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
    M143 H1 S275                                   ; set temperature limit for heater 1 to 275C
    M307 H1 B0 S1.00                               ; disable bang-bang mode for heater  and set PWM limit
    
    ; Fans
    M950 F0 C"fan0" Q500                           ; create fan 0 on pin fan0 and set its frequency
    M106 P0 S0 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 H1 T45                              ; set fan 1 value. Thermostatic control is turned on
    M950 F2 C"fan2" Q500                           ; create fan 2 on pin fan2 and set its frequency
    M106 P2 S1 H1:0 T45                            ; set fan 2 value. Thermostatic control is turned on
    
    ; Tools
    M563 P0 D0 H1 F0                               ; 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
    
    ; Custom settings are not defined
    
    

    Do you need more?

    Cheers, Chriss



  • @Chriss

    Where's the

    M575 P1 B57600 S1
    

    in that config?



  • @jay_s_uk
    Not there, but it seams like it is the default. It is set to the expected parameters when I query "M575 P1". But I will try to add it tomorrow.



  • @Chriss said in PanelDue 4.3" never connects:

    @jay_s_uk
    Not there, but it seams like it is the default. It is set to the expected parameters when I query "M575 P1". But I will try to add it tomorrow.

    Not after RC12



  • @bearer

    Fiddlesticks!

    From the RC12 WHATS_NEW_RRF3.md:
    All PanelDue users: the PanelDue connector (or IO_0 on Duet 3) is no longer dedicated to PanelDue, therefore if you connect a PanelDue to this port you must use the following command in config.g to enable it: M575 P1 S1 B57600. You can use baud rates other than 57600, however the IAP files all assume 57600 baud; therefore if you use another baud rate then PanelDue will not display firmware update progress.

    😞 To many things in parallel.....

    I like the new behavior in "3.01":
    If the serial aux port hasn't been enabled, M575 P1 with no other parameters now reports this

    It works now with the fresh generated config and I added "M575 P1 B57600 S1" to the config. I guess that the configtool should ask for a PanelDue and add this parameter than.

    I will check my "actual" config now, it is proven that it must be a configuration problem.
    🤦

    Cheers, Chriss



  • @Chriss said in PanelDue 4.3" never connects:

    I guess that the configtool should ask for a PanelDue and add this parameter than.

    Very good point!


  • administrators

    @Chriss said in PanelDue 4.3" never connects:

    @jay_s_uk
    Not there, but it seams like it is the default. It is set to the expected parameters when I query "M575 P1". But I will try to add it tomorrow.

    In 3.01-RC12 the M575 P1 command fails to tell you that the port is not enabled. The fix for that will be in the 3.01 release.


Log in to reply