Dan
Forum Replies Created
-
AuthorPosts
-
DanKeymaster
Thanks Dirk. No need to repost the code here. I’ll follow up on Github, which sends me notifications when people post issues there.
DanKeymasterThere was a bug in Right that was going way too far. It will be fixed in the next release on Monday.
You’re right about the version inconsistency. The v1.4 is the source code version. V6 is the EEPROM version. The difference is really esoteric. I will find a way to make them match so it makes more sense. Probably the next official version of the firmware will jump from 1.4 to 7.0.0 and the EEPROM version will also be 7 so they match.
DanKeymasterSome versions of Arduino software do treat the command
#include <>
the same as the rest.You’ll have to move the two ./AFMotorDrawbot/AFMotorDrawbot.* files to ./ and change the line that says
#include
to
#include
DanKeymaster>My friend change the CLOCK_FREQ the 16000000L to 36000000L, and MAX_COUNTER the 65536 to 955536L and velocity of stepper motor more low and the precision of draw is very better, but i think that it is no good idea.
I have never tried this. I have tried 2x CLOCK_FREQ (32000000L) which made the machine 2x faster.
DanKeymaster> the software is superb..
Thanks!
DanKeymasterIt doesn’t occur here when we upload firmware into new robots. :T
DanKeymasterTry like this:
DanKeymasterYes, you need to synchronize. That is what the “set home” button does – it tells the software that the pen holder is at the location on the screen. you can use the calibration.pdf (https://github.com/MarginallyClever/Makelangelo-software/tree/bb690393628b8442c9e740018b6a7bed16c3ade9/calibration%20pattern) to line up the pen holder with the software. I did not include the paper instructions in the video for the 2.5, I have to edit and re-upload it.
Machine width affects all the math for triangulation. Much more than wire length. Machine height also affects position of paper.
DanKeymasterDanKeymaster“m4 calibration.pdf” is included in the download zip file. Print it without scaling.
Position the paper at the top center of the board.
Move the pen holder until it matches the outline of the pen holder on the paper.
Set Home.Done!
DanKeymasterupdated. I replaced ‘d’ with ‘step_delay’.
DanKeymasterTry this version of the firmware:
https://github.com/MarginallyClever/Makelangelo-firmware/blob/master/firmware_ams/firmware_ams.inoDanKeymasteradjust the feedrate above the manual driving buttons. type in a new number and click “set” next to “engage/disengage”. then moving the pen holder with the buttons should be visibly faster or slower.
DanKeymasteryou can set the feed rate to be lower than 3500 and you should start to see a difference. The max speed bottlenecks in the AF_stepper library, but anything lower than the max should make a difference. Try 700 and see what happens.
DanKeymasterHi Phil,
In the top of the Makelangelo-firmware you’ll find
// Marginally Clever steppers are 400 steps per turn.
#define STEPPER_STEPS_PER_TURN (400.0)Change 400 to 200 and that should scale things down.
The top speed of the AMS1 and AMS2 boards is about 2500. In the current version of the software I don’t have a way to tell what board you are using so I leave it at the default for the v3 hardware. makes no difference to the v2 users, makes v3 users happy.
DanKeymasterOn OSX, if you have JAVA installed, double-clicking the JAR file should start the application. You may run into resistance from security preferences because the app was downloaded off the internet.
I have written a new OSX start in the last few days that is more robust. You can get a copy and try it here:
https://raw.githubusercontent.com/MarginallyClever/Makelangelo-software/dev/start%20OSX.command
DanKeymasterYou are correct that they end with a semicolon. Does anyone put gcode AFTER the semicolon? Programmer error.
Does Gcode come with lower-case letter or no-space-before letters? No, so no need to cover those cases.
I love that you’re making an effort, that’s rare and special. I want to encourage you. How? The fixes you’re proposing create new problems. By pointing them out I’m sending the “you’re doing it wrong” message instead of the “good try!” message.
DanKeymasterThe things you have added are not in the specs for GCODE.
Please limit your fix to the actual problem.
What do you bet there’s a compiler option that makes your system process the arduino code without error?
DanKeymasterWhat about when you have
G00 X10; G00 X-10
?
while(ptr>=buffer)
could be a very long time.
DanKeymasterI guess you’ll have to cast to int and see if that makes the bug go away. It’s specific to a compiler that I don’t have installed. Can you try and let me know what works, please? I’ll then add your fix to the code permanently.
DanKeymasterThe more steps the better. We use 400 step (0.9).
DanKeymasterI have updated the github repository and the issue with a possible fix. please download a fresh copy and try again. If it works I will make the same change across the rest of gcodecncdemo.
DanKeymasterI created a github issue
DanKeymasterSo it hangs on the very first command? That is almost guaranteed you are not setting “newline” in the arduino serial window. the program waits for newline (\n) before processing a message.
-
AuthorPosts