Topics created by Markdnd

If you have a smart phone (Iphone or Android) there is a free app called Feeder that you can use to subscribe to the atom github feed (https://github.com/dc42/RepRapFirmware/releases.atom), and then when it changes you'll get a push notification to inform you of new firmware.

Sorry it was me being stupid.

My xy move speed was set to 300mm/s which was causing missed steps.

I've set mine to 5 taps, but if the first and second agree it moves on, and so far they always have using Piezo20 probe units (I'm using 0.03mm tolerance on that particular machine as it is not very precise, I am using 0.01mm tolerance on my delta with smart effector and sometimes it needs to probe 3 times to get agreement, but that's 10 microns, so I think its pretty good). Yes its slower than 1 tap probing, but this feature reduces the risk of a bad calibration/levelling, which does not stop or pause the print resulting in a bad print or a head crash, and this risk is greater the more automated and less attended your printer is.

It's a good idea, but then being able to quickly edit a config and restart, without having to reupload firmware like on arduino 8 bit boards is a big step forwards.

If your machine were a production unit and you were an oem you would provide a pre-configured machine and only issue very carefully tested firmware updates.

Making our own machines and configuring our own firmware implies a degree of being hands on, understanding the machine and firmware and reading the release notes.

That’s where the cluster size makes a big difference though presumably you don’t have enough spare RAM to hold even one 64k cluster let alone the 2 or 3 you’d need to cache the cluster table for an 8Gb drive.

Working with tablets and desktops I’ve been spoiled and almost forgotten the joys of trying to cram an operating system and application into what is basically a glorified oven timer.

Honestly, this is the easiest way to do it.

https://www.prusaprinters.org/color-print/

Upload your sliced gcode and tell it what layer you want to pause at. It adds the pause gcode. Then you can have a macro to unload and load your new filament and resume.

The issue doesn't happen consistently and the same file could stop and start quite happily one day and fail the next.
One thing that may (or may not) be relevant is that I've only seen it happen on larger files so far (typically 15mb or bigger)

The files you asked for are:

My Cancel.g is the factory default empty one:

; stop.g ; called when a print is cancelled after a pause.

One G code file that I had the problem with is this one:

[[Language]] ; G-Code generated by Simplify3D(R) Version 4.0.0 ; Feb 26, 2018 at 1:27:08 PM ; Settings Summary ; processName,Process1 ```This is followed by about 200 lines of comments from Simplify listing all its settings plus its life history before we get to the actual code:

[[language]]
G90
M82
M106 S255
G4 P500
M106 S0
M140 S60
M190 S60
G28 ; home all axes
;G29 ; run auto bed levelling routine
M109 S180 ; heat extruder to correct temperature
G92 E0
G1 E-8.0000 F4800
G1 Z0.600 F6000
; process Process1
; layer 1, Z = 0.100
T0
; tool H0.100 W0.480
; skirt
G1 X-35.752 Y-17.500 F18000
G1 Z0.100 F6000
G1 E-0.0500 F1440
G92 E0
G1 X-36.241 Y-17.989 E0.0138 F3000
G1 X-36.302 Y-18.060 E0.0157
G1 X-36.820 Y-18.774 E0.0333
G1 X-36.870 Y-18.854 E0.0352
etc.

There then follows about 18mb of G-Code before we end with:

[[language]]

G1 X8.963 Y31.464 E1.1401
G1 X8.659 Y32.316 E1.1581
G92 E0
G1 E-8.0000 F4800
; layer end
M104 S0 ; turn off extruder
M140 S0 ; turn off bed
G28 ; home axes
M84 ; disable motors
M107; turn off part cooling fan
M81 S1; Power off after cooldown
; Build Summary
; Build time: 2 hours 56 minutes
; Filament length: 15021.0 mm (15.02 m)
; Plastic volume: 36129.70 mm^3 (36.13 cc)
; Plastic weight: 45.16 g (0.10 lb)
; Material cost: 2.08

I was having WiFi issues at the time so that may have a bearing.

Since the errors are being detected and don’t seem to be affecting normal operation I think I’ll just keep an eye on it for now and maybe take a couple of standard anti-interferance precautions (screening the interface cable, checking its routing etc.)

Thanks for the swift response (as always)

Thanks.

Knew I’d seen it somewhere.

Pid matters more the more powerful the heater relative to its area, so for a pcb heater 200x200 running on 12v drawing 9A the bed will struggle to get to temperatureand it will heat up slowly, bang bang is fine. If you have a much more powerful heater then bang bang would cause big oscillations at the set temperature.

When you’re dealing with high currents “simple” is a bit of a relative term. Resistance has a nasty habit of changing as things heat up. Admittedly it goes up for cheap copper heaters so a cold measurement would suffice for a safety check.

Having said that, insulation is a bit of a relative term when dealing with cheap imports.

DC is, of course, right though - current measurement is definitely a nice to have and almost certainly not worth the additional cost.

Nice to see somebody actually did it. Thanks, Kraegar!
Good to know.

Just a single SSID but I suspect it may be a bug in the wifi router firmware because I always have to restart both the router and the Duet to get a connection.