Topics created by audryhome

@dc42 Installed the beta, everything is fine!

M409 k"move.axes[]" f"f"
{
"key": "move.axes[]",
"flags": "f",
"result": [
{
"machinePosition": 2.652,
"userPosition": 0.102
},
{
"machinePosition": 5.511,
"userPosition": 0.102
},
{
"machinePosition": 180.17,
"userPosition": -0.03
}
],
"next": 0
}

Many Thanks!

@dc42 I did change the power to 5V and this is OK now.
Many thanks

@droftarts

Thanks again for your answer.

In fact I misunderstood the doc, since I use for years DUET2 & Octoprint and I thought the status messages seen on Octoprint were just a normal DUET output.

My mistake.

I understand M116 & M117 are just what I need for

@dc42 Many thanks for advice, will keep u posted when done.

@audryhome said in Modifying a global variable while running:

Regarding daemon.g, I think user should have control on the 10 sec delay. I understand the reason why this is done that way, but this greatly limit the usability of this interesing functionality.

Actually you have failed to understand the advice you were given.

If you put an infinite loop in your daemon.g, it does not run every 10 seconds.

; daemon.g while true echo state.time G4 S1

Would do everything in that loop once a second (plus the time to carry out the commands within the loop)

As the macro remains open, RRF won't open it again.
The reason it was changed to 10 seconds was because every time it's opened it must be read from the SD card, which impacts on other processes.

@audryhome which firmware version are you using? Please try firmware 3.4 if you are not already using it.

@dc42 Many thanks David

@audryhome if the temperature is oscillating, the usual fix is to increase the D parameter in the M307 command for the heater concerned. Try increasing it by 30%, and if that doesn't stop it, by 60%. You can send M307 with just the H and D parameters from the console while watching the temperature graph; then when you have established what value you need, edit the corresponding M307 command in config.g.

@dc42 Heater fault happens at power on only.
So far, my best remedy is to put a 30 Sec delay at the end of config.g and this cures the symptom.
Will investigate further. Possibly a config mismatch or a wiring problem, but since bed heater is also in the game, I doubt cabling is an issue since they are not running the same way on a bigbox.

@o_lampe Many thanks, as always the evidence is just in front of your eye!

@theruttmeister said in Using 2 extruder with a single stepper:

... using a single motor for two extruders is still covered

Looking at the claims of this patent, it also require that each of the two will work on a reversed motor direction, so if you find a different way, it will be a valid workaround. (not that it matter for makers and hobbyists).

Anybody knows if this design actually works and used in a product? Sometimes companies file patents just to be on the safe side.

@fcwilt Yes, I print tiny parts ( custom gears and connectors), and I need minimal entry points on my objects to allow best external mechanical interface possible.

Therefore I need to purge my nozzle between each part to ensure identical start conditions.

And since I need many parts, I stuff my printing bed with as much as possible parts.