Mike,
Thanks for the detailed report. What your symptoms suggest is that it's most likely the serial stream is getting corrupted, and this is most likely a problem in the end-to-end operation of XON/XOFF. What the machine does after the serial stream becomes corrupted is quite random and unpredictable, so not much information there.
I (re)confirmed that I am able to run the shapeoko hello world file you provided on my setup. It runs successfully. I also confirmed that you have XON/XOFF enabled from your settings. You do. So what this tells me is that it's probably not a problem in the TinyG code, but in the upstream serial interface and/or driver.
There are some significant differences between our host environments:
- I'm running MacOSX Lion, you are on XP.
- I'm therefore running a completely different set of FTDI drivers than you are - you are running FTDI driver version 2.8.14.0
- I'm therefore running the Mac version of Coolterm not the Windows version
So over the weekend I'll try to replicate your setup as closely as possible on a Windows box I have lying around. Some questions:
- What kind of machine are you running?
- Do you have any information on the serial port and the serial drivers. See
My Computer/Control Panel/System/Device Manager/ Ports for info.
- What service pack are you up to on XP and what type of XP are you running - home? pro?
- What version of Coolterm are your running?
- Just for yuks, what COM port does your USB driver map to (although this is usually quite random)?
- Lastly, what is the behavior of the XON/XOFF LED? It's the OUT3 LED located right next to the resistor labeled R22 in the picture here:
http://www.synthetos.com/wiki/index.php?title=Projects:TinyG-Hardware-Info:#Interface_Pinouts
-- Does it flash on and off during operation?
-- When the machine goes OC is it on or off?
-- Does it not turn on at all?
The LED turns ON when XOFF is issued by the board (because the serial receive buffer hit it's hi threshold -about 200 out of 256 characters), then turns OFF when XON is received from the host. Being stuck in the ON state can indicate that the board received characters, hit the hi limit of the buffer, issued the XOFF, then never received an XON. What THAT usually means is that the host never acted on the XOFF and just continued to jam characters down the wire.
I'll reserve judgement until we confirm or eliminate XON/XOFF as the culprit, but we are finding that even though our setups work fine with XON/XOFF, some others don't. Rather than diagnose each XON/XOFF problem independently the tgFX code synchronizes on the command responses rather than relying on XON/XOFF. So bear with us a bit longer until we get that out. In the mean time, let's try to get to the bottom of your issue.
- Alden
UPDATE: Can you please confirm the release of the FTDI Drivers you are running? in the VCP driver section I only see version 2.08.24 for for the Windows x86 - 32 bit. I do not see any drivers labeled 2.8.14.0 - perhaps you are running an earlier version.
Also, please also confirm that you are using the VCP drivers and not the D2XX drivers - I have to assume that you are because otherwise you don't get a COM port, but let's just be sure.
Thanks