cmcgrath5035

I suggest you try avrdude to update FW. Follow guides here

https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware

I have not compiled G2 in a while – what version compiled for you?
You are running Edge, correct?
I am in need of updating myself.
What host OS do you compile/download from?

Can we assume you have reviewed this wiki item

https://github.com/synthetos/TinyG/wiki/Tinyg-Communications-Programming

relative to buffering and Gcode delivery? While authored for tinyG running on ‘older’, lower performance hardware, I believe the intention of the port to G2 is to maintain a common approach.
And there is the G2 wiki as well

https://github.com/synthetos/g2/wiki/Getting-Started-with-G2

While I have not implemented what you are doing, my read is that maintaining optimal planning buffer fill is achieved by streaming the Gcode to tinyG under flow management by the serial I/O. For original tinyG, that was set by $ex to Xon/Xoff or RTS/CTS, for G2 of course it is native USB.
More aggressive buffer management is implemented by the Chilipeppr folks using the queue report mechanism.

Waiting for “ok>” seems as if you are implementing a ‘robot’ that types in a GCode command, waits for it to complete, then send the next command , but to use your comment, “that’s an assumption based on no fact whatsoever :)”. It would appear that this manner defeats the concept of a planning buffer and the third order curve fitting/planning strategy. But I am way beyond reasonable assumption boundary here.

Your approach to ‘spoofing’ timyG to match up with your fixed 1/10 microstepping seems reasonable.

Guess what, I was going to ask if you were sure that tinyG was powered 🙂
Some folks assumed the USB interfaced would be PC powered.

So, having the power lead give you some trouble is good practice; the screw down blocks can be problematic, Give each lead a little tug when you think it should be tight.

Enjoy

Ah so, of course.

Have you read thru any of the G38 command discussions, particularly on Chilipeppr, where an auto-leveler has been implemented?

Try a Google search on “auto leveling tinyG G38”, lots of hits.

It seems that the basic method used is to redefine an Z limit switch to be NO, connect a wire to the mill bit and a wire to the workpiece; works fine for a circuit board target, not so much when milling wood or plastic.

Seems that might work OK when milling metal in general.
You could just hit the Z limit, shutting down tinyG, then restart tinyG and Z will be a a new zero point.
Chilipeppr is much more sophisticated – probing an area and compensating for probe variations by in-line modification of GCode.

That help?

• This reply was modified 10 years, 1 month ago by cmcgrath5035.

You may find this item helpful as a backgrounder:

http://electronics.stackexchange.com/questions/55285/how-to-safely-ground-a-switching-power-supply-with-floating-outputs

I took a quick look at a pile of in-line power bricks in my experiment stash, a collection of old laptop, router and usb peripheral power units.
Some have two wire mains cords, with non-polarized plugs, and some have 3 wire (hot-neutral-GND) cords, all output a “floating” DC voltage.

So a possible scenario is that your MAC bricks’ DC- is parasitically coupled to the hot lead while the CNC supply DC- is parasitically coupled to the neutral side, OR vice-versa.
There is no good reason to assume that the parasitic coupling is the same magnitude with the two supplies or that the phase of the parasitic voltage is the same. And, in fact, the parasitic voltage could be mostly 60 cycle harmonics or could be at switching supply frequency (typically 15KHz or higher), or a combination.

I would guess that you might get the same tingle if you were to touch the DC- lead of the 24V power supply, but the resistance of a finger touching a small screw head vs a palm resting on a large aluminum plate (your laptop case) will be quite different, as would the magnitude of the tingle.

For tinyG V8, the Motor Voltage (for you, 24V) Ground Lead becomes connected to tinyG ground, and thereby USB connector shield and ground wire.

Reference Schematics can be found here (Pages 1 and 2)

https://github.com/synthetos/TinyG/tree/master/hardware/v8schematics

If I had to guess, you will find the slight potential difference (“charge”) exists between the Negative lead of the 24V power supply and your work environment.
Possible reasons for this are too numerous to cover here, obviously include a defective power supply but could be as subtle as asymmetry in you incoming line voltage(240V AC ). Do you have an AC mains ground connected to the Power Supply input?
You could contact the Inventables folks, ask about how the 24V output is referenced to input ground lead.

There could be an issue in the MAC end as well.

Since you are running 240V input, I’ll guess you are not in North America.
Other power related issues in your area?

A suggested test: do you have a spare in-line Laptop power supply (or similar)in the 12-30 V DC range? tinyG will function over that range, but motors will probably be starved for current so don’t try to run a real job. You could substitute that supply for your 24V supply. Make sure you have the polarity correct.

Without saying, be careful. If you are unsure what you are doing, perhaps a local computer repair shop could evaluate the 24V supply output for foreign voltages.

I generally run my CNC equipment in my shop (North America, 120V) connected to an in-line Ground Fault Interrupter (GFI), which will help protect yourself, but won’t “fix” a defective supply. Always a good option if available to you.

As the guy who taught me TV repair back in the 1960s said, when “working on exposed circuits, when in doubt, keep both hands in your pockets – don’t touch anything”.

Your fan issue – Jumpers set correctly for 12 or 24V fan? see

https://github.com/synthetos/TinyG/wiki/Connecting-TinyG