Forum Replies Created
-
AuthorPosts
-
cmcgrath5035Moderator
Good news, thanks for confirmation that wiki works
cmcgrath5035ModeratorThere is a confirmed bug in 440.16 (maybe 440.15 and 440.14 as well) that requires a tinyG reset to use a new $_tr (or $_sa) value. Since it is a bug, perhaps there is another mechanism that causes the new value to become active, explaining your “spontaneous” fix.
Keep an eye out here for fix :
cmcgrath5035ModeratorYes is is a pain, but you are clearly ahead of most who wonder who this dude avr is anyway.
Good luck with your projectcmcgrath5035ModeratorI would agree, 5A should be plenty for PCB loads.
Enjoycmcgrath5035Moderator2 for 2, great news.
Keep it simple, make a donation to your favorite local charity.I am glad we finally have a proven solution for you guys, I wish we could figure out why tinyGUpdater fails for you but works for others.
cmcgrath5035ModeratorI am not exactly sure what you plan to do to create 24V from a server supply, 30A is way more than tinyG can control and way more than the steppers can dissipate. If you are thinking to put 12V outputs in series, that may or may not work due to indeterminate ground references. Depends on power supply; a user recently fried his tinyG when he connected 2 12V power bricks in series, and tinyG ground ended up 12V higher than his PC chassis, buring up his USB cable. Know what you are doing.
Review this for explaination of Power Trimming:
cmcgrath5035ModeratorCool, thanks for the confirmation!
cmcgrath5035ModeratorTravel: Did you try the avrdude procedure in the Link above?
The blinking LED confirms that your board has a bootloader and should update with the described procedure.
cmcgrath5035ModeratorFYI have a look at
Someone who seems to be having some Win10 success
cmcgrath5035ModeratorOK, head to this thread over at Google Groups.
It was much faster to build the thread there – friendlier GUI.
Good luck, report results please
cmcgrath5035ModeratorLikely contributing, you need to get to fw 440.16.
G38.2 was very young way back then.Give it a try, if it fails for you, check this thread tomorrow AM
Reminder: you will have to reenter all your parameters. Make a copy of what you have. 440.16 will likely introduce a couple new parameters.
cmcgrath5035ModeratorGotta go out to the airport, check back sunrise Friday for an annotated How-To get avrdude to work for you.
Both Windows, correct?cmcgrath5035ModeratorOK, gotcha I guess. All that output is for the probe, first line of Gcode.
I need to read up on G38.2, don’t have time at the moment.Please respond with your FW version, in case we are chasing a defective G38.2 command implementation.
cmcgrath5035Moderator
I have a V8 board and .10 FW loaded and I am trying to get an NC file to do the probing. I am using JCNC at the moment which has very little support out side of sending Gcode.
There is no 0.10FW (that I am aware of), as of today the tinyG Master build is 440.16.
Please report value of parameter $fbThe last time I tried JCNC with fw build 440.14 I got nothing, I assumed JCNC no longer worked, so I am surprised you are getting anything. Perhaps that was an issue on my system
It would help deciphering the CoolTerm dump if you turned on “local echo” so that the commands you enter would show up in the dump.
PS
Misteaks? Not me, that is just a pile of scrap lumber over in the corner, all cut into little pieces.cmcgrath5035ModeratorG0 X0.001 is likely too short a distance to move (or try to jog with CP.
Try G0 X5.0, get movement?
-
AuthorPosts