Web Control and firmware not compatible anymore

FG

@phaedrux I installed 3.0 and now the bed and hotend have a measured temperature of -273.1 °C and also the defaults for the "active" and "standy" temperatures are -273 °C. I have a delta printer with a Smart Effector and before reloading the Web Controller, the old Web Controller also showed that the z probe is read as permanently triggered now. After restarting and reloading everything I now have Duet Web Control 2.0.4 and there the z probe is not shown any more. So I cannot say if it is still read faulty. But the measured and default bed and heater temperatures remain at -273.1 °C.

After the update, before reloading the web interface I tried the M308 command from here:
https://docs.duet3d.com/en/User_manual/Connecting_hardware/Temperature_connecting_PT100
to properly configure the heater. A second heater showed up in the interface for a moment, afterwards it reloaded itself to the new version where only the one original heater was shown again, but still with the absolute zero temperature measured as well as shown on the touch display as active and standy temperature.

FG

@phaedrux
I found this guide how to adapt the configuration for the version 3 firmware:

https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_Summary_of_what_you_need_to_do_to_convert_your_configuration_and_other_files

I could fix the temperature sensors and heaters but failed with the z probe. First I added it to the z axis which lead to my printer crashing in the endstop continuously. After adding it to E0 the "normal" endstops of my delta printer at the top of each axis work again. I implemented the z probe in the config.g now as follows:

M558 P5 C"e0stop" X0 Y0 Z0 R0.4 H30 F1000 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
; Z probe parameters
G31 K0 P100 X0.0 Y0.0 Z-0.02

before it was:

M558 P5 X0 Y0 Z0 R0.4 H30 F1000 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
; Z probe parameters
G31 T1 P100 X0.0 Y0.0 Z-0.02

Due to this change the z probe value is shown in the Web Control again. But it still is permanently triggered with a value of 1000. I could not find any information in the link above why this should happen and what is the source of the error. I did not dare to start a calibration run because I am afraid that the printer will chip down my glass bed while misreading the z probe sensor.

Also I am a little bit afraid to continue updating after this 3.0 version because the linked guide above says that from 3.01 on I have to define my fans with the M950 command and the pins they use. But without disassembling my whole printer setup I have no idea which pins they use and would need to try them out until the correct fan is spinning. Is there a way to read out the pins for the automatically detected fans in 3.0?

infiniteloop

@fg said in Web Control and firmware not compatible anymore:

But without disassembling my whole printer setup I have no idea which pins they use and would need to try them out until the correct fan is spinning.

In RRF 2.x, fans are numbered from 0 up. Same is true for other devices like heaters and steppers. Using these schematics you can map the old numbering scheme to the new pin names for M950.

dc42

@fg said in Web Control and firmware not compatible anymore:

I could fix the temperature sensors and heaters but failed with the z probe. First I added it to the z axis which lead to my printer crashing in the endstop continuously. After adding it to E0 the "normal" endstops of my delta printer at the top of each axis work again. I implemented the z probe in the config.g now as follows:
M558 P5 C"e0stop" X0 Y0 Z0 R0.4 H30 F1000 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
; Z probe parameters
G31 K0 P100 X0.0 Y0.0 Z-0.02

before it was:
M558 P5 X0 Y0 Z0 R0.4 H30 F1000 T6000 ; Set Z probe type to unmodulated, the axes for which it is used and the probe + travel speeds
; Z probe parameters
G31 T1 P100 X0.0 Y0.0 Z-0.02

Due to this change the z probe value is shown in the Web Control again. But it still is permanently triggered with a value of 1000.

It looks like your Z probe is connected to the ZProbe connector on the Duet, but your M558 command assumes it is connected to the E0_Stop connector. So change "e0stop" in the M558 command to "zprobe.in".

FG

@dc42 Thank you very much for the correct name of the connector. With this change everything was running under 3.0 so I continued to 3.3. I had to play around a little bit to understand the new fan control but in the end I was able to make them work again as they did before.

But with 3.3 the touch screen (PanelDue) is not able to connect to the printer any more. It shows "Connecting" in the upper right corner and gets no data about the printer. In the setup tab it tells its software version to be 1.17. I found out that I have a 5 inch version of the PanelDue but not more details about the hardware. Here:

https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_PanelDue

"late V2/V3/5i/7i PanelDue" are mentioned and I don't know if my PanelDue is a V1 oder V2 or a normal 5" or even 5i. How can I find out if I can install the improved firmware on my PanelDue? And when I cannot install it, will version 1.25 at least allow my PanelDue to communicate with my printer again or do I have to downgrade it to 3.0 again and stay at this version in order for the PanelDue to work?

infiniteloop

@fg Thank you for the link

Allow me to cite that:

For all versions of RepRapFirmware up to RRF 3.1.1, and all versions of PanelDue, use PanelDue firmware version 1.25.0

So, depending on the Paneldue you have, you may be limited to RRF 3.1.1.

However, as you have v1.17 installed, you have to upgrade the display via USB (i.e. with Bossa), which means you need physical access to the PanelDue - at least to its USB connector and the reset and erase buttons. That’s a good chance to check which kind of board you own

Dougal1957

@fg do you have a M575 line in your Config.g to configure the Serial comms for the PanelDue?
see https://docs.duet3d.com/en/User_manual/Reference/Gcodes.

Doug

Phaedrux

In RRF3 you need to tell it you have a PanelDue connected and set the baud rate.

M575 P1 B57600 S1

It may be beneficial to create a new config using the online tool for 3.x just to see an example of the syntax.

https://configtool.reprapfirmware.org/Start

Phaedrux

@fg said in Web Control and firmware not compatible anymore:

don't know if my PanelDue is a V1 oder V2 or a normal 5" or even 5i.

You can post a photo of the paneldue and we can get an idea what it is. Also when you connect to it with Bossa it will give you the CPU/RAM info about it and that will narrow it down further.

FG

@phaedrux Thank your for the information. Also thank you Dougal1957 for coming up with the M575 command. I missed the part that I need it in the newer firmware. With this command the PanelDue with its version 1.17 connects to the DuetWifi with firmware 3.3.

Unfortunately I get a lot of guests tomorrow which stay until the end of the week. So I am busy preparing different things. I am going to open the case of my PanelDue and connect to it via USB as infiniteloop suggested on Monday in order to find out which version I have. I will let you know as soon as I have more information about it. And even though we have just Wednesday now, I wish you all a nice weekend!

FG

I opened my PanelDue and it is labelled V 3.0. Due to my firmware already being V. 3.3 I was able to manually press the erase and reset button and upload new firmware (sending the erase and reset commands from the Duet board failed). I tried out the PanelDue firmware 1.25 for PanelDue 3.0-4.3 but this resulted in black stripes on the touch screen which was no longer reacting. However the binary for 3.0-5.0 worked.

Afterwards I updated the DuetWiFi first to 3.4.0 and afterwards to 3.4.1. With this working, I finally updated the PanelDue to 3.4.1 pre 2.

Now everything is up to date and working again. Thank you all very much!

infiniteloop

@fg said in Web Control and firmware not compatible anymore:

Now everything is up to date and working again.

Good to hear.