@gruen Try this release: https://github.com/Duet3D/RepRapFirmware/releases/tag/3.3beta2

Actually, this was already there in 3.3b1 🙂

Running it without the X goes through, but there's no backlight.

And with IO0 in config.g, the probe works ... for now. IO1 is still not working.

@carcamerarig see the guide here about file locations, but remember this is in standalone mode: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_File_locations_on_the_Duet_SD_card

As you have Mini 5+, you can always update via USB using this method: https://duet3d.dozuki.com/Wiki/Installing_and_Updating_Firmware#Section_Duet_3_Mini_5_WiFi_Ethernet

This guide has only recently been updated, so it may change. I’ve removed the ‘location’ part in “ You will get a message if it is missing, with the filename and location it expects” as it does not tell you where it expects the file to be, though I will suggest it!

Ian

Out of curiosity - do you get the same if you disconnect the PT100 board and connect the DHT to the duet directly?

Thanks. It's normal to get one write error per driver the first time you run M122 after power up or reset. Running M122 clears the error counts, so they should read zero after that unless you get a VIN under-voltage event.

It's a new error in 3.3b2 -- it worked fine in 3.3b1. And the maxiwatt is very compact and heats up fast, it's not like there was a plateau.

I just started a longer print, but after that finishes, I can try again and post the temp graph that shows the heatup is not plateau-ing. I also don't get the usual error message about the heating being too slow or anything, just straight heater fault.

Excellent help, advice and support from the forum, big thank you from me to everyone that helped. 🙏

I am not saying you're wrong. I just don't feel qualified to say I am right either.

@tekkydave said in RRF 3.3beta2 Macro Parameters:

Is this just a consequence of it is not yet being possible to query a parameter name to check whether it exists?

Yes.

@dc42 yes, it was different on previous versions.
I was using minX/maxX etc in homeall.g and bed.g to calculate the centre of the bed and the extremes for twin z level.
I can hard code these, but the code was portable before.

@dc42 I will give it a try tonight and reslice something. The same gcode did work on 3.2.2 though. I did reslice using same settings but that did not help.

It's moved. Go to the System page, click on System Directory, and you can select the menu folder from the dropdown list.

I am currently looking into a CAN driver bug in 3.3b1 that might explain the CAN errors. The bug would cause a task that is sending messages over CAN to lock up. Possibly this might cause a problem with SPI comms too, I don't know.

I confirm that the 12864 encoder does not work in RRF 3.3beta1 for the Maestro. I will fix it in beta2.

@oliof said in 3.3b1 SBC print time/filament usage: MatterControl:

MatterControl has yet another way to mark print time and filament usage estimation. I have included a file to look at for @chrishamm (-:

sample_cube_MC.gcode

Now added to the 3.3beta RRF source code too.

a2244e84-ea55-4bb4-90cd-34a6c886114d-image.png

I cannot get it to run on Linux so I won't focus on adding support for this to DSF. It should be quite straight-forward once you can configure it to output the filament usage in mm or m and to generate the layer height in a comment.

@oliof said in 3.3b1 SBC Ideamaker print time and filament usage estimates:

Hi @chrishamm,
attached is a file sliced with Ideamaker 4.0.1 (latest stable release).

In the DWC job list, layer height and print time estimate by the slicer are not shown.

sample-cube-ideamaker.gcode

I have confirmed that this file is correctly parsed in standalone mode. Layer height is not provided, but RRF does not use it.

17c0c487-00e0-4c54-9571-8ad1daf98ed5-image.png

@oliof said in 3.3b1 SBC KISS slicer filament usage and print time estimates:

Hi,
KISS Slicer 2.0 alpha 6 filament usage and print time estimates aren't detected by 3.3b1 in SBC mode.

Attached is a sample file so filters can be adjusted.

(I guess this goes to @chrishamm again)

sample_cube-KISS.gcode

I have confirmed that this file is already analysed correctly in standalone mode.

d971b9df-d997-4a58-8c71-79d0611d9382-image.png

Done in standalone mode:

0074ca6f-1092-4a91-aa54-62a6c8a4097b-image.png