alden

@psyko – You are essentially correct. But I’m not sure why Tom’s getting that movement in Y; at least not that particular move that goes to 180. What I was going to do with the code is (1) confirm proper operation of the Gcode file as a start (and generate line numbers so it’s easier to debug), (2) reproduce Tom’s steps to see how Y movement might occur, and (3) see if I can come up with a procedure / documentation for stopping and restarting a job under coolterm – albeit probably restarting from the beginning.

• This reply was modified 10 years, 9 months ago by alden.

This page may be helpful, particularly the part on flow control. I don’t have time for a full answer right now – read this then I have some other ideas that might help.

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

Good suggestions. Let me think this over and talk with Riley. I agree, we need to find a cleaner way to make things available.

Some of the challenges are that github does not easily deal with binaries or hex files, it’s designed for sources and they structure it so it’s difficult to manage anything else. So already we need 2 mechanisms.

The wiki is needed as it’s the documentation.

Another is that the terms Master and Edge are, in fact, meaningful in themselves. We will THINK we have all the issues addressed when we push to master, then find that there are 1 or 2 bugs that need to be fixed in master – e.g. the promotion from 380.06 to 380.08, both of which are in master. We also do need to isolate the Edge builds from master so we can iterate them without affecting the master. What we probably should do is ALWAYS state the build number, whether it’s in master or edge (or sometimes dev).

As for the Forum, I have to ask Riley – he manages that part. We could possibly move the forum from here to the Github Issues, but that’s not really it’s intended use – although a lot of projects use it as a forum and it seems to work OK.

Let me talk this over with the team and see what we can come up with.

Tom,

Let’s try to tone down the rhetoric and try to solve your issues. We have been answering your posts and fixing your issues for over 2 months now, as you can see from your digest:
https://www.synthetos.com/users/tomking505/topic/

The clunk.
The clunk you experienced in build 380.06 has been fixed in later releases, which are now in the edge branch. At your suggestion we have revised the firmware flash page here:
https://github.com/synthetos/TinyG/wiki/TinyG-Updating-Firmware

We are currently testing this issue in the Edge branch. The edge branch is a release candidate for master, and is not normally to be used for production operations. As soon as it passes all tests (including working with tgFX), then it will be promoted to master.

Gcode running once fine then others it messes up.
We have said that noise was most likely your problem, most likely spindle noise – in our experience.

When a DC motor like a spindle starts spinning it CAN cause a huge amount of electrical noise. Some motors are MUCH more noisy than others. You stated that sometime TinyG works fine then on the same Gcode it does not. Your symptoms are a CLASSIC EXAMPLE of electrical noise or possibly some other corruption on the USB line.

This may or may not be the case in your situation, as you have stated the spindle line is isolated from the other power, but to be thorough we need to test this.

Lastly, there’s a question of if you are having problems because of something in your host program. tgFX Master works with TinyG Master. If you are using tgFX you should be using the 32 bit version with master (We removed the x64 windows version that you and other were having issues with). tgFX(32bit) should work just fine with master. HOWEVER, if it does not we need to know about this. So please let us know.

Can you answer a few questions to help diagnose these issues:

– What computer and OS are you running
– What FTDI drivers / versions are you running?
– Are you using a USB hub or are you connected directly?

– We changed out your USB cable earlier. Try another USB cable. Sometimes it’s that simple. We are looking for anything that might be causing communications errors.

– I see your settings here: https://www.synthetos.com/topics/slow-in-the-corners/ Are these still the same or have they changed? I believe we changed your junction deviation to something larger when you were having problems with slow corners.

– What are you driving TinyG with? Coolterm? tgFX? Something else?

– If Coolterm have you enabled XON? I see from your settings in that you do have XON enabled in TinyG

– If you are running tgFX, what version? Is it 32 bit or 64 bit? Do the same files run OK from Coolterm?

– Have you tried running the same Gcode files that are having trouble with no spindle running (dry run). Do you have the same problems?

– Can you please post all the Gcode files you have trouble with? You posted one and that was helpful for diagnosing the arc move.

– If you have three TinyG’s are you experiencing the same behaviors on all three?

– Try turning off your status reports. If the serial IO system is having problems perhaps the text return from status reports is affect it.

– When you were running these files had you homed the machine? Have you had any issues with homing?

– Do your motors run reliably at the maximum velocity, feed rates and jerk settings you have set? Try reducing them and seeing if you have the same problems (this is less likely, but it may be worth a try)

– Another possibility is that your power supply is collapsing under load. What power supply and motors are you running?

— Thanks

I appreciate your pitching in. You know, we work very hard on this and it’s quite disappointing when people are not satisfied. We are not getting rich off this, and it’s not our regular jobs. Any help we can get is much appreciated.

🙂

The .hex file is on the edge branch in the github:
https://github.com/synthetos/TinyG/tree/edge

in the firmware/tinyg/default directory. Don’t worry if you looked for it before and didn’t find it, I just added it back in. Also, I expect another push to edge in the near future – perhaps as early as this weekend.

Can you please tell us what firmware build you are running and post your settings? Thanks