-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find a tool which sends gcode files to the firmware #15
Comments
Sorry, it loads them ok but when I click "print" it says:
|
Trying w ubuntu 12.04 64bit (in vmware fusion)
Unplugged and replugged arduino usb. Fusion ask me where to connect and I said linux.
It failed. I see the arduino communication light blink but pronterface isn't able to connect. |
http://www.repetier.com/documentation/repetier-host/ looks pretty awesome so far. Might be mac-only. |
I can't get pronterface or repetier to run gcode files although both have their uses for manual control. I like repetier better for almost everything but am still using pronterface to manually send gcode. There are also potential problems with gcode generating tools in that they spit out gcodes that marlin doesn't understand. My new plan is to hand write gcode for a simple plate and manually send it by copy pasting through pronterface. This is scalable enough to get us to the point where we can cut warehouse pieces. We can work out the kinks with the more sophisticated software for a later milestone. I'll leave this ticket open for the current milestone to figure out some way to stream gcode to the firmware, even if it's a simple command line tool. |
Jesus christ, I've tried about 10 programs and can't get any to work. |
A quick look seems to show that some of these programs assume the firmware will execute the move before responding with carriage return or line feed or whatever. Maybe marlin's responding immediately? |
Once I get some known working gcode, I'll put it here for use as a test file.
See http://opensourceecology.org/wiki/GcodeCommunications
The text was updated successfully, but these errors were encountered: