cmcgrath5035

tinyG has outputs (3.3V logic) that control spindle on/off and coolant on/off.
You could use one of these with an appropriate level shifter circuit to drive your solenoid.
You would likely have to manually edit your Gcode, perhaps you do that already.

Or are you looking for a solution driven by Z axis commands?

periscope
This thread is sort of old. I am a linux user primarily, Win when I have to, zero direct knowledge in MacOS world, aside from knowing it is Linux-like. That is not much help when you come to specifics.
I see you making progress in search for more current support threads.
Focus there.
You need to find a path to tinyG 435.10 (or greater) and, if you want to use tgFX, build 3625.
I know you are doing that, this thread won’t help.

Gianteye
It would seem a helpful test would be to send your Gcode to your tinyG via an alternate sender. Do you have Coolterm loaded to on your control computer? If you are running Windows, you might install JCNC and try that. Or try the ChilliPepper interface.

If my math is correct, a 1/8″ diameter circle in 256 segments has a segment length of approx 0.0195mm. A 45 degree angled segment would call for relative x and y moves of 0.0138mm. Other angled segments will call for smaller x or y moves. These are likely too short for a ShapeOko setup. My understanding is that tinyG accumulates moves it can’t make until it can make a move in that direction.
But I seem to recall you have built a screw machine with better mm/revolution precision.

Alden has evaluated short move dynamics for the 435.10 tinyG build down to about 0.02mm for a ShapeOko.
ShapeOko with NEMA17s are typically 36.54 mm/rev, or 0.023 mm/microstep (for X and Y)
Your expected minimum move would then be about 0.02*YourMMperRev/36.54

All this math is of course moot if the issue is in tgFX.
But always good to have in mind the maximum precision of moves for your machine, which is the distance moved with a microstep.

I don’t have any useful G2 experience yet so can’t really help, but suggest you post what Interface OS (Win, Mac, Linux) and tool (Coolterm, putty, etc) you are using to interface your G2s as suggested next steps may be different for each environment.

Also, GREAT idea to make your configuration info available as pca did, but I suggest to post it to a dropbox(or similar) .txt file and post a link to that file.
As you can see above, the WordPress Forum tool removes whitespace from the parameter listing, making it more difficult to scan for values.
Using the code tags option in WordPress is somewhat better, but the scroll bar is all the way at the bottom on the long listings.
Here is an example (for tinyG ver 1) :

https://dl.dropboxusercontent.com/u/50261731/2014-05-31_18.28.12-tinyg.conf

When reading forum items, I frequently open the configs in a new browser tab (right click on the link) for easier analysis of the issue and configs with less scrolling of the screen..

Alas, you’ll have to wait for Alden or Rob to stop by for real help with the issue at hand.

Edit: Ha, Alden and I were typing at the same time.

• This reply was modified 10 years, 6 months ago by cmcgrath5035.

Let’s redirect this discussion to thread that starts here:

https://www.synthetos.com/topics/tinyg-connection-issues/

I have not seen this specific issue raised before.

What tinyG build are you running?
What tgFX build are you running?

If not already, you may want to try tinyG build 435.10, the most recent Edge build. It does correct some other default parameter setting implementations, might help here as well.

• This reply was modified 10 years, 7 months ago by cmcgrath5035.

TedB
1. Something is very wrong with your confgs – compare yours to this

https://dl.dropboxusercontent.com/u/50261731/2014-05-31_18.28.12-tinyg.conf

Those values may not be correct for you, but your file has numerous ‘nan’ entries that are bogus.
2. Try this: Reset tinyG (reset button) then in Coolterm enter $defa=1. This will reset the tinyG to factory defaults. Likely it will reset some values that you entered for your machine, they will have to be reentered. But should you continue to see ‘nan’ when you do a $$ dump, then you likely have a defective unit.
Reference

https://github.com/synthetos/TinyG/wiki/TinyG-Configuration-for-Firmware-Version-0.97

Assuming 2. works OK, read on:
3. Are your Limit switches really NO? NO is susceptible to noise. Try running your job with Limit switches disabled.
4. I assume you reversed the wiring on one of your Y motors, because the config says both motors 2 and 3 are set to the same polarity.
5. Your Coolterm settings “look” correct to me, but I am not a Coolterm user.
6. I would leave $?pm=0 for all motors. Should work, dissipates a little more power but that isn’t you issue at the moment.

Good Luck

• This reply was modified 10 years, 7 months ago by cmcgrath5035.
• This reply was modified 10 years, 7 months ago by cmcgrath5035.