TinyG skipping gcode lines page 2

More info.. Finally got my UPS in the mail so I hooked it up to that..It ran just fine 4 times through the code then boom again..
This time coolterm had finished sending the gcode and I was actually able to see an error Its all right here. Is it "telling" of something that the system shutdown error came then a movement then again ? Or how about a -0.000 velocity..? pulling at straws..

Note it did hit a limit switch (never should have been close but when it went psycho speed mode the y axis slammed into the non-homing side limit switch. It really seems like its still trying to execute the code but when the axis goes to full speed obviously tinyg would be lost as to where it really is.

Here is what I was able to get in coolterm..
tinyg [inch] ok>
qr:1
tinyg [inch] ok>
tinyg [inch] ok>
qr:1
tinyg [inch] ok>
qr:2
tinyg [inch] ok>
tinyg [inch] ok>
tinyg [inch] ok>
posx:6.675,posy:6.750,vel:-0.000
qr:3
posx:6.675,posy:6.750,vel:0.416
posx:6.684,posy:6.773,vel:41.623
posx:6.744,posy:6.924,vel:149.636
posx:6.858,posy:7.206,vel:199.584
posx:6.975,posy:7.500,vel:176.587
posx:7.053,posy:7.694,vel:81.582
posx:7.075,posy:7.749,vel:6.660
qr:4
qr:5
qr:7
posx:7.075,posy:7.750,vel:-0.000
qr:8
posx:7.075,posy:7.750,vel:0.416
posx:7.097,posy:7.738,vel:41.623
posx:7.228,posy:7.667,vel:149.636
posx:7.493,posy:7.524,vel:199.063
posx:7.783,posy:7.367,vel:200.000
posx:8.073,posy:7.211
posx:8.362,posy:7.054
posx:8.635,posy:6.899,vel:185.016
posx:8.853,posy:6.789,vel:100.000
posx:8.922,posy:6.752,vel:12.591
qr:9
qr:10
qr:12
posx:8.925,posy:6.750,vel:-0.000
qr:13
posx:8.925,posy:6.750,vel:0.416
posx:8.936,posy:6.777,vel:45.890
posx:8.994,posy:6.924,vel:149.636
posx:9.108,posy:7.206,vel:199.584
posx:9.225,posy:7.500,vel:176.587
posx:9.305,posy:7.700,vel:75.858
posx:9.325,posy:7.749,vel:6.660
qr:14
qr:15
qr:17
posx:9.325,posy:7.750,vel:-0.000
qr:18
{"er":{"fb":370.08,"st":27,"msg":"System shutdown","val":1}}
posx:5.000,posy:8.000,vel:0.000,stat:3
qr:24
{"er":{"fb":370.08,"st":27,"msg":"System shutdown","val":1}}

and more info (don't forget to read what I've already wrote in the last 2 posts above)

Just switched my solenoid to its own power supply on its own independent circuit. So I have the 24V supply (Meanwell SP320-24) for tinyg just running the board/steppers, the 24V supply is plugged into a UPS. The solenoid now has its own 24V supply (adjustable Protek lab power supply) plugged into its own circuit. I have snap on ferrite beads around each pair of limit switch wires as well as on the DC input wires to the tinyg board. I also have .1uF caps from each limit switch to ground. Using NC "industrial" ($70/each) honeywell limit switches. Any "disabled" limit switches do NOT have caps on them. My limit switch wiring is all shielded cables with the shields tied directly to the ground pins for each limit switch and the other end of the shields (far end from tinyg) not connected.

It made it through 4 complete gcode cycles then..boom psycho speed mode again.. It "attempted" to complete 3 G01 moves during that psycho time and then tinyg went to the flashing light/reset type mode..

I will try disabling the limits and solenoids (1 at a time) on Monday when i get back to work.

What about the er message, then a movement, then another er message?

OMG..horray..party..yahoooo. I'm 99% sure I found the problem.. Noise from the Y axis (using dual motors) steppers motors.
Today I redid ALL the wiring for the machine. And this time I replaced the non-shielded wire that came with the steppers with shielded wire and tied the shields to the TinyG ground.. Well when I started it up I homed the X axis (no problem there) BUT then tried to home the Y axis and it moved about a 1/4" forward then tinyg immediately shut down and generated the er message. I screamed and said what the heck did I do this time.. Then I decided to try disconnecting the shields on the stepper motor cables from tinyg ground and the Y axis homed perfectly. So I tied the stepper motor shields to the machines true earth/chassis ground (power supply - is coupled to ground with a capacitor in side the power supply and not a hard ground to earth) and ran the gcode program 10 times without any issues at all..
Another thing I noticed now was that before I had shielded stepper cables when coolterm was sending the code to tinyG its "% completion/sending" dialog box was always showing "not responding" and it would not show the tinyg messages until it was finished 100% with the download to tinyg and the dialog went away (not knowing any better I thought this might be normal and never questioned it).. BUT NOW with the shielded stepper cables I get a true percentage of sending completion and I can see all the timyG messages the whole time its sending the file. So seems the noise was even messing with coolterm/my laptop.

I do not have the cylinder hooked up yet but I'm almost positive that the Y axis noise was the problem the whole time and not the cylinder/solenoid. Tomorrow I will hook the solenoid back up and retest sending the files multiple times..

I feel soooooo silly that I didn't think that the unshielded stepper cabling would be the problem.. SOO glad I decided to rewire everything this morning. WELL worth the $10 in shielded cables. Also so thankful for all the help Riley/Alden/Matt have provided... I was just too quick to assume it was a bug in the software...sorry about that. But I never thought the stepper motors would be so noisy. I find it interesting though that I can tie the X stepper motor shield to tinyg without problems but the 2 motor Y axis shields immediately took tinyg down.

I'll update this tomorrow when I hook the cylinders up and try sending the code again. Fingers crossed that I have NO more problems.

All is good again in the world.. Everything including the cylinder is hooked up/running and NO/ZERO issues so far.. HOORAY.. Seems it was 100% related to noise on the Y axis (2 stepper motors).
Now I'll try going back to an edge firmware so I can take advantage of new stuff there..