Forum Replies Created
-
AuthorPosts
-
alden
MemberI’m afraid I can’t answer that for sure. Also, it’;s hard to get the driver ships off. You have to unsolder them from beneath first to detach the chip from the power pad. They are soldered on to the board for heatsinking. That’s what the 2 big holes are on the bottom of the board.
MemberSigh. We never had these problems with AVRStudio4. Try the code anyway. I have seen this and the code actually programmed correctly, it just didn;t verify correctly. If that doesn’t work try programming it with AVRStudio4. It’s ben removed from the Atmel site but there are still links for it. Gargoyle: Avrstudio4 links
ALso, you want the bootrst fuse to application unless you have the boot loader installed.
MemberI have a suspicion of what’s going on here. I suspect that the latch operation takes the switch to a point where it’s right on the edge of firing. Then the backoff fires the switch again and ends the backoff. I think it’s worth an experiment to lock out switch detection during the backoff and see if that doesn;t prevent this. I’ll add it to my list, or you can hack the code in cycle_homing.c if you want to experiment yourself.
MemberSorry you had a problem. We can offer you a replacement for $49.99 (includes shipping) if you return the damaged unit.
MemberThis is very interesting. Please let us know how the node.JS / rPi config goes. Can you open a Github repo for it?
Also, we have been working on the JSON for over a year and hopefully have it where we want it. Any comments on functionality, structure, ease-of-use, etc. are welcome.MemberSorry for the delayed response. Are the other axes moving? Were there any other changes to the setup?
MemberSorry you are having problems. What happens when you hit the reset button?
MemberYou are right – the cheat sheet definition was wrong. It’s been corrected.
Power remains on indefinitely. There is a feature request in to make it turn off after some period if idle time, but no ETA on this yet. I plan to do this by registering a call-back in the main loop that uses the tick counter to count a number of 10ms periods from the RTC. I welcome someone hacking the code to beat me to it.
–Alden
MemberYes. We are prototyping a version 8 board that breaks out the stepper lines to external pins. We’re probably about 2 months away from first production.
–Alden
MemberYou can find a fix in build 370.09 in the edge branch on github
https://github.com/synthetos/TinyG/tree/edge/firmware/tinyg/default/tinyg.hexPlease let me know if this corrects the problem
MemberSet the line delay in Cooterm to about 50milliseconds and try it with that. The issue is that the xmega on the tinyg needs time to write to EEPROM, during which time it shuts down interrupts and therefore loses serial chars
MemberIt sounds like you may have a noisy limit switch line. I wrote up some steps to take here:
Please let me know if these are helpful or not.
–Alden
MemberI did locate the bug. Thank you for pointing it out. I will post a new release to github once I have a day or 2 testing.
March 24, 2013 at 9:25 pm in reply to: TinyG support for Subroutine calls / O Codes / M98 and M99 #3946MemberWe currently do not support O codes and M98 / M99 calls. We do not have currently plans to implement these functions. If your application requires these functions we are happy to discuss further. We can be contacted at the synthetos gmail address.
Thanks
MemberThanks you for your post. I have reproduced the bug and will work on a fix.
-
AuthorPosts
