Software 3.5.1 released

dc42

@PDBeal yes we will release PanelDue 3.5 soon, based on the existing RC. We also have a new, more capable screen under development and that will eventually replace PanelDue in our product range.

Exerqtor

@dc42 said in Software 3.5.1 released:

@PDBeal ~~yes we will release PanelDue 3.5 soon, based on the existing RC~~. We also have a new, more capable screen under development and that will eventually replace PanelDue in our product range.

Finally! Looking forrward to hearing & seeing more about that!

ctilley79

@dc42 Onto 3.6!! What’s next on the feature roadmap? Any hints?

JayT

@Alex-cr : I have tried this release. I face a lot of bad command errors suddenly while printing. When I check Gcode line, it is fine. If i revert to 3.4.6, I don't face much bad command errors while printing. Did you face anything like that?

Phaedrux

@JayT said in Software 3.5.1 released:

@Alex-cr : I have tried this release. I face a lot of bad command errors suddenly while printing. When I check Gcode line, it is fine. If i revert to 3.4.6, I don't face much bad command errors while printing. Did you face anything like that?

Can you give some more detail about what exactly you're seeing and where you see it?

Notepad

Wooo, Lets goo!
A lot of nice changes across the board. I especially like the DWC change for the text editor. Applying input shaping to smaller segments has also produced a noticeable increase in print quality, very nice indeed.

I have however noticed a weird behaviour with the resume.g, which I have made a seperate thread for(https://forum.duet3d.com/topic/35544/resume-g-activating-twice-with-fw3-5?_=1713890021060)

JayT

@Phaedrux :

If i simulate the gcode, I get some errors like bad command or message box stating expected integer after Y.
Sometimes error says "C1 " instead of G1. When I look back at the line number in Gcode, Line looks ok.
Is it a problem with Slicer & after error Reprap fixes it ?
Because when I run it the second time, or simulate second time, bad command error either does not come at all, or it comes at a different line.

My problems are similar as posted in the thread :

https://forum.duet3d.com/topic/35553/bad-command-error-using-rrf-3-5-0-and-3-5-1-using-duet2-wifi/2

gloomyandy

@JayT What board are you using?

JayT

@gloomyandy :

I have duet2-wifi.

Phaedrux

@JayT said in Software 3.5.1 released:

@Phaedrux :

If i simulate the gcode, I get some errors like bad command or message box stating expected integer after Y.
Sometimes error says "C1 " instead of G1. When I look back at the line number in Gcode, Line looks ok.
Is it a problem with Slicer & after error Reprap fixes it ?
Because when I run it the second time, or simulate second time, bad command error either does not come at all, or it comes at a different line.

My problems are similar as posted in the thread :

https://forum.duet3d.com/topic/35553/bad-command-error-using-rrf-3-5-0-and-3-5-1-using-duet2-wifi/2

Can you start a thread for your issue and include as much detail as possible?

alwaysom

Hello
got this message"Error in start-up file macro line 5: in file macro line 5 column 17: M307: expected number after 'K'" " on startup after updating to 3.5.1.
I first thought it was a problem in config-override or config file but in my config ther is no M307 with K and this is my Config-override:
; config-override.g file generated in response to M500 at 2024-04-20 19:05
; This is a system-generated file - do not edit
M307 H0 R0.123 K0.236:0.000 D11.52 E1.35 S1.00 B0
M307 H1 R2.660 K0.303:0.000 D5.15 E1.35 S0.75 B0 V23.9
; Probed axis limits
M208 S0 Z359.81
; Z probe parameters
G31 K0 P25 X42.0 Y21.0 Z2.40

The Printer is working good but message on startup is boring.
Can someone tell me where i have to search for the M307 command?

Phaedrux

@alwaysom said in Software 3.5.1 released:

"Error in start-up file macro line 5: in file macro line 5 column 17: M307: expected number after 'K'

Can you identify exactly where line5 column17 is in this instance?

JayT

@Phaedrux : done.

Phaedrux

I'm going to lock this thread now. If you're experiencing issues after upgrading to 3.5.1, please create a new thread with your issue and please include as much detail as possible.