Topics created by baird1fa

@baird1fa for smoothly accelerating or decelerating motion the time t of the nth step pulse measured from the start of the move is given by this formula:

t = t0 +/- sqrt(q + p * n)

where p = 2/a, q = t0^2

where t0 = -u/a, a is the acceleration and u is the initial speed.

@baird1fa they are a fixed (or nearly fixed) width with a variable space between them.

@baird1fa that is documented here: https://docs.duet3d.com/en/User_manual/Reference/Gcode_meta_commands#expressions

It’s because standard Gcode uses brackets for commenting.

Ian

@baird1fa See: https://docs.duet3d.com/en/User_manual/Reference/Gcodes#n-line-number

I found my issue, I was using a M21 where I should have had G21 to put the macro into mm.

@baird1fa that is correct, the inches/mm setting is saved on entry to any macro and restored when it exits, along with some other parameters e.g. the feed rate and whether distances are absolute or relative. So you can safely use G20 or G21 at the start of your macro to ensure that movement commands in the macro are always interpreted the same way.

If you do need to detect whether inches or mm are being used, this is set separately for every input (so a job that changes the units to inches won't affect the behaviour of the jog commands in DWC or PanelDue). The current setting can be found in the object model as inputs[N].distanceUnit. The value of N for the input making the query is state.thisInput. So you would normally request inputs[state.thisInput].distanceUnit.

@T3P3Tony The issue seems to have resolved itself. I connected it via USB and ran the M552 and M587 commands and could see that it was connected. I then powered it up normally and I would stay connected. I think there must have been an issue with too many devices connected to the wifi or an issue with IP address assignments. but it seems to be fine now.

@baird1fa on tablet/phone, try:

http://cncrouter.local/

Ian

@baird1fa If you are still looking for the upgrade, I'm happy to share with you my configuration files.
I am running my Troodon 300 with pretty much default hardware, expect that I have upgraded with direct drive.
My RRF firmware is 3.4.4

@baird1fa, @gloomyandy is correct. I will fix this in RRF 3.4.2rc2.

@phaedrux I was messing around with that because if I used the parameters that the system auto tuner calculated the Heater would fault because the temperature was rising too slowly and then give an expected value that was negative, and the actual value that was even more negative. I could try running the auto tuner again but it take 16 hours to complete on this system.

@baird1fa said in Global variables stopped working:

@fcwilt @Nightowl999

These would make excellent additions to the documentation on how to use variables. The examples of how to use them are not the clearest. For instance the use of the space rather than the "." I really struggled with this. I ended up assuming that I needed to use set for global variables whether declaring them or just using them. I kept getting an error for G (lobal) not a valid command.

I forgot to mention: I put all of my global variables in config.g so they are ready to use right after the printer is powered up or reset.

Frederick

@baird1fa that looks OK to me, except that you will need to set the A motor current in the M906 command.

@owend said in Input debounce setting:

G4 P10 ; delay 10ms to debounce if sensors.filamentMonitors[0].status="ok" echo "switch bounce detected - error cancelled" M99 ; break out of macro if sensor value is zero again (bouncing)

This seems to have worked. I haven't fully tested it yet, also I needed add a filament-error.g where I put this code (incase someone comes across this post in the future) I was just using the pause.g for the filament runout.

@phaedrux Good to know. Thanks.