Home › Forums › TinyG › TinyG Support › Great Hardware but…
- This topic has 8 replies, 4 voices, and was last updated 11 years, 1 month ago by Riley.
-
AuthorPosts
-
September 22, 2013 at 1:26 pm #4568InPhaseMember
I am impressed with the solidity of the hardware on the TinyG. Having said that, it is just too damn experimental and I need to get some work done. In a perfect world I’d have the time to play with the board, but I have had it a few weeks and have yet to produce anything good from it. tgFX causes the program to stall in full screen. Codes that run fine under Mach are erratic and skewed with TG. I have tried different post processor settings from Gcode ARCS to EMC2 to manually editing the code.
To top it all off, when a program finishes the run and returns to the home position, the board sets the position as some random number which I have to reset to zero every time. I have eliminated electrical interference and grounding as the problem. The codes run great on other machines. I really want to use this board, but it just isn’t as plug and play as my schedule needs it to be.
I generally use Vectric Aspire to produce my code. I need some answers but I don’t really know what questions to ask. HELP!!!
September 22, 2013 at 7:32 pm #4572InPhaseMemberOk, here is what I have found while waiting on some input:
I flashed the current dev version of the firmware and success!! Sort of. The code now executes fine from a terminal, but sadly tgFX doesn’t work, neither 2012 nor 2077. I haven’t tried the 32 bit version(s) yet. It’s great that I can run code now, but it sucks that I can’t do it from a GUI. I’m not much of a command line type. But it is sufficient for now.
I thought about flashing the edge, but got reckless and went straight to dev. I may try edge to see if it clears it all up, but that’s for another day.
September 23, 2013 at 7:53 pm #4575mcgyvrMemberGot an android tablet?
https://play.google.com/store/apps/details?id=org.csgeeks.TinyG&hl=enSeptember 23, 2013 at 9:08 pm #4577aldenMemberInPhase – thanks for your comments,and sorry you are having problems. TgFX still needs some shakeout and the new binaries need to get posted. Hopefully we’ll get through this hiccup. THanks for your patience, and I understand if you can’t integrate into a production environment until these things are taken care of.
September 23, 2013 at 10:03 pm #4580InPhaseMemberYeah, Mac, I have an Android, but the app doesn’t work with the v8 board yet. Matthew Stock (the app developer) and I have been corresponding about that issue and it’s being worked on.
Alden, thanks for the response. Tonight I discovered that the problem definitely isn’t tgFX, but is in fact in the firmware. When using either the master or edge version of the firmware the machine will produce some rather undesirable effects. And this occurs when using tgFX and Coolterm to send the file.
However, using the dev version 0.97 build 392.70, the code will run perfect. BUT only with Coolterm. tgFX will not pull data from the board at all. So whatever you did in the dev version of the firmware as far as code execution is great. I will be able to use it this way for now. It would be great to have a functional GUI, but I understand it is a work-in-progress. I have attached some pics to demonstrate the effect of the master and dev firmware.
September 23, 2013 at 10:06 pm #4584aldenMemberCan you post or email me the gcode and settings you are using (and anything else you think I might need to reproduce the problem)? I would like to find out what’s going on here so I can isolate the problem and fix edge and master.
I also suspect think might have to do with RTS/CTS flow control, which are one of the things that have changed between master/edge and the dev branch. What kind of flow control are you setting up in TinyG, and in Coolterm?
Thanks
- This reply was modified 11 years, 1 month ago by alden. Reason: added flow control para
September 23, 2013 at 10:21 pm #4587InPhaseMemberFirst thing in the morning I will get you the Tiny G settings. But I can say for sure that flow control in Coolterm is XON, with RTS and DTR set to on.
September 23, 2013 at 10:32 pm #4588aldenMemberThanks. I’m traveling this week but should be able to test it out at the end of the week or over the weekend. Can you please also include the Gcode that failed? I’d like to try to run it. Thanks.
September 24, 2013 at 6:54 am #4592RileyKeymasterInPhase,
Thanks for the replies. I am testing out a fix for tgFX tonight. Like Alden said we suspect its RTS/CTS that is set by default in all of the lastest branches firmware.
Riley
-
AuthorPosts
- You must be logged in to reply to this topic.