Topics created by niocio01

@niocio01 I've not heard anything at the moment. Most work has been going into the new input shaping for 3.6 on both mainboards and expansion boards

@timschneider thanks for pointing out the bug in RRF when you try to set a variable to that very large value. I will fix it in the 3.5 source code.

I suggest you use

var testVar1 = null

instead.

@niocio01 said in Allow subfolders for config files:

Is this also true for the "TriggerN.g" Files?

DC said no, so what do your your trigger files look like? Could you use conditional gcode to make one "universal" triggerN.g?

Allright, bridging the Top Pin (NC on the PCB) to the bottom one (io3.in) did the trick.

I had to invert the signal but other than that no changes were necessary on my firmware configuration.

For future reference and anyone who is trying to do something similar:

M950 J1 C"!^100.io3.in" ; Tool1 docking detection GPIO setup

Is the command I use now.

@niocio01 unfortunately, Neopixel strings don't support setting just some colours. So you need to send the commands for all the LEDs that you want to change. You can either write a macro that computes and writes the correct colours for all 4 tools and call that every time the status of a tool changes, or you could use global variables to record the correct colour for each tool so that you don't need to recompute it each time.

@gloomyandy Yes. I get it only once, when I turn the PSU off, which I expected.
It's not a big deal, just a minor annoyance.
I just wish to keep my logs clean. 😉