Topics created by Festivejelly

@gloomyandy Not the case here as it retracts and Zhops to the beginning of each line. I suspect it to be an issue with the hemera XS. I havent used this printer in like a year and put the new hemera XS on it to reduce the weight. Ill try some of the other tool heads to see if they have the same issues.

It happens even at very slow speed.

@Phaedrux I think it was 3.4.3 ill need to hunt around in my files but I dont think the binaries are named by the version so might be hard to tell.

I upgraded the version to use the duet accelerometer which ended up being a dud anyway, wish id stayed on the version I was on!

Ive rolled back to an older firmware version and it seems to be printing better now but the ringing is all over the shop even with input shaping. I wonder if the input shaping is actually causing this.

Im not entirely confident in the input shaping values from the sensor tbh.

@Festivejelly Have you made any progress on getting your accelerometer connected? Do you have a PanelDue connected? If so, are you using both cables (ie ribbon and 4-wire)? @myersm1234 found in his thread https://forum.duet3d.com/topic/35460/accelerometer-not-found-on-specified-port/33 that disconnecting the PanelDue ribbon cable fixed it for him, though I was not able to replicate the problem in my bench setup.

Ian

@festivejelly

You could cycle through them with something like this
Note untested and assumes each tool has a filament monitor and is numbered the same way. ie T0 uses sensor 0

Edit:
The original code would select each tool in turn that had filament
A break command is needed to just select the first that has filament

while iterations < #sensors.filamentMonitors if (sensors.filamentMonitors[iterations].enabled==true) && (sensors.filamentMonitors[iterations].status=="ok") T{iterations} break

@festivejelly adding a search function is a good idea. I will move this to the wishlist.

@festivejelly please send a picture of the temperature.graph when this is happening and the errors you get in the console.

@fcwilt Fair points there actually I could simply that and probably remove some info. Or maybe just hash the string lol.

Thanks for the update.

@festivejelly Have you tried setting M111 for gcode (and possibly some of the other options)? I think you will only get the output via the USB connection, but it may give you want you want.

@generisi said in Firmware install from scratch:

@Phaedrux , how do I untangle a mix of RRF 3.2.2 and 3.3 ? My goal is 3.3 but the printer is behaving strangely and the web interface and the Paneldue are not working fully correctly?

Depends what you're running. It would be best if you started a new thread with your details.