Snuggly's Plasma Build

snugglylovemuffin wrote: If hooking it up to a power supply doesn't work, does that mean the firmware is corrupted?

NO!
It does mean something is very wrong with your wiring and/or power supply or one of the drives or....................

In halshow: hm2_7i96.0.gpio.011 is switching between in /in_not (does this matter, am I reading the pin wrong?)

I don't believe I've tested this pin because it is the common and it didn't seem to matter. GPIO pins 0-10 are working as well as SSR relay pin hm2_7i96.0.ssr.00.out-00. (My mistake for reading the SSR as GPIO)

I believe that one of the issues was a Z soft limit of 0.25, which I have increased. The files Islander modified for me seemingly corrected this, I will check these files again to isolate the issue further.

GPIO11 is _not_ the input common pin (nor is the input common pin readable)

GPIO11 toggles because you are reading one of the SSR output driving pins (which are 1MHz square waves) so you will read random high/low values on this (and other) GPIO pins that are not associated with actual simple input pins, that is, all pins are readable as GPIO even if they have alternate functions.

You can for example also read the stepgen output pins as GPIO...

interesting. So it looks like everything is wired properly and the joint 3 limit is caused by something else.

Increasing soft limits didn't relieve the issue unfortunately. I've commented the line out for now while I figure out my z axis crashing issue.

Joint.3.limit means that the limt switch has been triggered. It might have really been triggered, or it might simply be electrical noise or mechanical vibration.

I tend to run my limit switches through a software debounce (in HAL). And quite a long one, 10mS or so.

I don't believe Snuggly has an actual limit switch on his Z axis.

The THC.hal he is using sets all three joint.3. hal switch pins to true when the logic thinks there is a Z axis error OR when it thinks the float switch (FloatSwitch) pin is true AND some logic of the M3 code (spindle.0.forward) and the torch state.

net TriggerLimit or2.2.out => joint.3.neg-lim-sw-in joint.3.pos-lim-sw-in joint.3.home-sw-in

net FloatAndTorchOn and2.5.out => or2.2.in1
#net LimitZ hm2_7i96.0.gpio.006.in_not => or2.2.in0

This is Tommy's hal so I will leave the logic functional details to him.

John