Forum Replies Created
-
Well, unfortunately, it is hard to tell what you are doing.
First, tinyG is a V8, loaded with build 412.XY ?
Also note that build 429.01 is now available and is a more up-to-date EDGE version.
You are running your gcode with tgFX? What version (build) ?From your description, it worked runs 1 and 2.
Do you reload material between runs, or just rest a zero point on one piece of material?Significant power dips could be an issue, as could excessive noise from spindle(or vacuum) on the power lines.
If you are pushing your gantry around by hand, to load new material or etc., the motors could be inducing noise back into tinyG.
When I run jobs, I set my zero point, with cli commands or jogging, then reset tinyG (reset button) before starting the Gcode run.
Interesting. Are you sure that the frame of the power supply is actually connected to anything? I think normally it would be the third wire of the AC inlet, which your don’t have.
I have the shields connected to DC- at tinyG, but there is no guarantee that is the best solution.
Conducted (powerline) emissions can be real tough to diagnose, even in a three wire world., Power supplies, to meet FCC rules, should have reasonable outgoing (conducted back on the input mains) emissions, but those mitigation techniques may be compromised in your two wire environment.
Most all power supplies are now electronic AC to DC converters. Might be interesting to try an old linear (transformer) supply,if you have one or could borrow. Know anyone into Ham radio? Those folks frequently have power filters in their experimental bag of tricks.
The power LED, Motor LEDS (brief slight motor humming in startup only) all shine. The TX/RX never do. Also the board will not power up via USB port.
When connecting to 24vDC the spindle light flashes approx 12 times. Then green motor lights shine for about 2 seconds and the motors hum. Then the power light stays on steady.
All the above looks correct. You can’t power tinyG from USB.
The 12 x flashes of the spindle are the bootloader. When done booting, TinyG starts with all 4 motors held in current position (the hum you hear) for a settable period of time(depends on Motor Power parameters)
If you purchased about 6 weeks ago, you likely received a V8 unit.
Please verify. Might possibly be a V7; silkscreen on the pwb.To debug your connection issues, we need to know what OS (Win, MacOS, Linux) you are using.
Did you read the section on the Wiki about needing FTDI drivers (FTDI is the supplier of the USB device used on TinyG)? Read thru this if not:
Hmmm, I am not 100% familiar with V6 hardware, but some observations and ideas that might help.
Your CoolTerm issues might be caused by a flow control mis-match?
Check the flow control state in tinyG, parameter $ex.
Set same in CoolTerm. The most recent tinyG FW builds use RTS/CTS. I have no idea what your FW might specify.tgFX might not be of much use to you until you get your FW updated.
The most functional versions of tgFX require FW 412.1 or higher.
I believe you are correct – that tgFX uses the bootloader to do its upgrades so that will not work for you.
And, the tgFX-tinyG interface only works when tinyG is 412.1 or higher.I have had good luck updating FW using AVRDUDE on Linux.
I never bothered to get Coolterm working on Linux
In this thread I describe using putty and plink for gcode sending
See if any of this helps.
