RRF 3.01 RC11 problems

Marco Bona

@bearer , from the dwc console. I have disconnected Panel due for the moment.
Why? Am I doing something wrong?

A Former User

Not wrong, just odd. The simple explanation would be USB and the duet in bootloader mode; but if DWC works and M122 doesn't it is strange.

Are you using the standard 57600 baud for the PanelDue? Also try adding M575 P1 S1 B57600 to your config as it will become neccecary in the next release anyway.

Marco Bona

@bearer , I have already added M575 P1 S1 B57600 in config.g
I attach the image with answer of M122

A Former User

Still strange; but it can print?

Does DWC respond to M115? If not can you connect via USB and try? (take care to disconnect the 12/24v power supply to avoid potential for ground loops, USB power is enough to try M122 and M115).

Marco Bona

@bearer , yes, I'm printing even if every now and then the filament gets stuck in the extruder for no reason, but I think it's not a related problem.
M115 works correctly in DWC.
M122 from YAT works.

m122
=== Diagnostics ===<LF>RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC11+1 running on Duet WiFi 1.02 or later + DueX5<LF>Board ID: 08DGM-9T6BU-FG3SN-6J9F0-3S46M-9UYZD<LF>Used output buffers: 1 of 24 (15 max)<LF>=== RTOS ===<LF>Static ram: 28076<LF>Dynamic ram: 95636 of which 56 recycled<LF>Exception stack ram used: 284<LF>Never used ram: 7020<LF>Tasks: NETWORK(ready,272) HEAT(suspended,1280) DUEX(suspended,160) MAIN(running,1916) IDLE(ready,76)<LF>Owned mutexes: WiFi(NETWORK)<LF>=== Platform ===<LF>Last reset 00:01:07 ago, cause: power up<LF>Last software reset at 2020-05-02 20:54, reason: User, spinning module GCodes, available RAM 6824 bytes (slot 0)<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d<LF>Error status: 0<LF>MCU temperature: min 24.4, current 27.3, max 27.6<LF>Supply voltage: min 0.1, current 0.5, max 0.8, under voltage events: 0, over voltage events: 0, power good: no<LF>Driver 0: ok, SG min/max not available<LF>Driver 1: ok, SG min/max not avai<Warning: Maximal number of bytes per line exceeded! Check the end-of-line settings or increase the limit in the advanced terminal settings.>

A Former User

While i doubt it'd make a difference check if there is a newer compatible version of DWC, then post the DWC version and see if chrishamm or dc42 has anything to add I guess (or anyone else for that matter)

Marco Bona

@bearer , @dc42 , @chrishamm , DWC version is 2.1.6, firmware version is 3.01-RC11+1on Duet Wifi and panel due firmware is 1.23.2, released today,but I was already having problems with the previous version.
I remain available for further checks

dc42

Please check that PanelDue is also set to 57600 baud, on the Setup page of PanelDue.

Latest PanelDue firmware is 1.24 available at https://github.com/dc42/PanelDueFirmware/releases/tag/1.24. Instructions for installing PanelDue firmware are at https://duet3d.dozuki.com/Wiki/PanelDue_Firmware_update.

Marco Bona

@dc42 , i have the same problem with 1.24. Sorry but I saw that in the dropbox folder you had a panel due file (1.23.2) that I installed.
The bauds are set correctly.
Today I downgraded to stable RRF3.0 and M122 works properly from DWC while I continue to have problems with panel two (I don't see the contents of the gcode and macro folder), I noticed that when I run some commands (ex. M584 P5) from the console nothing happens while M122 and homing work properly from panel due.
I tried to connect panel due to Duet3 (I have RRF 3.01 RC9 or 10, I don't remember) and it seems to work correctly. Can it be a communication problem with the duet wifi board?

dc42

@Marco-Bona said in RRF 3.01 RC11 problems:

@dc42 , i have the same problem with 1.24. Sorry but I saw that in the dropbox folder you had a panel due file (1.23.2) that I installed.
The bauds are set correctly.

Strange, the RRF 3.01-RC11, DWC 2.1.6 and PanelDue 1.24 combination is working well for me and others.

Can it be a communication problem with the duet wifi board?

Could be, but I'm not aware of any reason why RRF 3.01-RC11 would behave differently from 3.0. I assume you are using DuetWiFiServer release 1.23.

Marco Bona

@dc42 , yes, I'm using that version of DuetWifiServer.
Is there any procedure to check the integrity of the board?
I'm starting to think I have some problems with that card and I believe that the continuous panel due restarts during printing are due to some communication problem but I don't know how I could verify it.
Initially I thought that they were due to something that went to the ground but do not happen according to a logic.
I also checked almost all the electrical wiring but I don't find anything strange.
Not having shielded cables can it be caused by some interference with the motors?

dc42

@Marco-Bona said in RRF 3.01 RC11 problems:

I'm starting to think I have some problems with that card and I believe that the continuous panel due restarts during printing are due to some communication problem but I don't know how I could verify it.

PanelDue restarts are not normal. Perhaps something is pressing on the PanalDue reset button; or there is a bad connection in the 5V or ground wire between the Duet and PanelDue; or the 5V rail is unstable for some reason.

Marco Bona

@dc42 , Ok, said so I assume that the problem may be due to the 5V line because I find the same problem with both the ribbon cable and the 4-wire one.
With Duet3 I have not yet been able to try because I am finishing wiring everything and I think it will still take some time.
Thanks for the clarification.

dc42

@Marco-Bona said in RRF 3.01 RC11 problems:

@dc42 , Ok, said so I assume that the problem may be due to the 5V line because I find the same problem with both the ribbon cable and the 4-wire one.
With Duet3 I have not yet been able to try because I am finishing wiring everything and I think it will still take some time.
Thanks for the clarification.

Are you certain it is just the PanelDue restarting, not the Duet? What do you see when it restarts?

Marco Bona

@dc42 , only panel due restarts, I see the initial screen with the logo, instead the printing proceeds without problems. The strange thing is that when I restart Duet wifi a series of line errors are displayed but I cannot tell you which ones because it is too fast to do it and they do not remain stored in the console. Tomorrow night I check the 5V, but if it were unstable that line can also create all the other problems?