@T3P3Tony - I have a little update on that. There were enough parts to print and of course I ran out of filament. In the meantime, I received the new 6HC v1.02. I upgraded from v1.01 28V supply voltage to 45V. The filament arrived and I continued printing. The error no longer appeared. I have no idea how much difference there is in the FW for version 1.01 and 1.02, but maybe it will help you in your search.

20230321_195946.JPG

@PetrKroupa Thanks for reporting this, I can confirm there is a problem in 3.5b2. It will be fixed in the next beta.

@MintyTrebor Thanks, I've changed registerCategory in the 3.5 branch to wait for the DOM update.

@Acid Another explanation is that none of your M568 commands have a "P" parameter to specify which tool the rest of the command refers to. If no "P" parameter is given, the firmware might default to using tool 0, but then again, it might not. Assuming you only have one tool, I suggest you try adding P0 to all of your M568 commands. Let us know how you get on. Another suggestion is that you add M400 after your G1 E-620 command. This will ensure that the move completes before turning off the tool. Also, it might help if you told us exactly how and where the macro fails. You can debug it yourself by sending one command at a time.

@Acid said in Wrap text on 12864 displays - 3.5b2:

Hi OwenD, I tried this out but for me it only shows line one with the example. Also, S should be P 😉

Yes I tried also with same results
The parser no doubt strips out the new line command and anything following

Would there be anything else we could try?

Nothing I know of.
Would require firmware changes, so one for @dc42

@dc42 said in QOI image from PS 2.6.0-a4 aborts print on RRF 3.5.0b2:

Have you already posted your start.g in this thread? If not, please do so.

Here you go:

; start.g v1.3 ; Called whenever you start a print, run before slicer gcode at start of print echo "start.g start" G21 ; Set units to millimeters G90 ; Use absolute coordinates M83 ; Use relative distances for extrusion M140 S65 ; Set bed temperature to 65°C if exists(global.sb_leds) set global.sb_leds = "heating" ; StealthBurner LED status T0 ; Select Tool 0 M291 P"Print started, preheating." T10 ; Info message G4 S1 ; Wait 1 second M220 S100 ; Reset speed factor M221 S100 ; Reset extrusion factor M290 R0 S0 ; Reset baby stepping M107 ; Turn off the part cooling fan if heat.heaters[0].current < 65 M140 S65 ; Set bed temperature to 65°C M116 H0 ; Wait for the bed to reach its temperature echo "start.g end

@vijays I also see this post:
https://forum.duet3d.com/topic/31649/duet-3-board-gpio-input-heater-control/3

I assume they are related?

@MaxGyver

I just noticed that for G32, G30 and G29 the probe Z-offset is applied AFTER the first probe point has been probed. All succeeding probing moves use the correct offsets. 😕
I am on RRF 3.5.0-b2+

@Marcossf you can also share a zip of the /sys directory and and other macro directories. If that's sensitive information then we can arrange to get it another way

@kuon you may be ok. It certainly won't damage anything but you may find the odd other feature that doesn't work

@Adrian52 just for info if that can help, you can use M302 P0 S0 R0 in the mean time.
@dc42 Thank you very much for the tremendous work.

@Exerqtor thanks for reporting this. I've added it to my list to investigate/fix before the next beta.

@dc42 said in 3.5.0-b2: Bed shut off during print:

@CCS86 regarding this:

if heat.heaters[0].current < 60-1 M190 R60 ; Wait for cold bed G4 S240 ; Cold Pause else M190 R60 ; Wait for hot bed <<<<<<< G4 S1 ; Hot Pause

The M190 command with the "Wait for hot bed" comment wil be ignored because it needs to be on a separate line, not on the same line as the 'else'. I will change the parser to generate an error message when there are unexpected characters after 'else'.

Great, thank you for that correction!

The bed plate acts as a heat sink/heat spreader for the heater. If part of the heater separates from the bed, that part gets extra hot. Here's what happens to the heater when the 3M adhesive starts to let go:

alt text

Good morning,

Thank you very much @jay_s_uk, the problem is indeed solved.

Best regards

@Proschi78 there has been no intentional change to the stepper motor configuration default values since 3.4.

@droftarts said in Endstop indicator on Y axis not working in DWC 3.5b2+1:

@OwenD It's working for me (Z also >works) with nearly the same setup; >3.5beta2+, but build date is different:

I built from source which explains why my build date is a day later.
There appears to be something really weird with my end stop.
I just ran multiple home Y moves and occasionally the indicator works.
Can only assume that somehow it's triggering then breaking contact??
I'll mark this as solved.