Dan
Forum Replies Created
-
Posts
-
it’s hard to say. increasing spool size will increase the amount of torque required to turn the spool, which could make the steppers miss steps. like… if it is trying to make a step but is not finished by the time the next step begins… oops.
the code works by using an Interrupt Service Routine (ISR). basically… I use one of the chip clocks and say “every nth tick run this routine”. the routine is optimized to be as fast as i can make it, so that it can make the step commands as fast as possible. if the ISR is not done by the next clock tick then the ISR … trips over it’s own feet, metaphorically. unpredictable things happen. that is also why you don’t see pause() or delay() in there. the ISR speed is adjusted to control the delay between steps. I have pushed it to about F8000 with success, but the drawing accuracy is very very low and the belts start to skip on the pulleys.
A RUMBA board should be running at the same speed as a Mega. I like to think of the RUMBA as a Mega and a Ramps on a single PCB.
500mm/s is crazy fast. I mean, that would be hard for ANY cnc machine.
For feed rate (speed) and acceleration there is the default, the maximum, and the current value. MAX_FEEDRATE and MAX_ACCELERATION are the maximum. you cannot change the current value above the maximum. default is the starting value when the machine is turned on. So YES, you can change the current value with that gcode. if you want to go higher you will have to change the value for MAX_(whatever) and then upload the code to the robot.
Acceleration is change in velocity. Jerk is change in acceleration. max jerk is the limit on acceleration changes.
I think you’ll find that even if you change the pause() you cannot get 500mm/s. Currently at 5000 steps each step takes ~200us to calculate. The stepper motors would have to turn over 600 RPM, or 40000 microsteps per second AT FULL SPEED, not including acceleration and deceleration delay. That would require a minimum clock speed of 40 microseconds per step. So… the RUMBA board would have to be >5x faster clock to do what you want OR the code would have to be vastly more efficient OR the microstepping would have to be turned off, creating a less accurate but faster moving machine.
When you say “jerking” what do you mean? when i hear “jerk” I think of speed is affected by acceleration is affected by jerk is affected by snap, etc.
What speed are you trying to reach?
The two most obvious limits to top speed are
* the physical limits of the hardware – improved by reducing mass, increasing torque, etc
* the clock speed of the brain – improved by getting a faster brain to step motors more quicklyIn zarplotter.h there is a MAX_FEEDRATE, MAX_ACCELERATION, and MAX_JERK. These can all be raised.
I want to hear more about your experiments so that they can be shared with everyone.
fwiw, I have been doing experiments with adjusting acceleration based on machine size and plotter position.
Acceleration sideways can be higher when the plotter is near the top of the drawing because the V shape of the belts is much wider (more stable).
Marlin firmware supports RUMBA and this LCD screen.
I have ordered one from Amazon to experiment and it is on the way.
The hardest part is fitting the graphics into the tiny brain of the RUMBA board.That is odd. I normally get better quality higher up. If you draw a 10cm line in any one direction is it actually 10cm?
Check the microstepping switches on the driver.
Makelangelo 2.5.2 is no longer supported by the software.
I don’t have the resources to support every version.
If you modify the code to support 2.5.2 and send in a pull request then I welcome it.close makelangelo-software
run regedit.
find Computer\HKEY_CURRENT_USER\Software\JavaSoft\Prefs\/Draw/Bot\/Language\language
change value data to “/English”
run makelangelo-software again.
I don’t know why that many common grounds would be better. if you find out, let me know.
try this sketch: https://github.com/i-make-robots/LEDWall/blob/64×36-wall/Teensy/basicTest/basicTest.ino
change
#define COLUMNS 64 // all of the following params need to be adjusted for screen size
#define ROWS 36 // LED_LAYOUT assumed 0 if ROWS > 8and post results. if you have trouble putting pictures here, try uploading them to imgur.com and then linking them here.
https://github.com/FastLED/FastLED
comes with examples.
I don’t recognize the code you’re running (did I write it?) but right away I wonder if
config = WS2811_GRB | WS2811_800kHz;
is what you want when you probably purchased WS2812* LEDs. The devil is in the details.
I also wonder if LEDS_PER_STRIP matches your setup.
Does a FastLED raindow demo work if you set it to 24*108 LEDs? That will tell us if they can all light up (good wiring).
In the Teensy sketch (https://github.com/i-make-robots/LEDWall/blob/master/Teensy/videoDisplay/videoDisplay.ino) did you adjust COLUMNS and ROWS to match your new values?
In the Processing sketch (https://github.com/i-make-robots/LEDWall/blob/master/Processing/screenCapture/screenCapture.pde) did you change the SCREEN_WIDTH and SCREEN_HEIGHT to match?
Did you click “set home” first? The V3 machine cannot auto-home like the V5.
“the dimensions are completely wrong” could be more specific. Details matter! 🙂
Oh yeah, we don’t support the full graphic smart controller. We don’t have any to test with! it’s very pretty. Send me one and I’ll look into it 🙂
Click the connect button and choose the port
you should get a hello world message.
click settings and adjust your machine. check in pen that “up” and “down” correctly raise and lower the pen. if not adjust with the test buttons, then regenerate the gcode.
now your robot is connected, settings are checked, gcode is prepared, and you are ready to go. hit start.
If you have an LCD panel then the robot should beep and ask you to prepare the next pen. click the lcd panel button to continue.
If you don’t have an LCD panel, make sure to compile the firmware without it.
Please share here when you have results!
> a 10×10 cm border exceed the size of the machine
What were your settings supposed o be? it looks like you have a machine 3m*1m. What are your machine and paper settings?
> D10 V5
Your robot thinks it is a Makelangelo 5.
in makelangelo-firmware, polargraph.h the following should be:
#define MACHINE_HARDWARE_VERSION 3
//#define MACHINE_HARDWARE_VERSION 5and in configure.h,
#define MACHINE_STYLE POLARGRAPH
upload your firmware again. it should then report D10 V3, and all will be well.
open windows command prompt.
go to the folder with the bat file and the Makelangelo-7.16.1-with-dependencies.jar file.
typeFOR %A IN (Makelangelo*.jar) DO ECHO %A
and hit enter. What result do you get?
please post your log file contents. it sounds like your firmware is set up for 5 and is announcing itself as such.
When does it “jump”?
Nice! Shared.
What is the status on this ? I don’t see the posts here so i’m no longer up to date. Is the OpenGL error fixed? I think I sent you a link on how to get drivers. Please try 7.16.1 and let me know if it’s better.
