[solved] makelangelo 2 line inaccuracy

[Anonymous]

my maklangelo2 keeps going way up and way down when drawing way up that the strings cut although the borders and limits are set correctly in the software please help and advice

if anyone readying this has a successful M2 robot please message me at : https://www.facebook.com/yousef.farokh
cuz i really need help
thank you

[Anonymous]

What happens when you move Y+10? Should move 1cm up

What happens when you move X+10? Should move 1cm right

[Anonymous]

yes but the problem occurs in drawing

[Anonymous]

Are you running connected with USB cable? Sometimes the signal from PC to Makelangelo has noise and can lose one digit. Not very bad most of the time: X1.0053 instead of X1.00543. Sometimes really bad: X100543 instead of X1.00543.
I am working on adding checksum to messages to fix this issue.

[Anonymous]

yeah connected to usb cable ? am i suppose not to connect it ?

[Anonymous]

You are! I have recently discovered that you are not alone with this problem.

I am working on adding a CRC system so robot confirms it got the message that PC sent. This should eliminate a lot of bad juju.

I am also setting up a permanent installation of the M2 so I can test the software regularly.

[Anonymous]

i tried every thing but my machine does not under stand the concept of limits 😀 what a rebel i goes out side paper limits and machine limits although all values are set correctly and in millimeters 😮

[Anonymous]

but… if everything is set right the PC should never ask the robot to go outside the limits.

[Anonymous]

its all set right , will making a video help ?

[Anonymous]

Yes, it could. Also can you tell me all your settings in “configure limits” and “configure bobbins”?

[Anonymous]

my M2 robot
http://imgur.com/a/qEHi1

every thing is set correct and the measurements are : mw:1060mm mh:660mm pw:600mm ph:500mm
and here is a video : http://www.youtube.com/watch?v=AiGi3wMyzjE

[Anonymous]

Two questions.

1: what is your bobbin diameter config? for the M2 it should be ~9.5mm.

2: when you measure the board size, width should be from NW eyebolt to NE eyebolt. Is this what you did? Also height should be NW eyebolt to SW eyebolt (or NE to SE, same thing).

I also notice the pen holder feet leave the paper a lot. That shouldn’t happen! Try moving the strings to the 2nd or 3rd hole on the top of the pen holder.

Does this help?

[Anonymous]

1) yes my bobin diameter is 9.5 mm
2) yes all the machines sizes are from the eye bolt to the eye bolt

[Anonymous]

What gcode are you running in your test? It doesn’t look like a picture generated by the Makelangelo software.

[Anonymous]

this in in fact an image created by makelangelo this is the Fibonacci its a ready g code i also have problems on transfaring images ti g code it keeps on saying access denied

[Anonymous]

It looks like your stepper motors are skipping? I don’t know that is just what they look like in the video. Did you try creating code from a picture and NOT using the supplied GCode examples? I might be wrong, but I would think the supplied examples would have different movements because the machine’s settings (W,H,PaperW, and PaperH) are different.

[Anonymous]

i cant make my own code it tells me access denied cannot save g code

[Anonymous]

Humm…. did you unzip the folder to your desktop? Are you the admin to the computer? Are your disk drives full?

[Anonymous]

Also I suspect the supplied samples may have a config line at the top that resets the bobbin diameters, which would explain why your settings aren’t being used.

Normally the process is:
– set up your machine
– load (convert) an image
– draw image

What is happening is this:
– set up your machine
– load (convert) an image
* image is turned into lines
* lines are saved to gcode
* start of gcode file includes machine dimensions, bobbin size, motor invert commands
– draw image
* even if you are connected to machine, commands from file are sent to robot which might be different from your current settings

Why aren’t the settings saved on the robot (in EEPROM or something)? Well… I use one robot and test it on many different sizes of boards. EEPROM is like a really old hard drive – write to it too many times and it stops working. So instead of wearing out the EEPROM, I store the values in the file. Maybe I’m the only person who needs this feature?

What I will do is remove the sample gcode from the next update. It’s causing problems and I don’t use it anyhow.

Until you fix your directory permissions you will not be able to use the full power of this battlesta- er, robot. I will add a preferences option so you can set where you want the file to be saved, that might make your life easier.

[Anonymous]

One solution would be to save the machine settings in another file. Then send that file to the machine and then send the gcode file. You could simply create a temp file that contains the contents of the config file and then the gcode drawing.

I haven’t had the chance to look at the code yet but that seems doable.

[Anonymous]

That’s an interesting approach. If you are running connected you can just remove the config lines from the start of the file. The machine gets config data the moment it connects, so it doesn’t need the ones in the file. It *will* need them if you run the same file from an SD card… but for a test this should be enough.

I’m presently working on a way to load a machine setting without being connected so it will generate gcode that correctly signs the image, etc.

[Anonymous]

still the same problem idk why my m2 doesnt work although every thing is connected good and followed all your instructions !!!
and my pc still cannot convert images ??

[Author]

Posts