Dan
Forum Replies Created
-
Posts
-
correct and correct.
by default the firmware is set up for makelangelo. to confirm:
in configure.h, there is a line that should say
#define MACHINE_STYLE POLARGRAPH
if the last word is any other type of robot, change it to match as above.
In robot_polargraph.h, If you have a M3.2 there is a line that should say
#define MACHINE_HARDWARE_VERSION 3 // If you have a makelangelo 3+
//#define MACHINE_HARDWARE_VERSION 5 // If you have a makelangelo 5+In robot_polargraph.h, If you have a M5 there is a line that should say
//#define MACHINE_HARDWARE_VERSION 3 // If you have a makelangelo 3+
#define MACHINE_HARDWARE_VERSION 5 // If you have a makelangelo 5+Then go to tools > port and make sure the selected port is your robot. This is the phone number it calls to talk to your robot and send it instructions, same as when you connect with Makelangelo software to drive it from the app.
Then press the circle button that is second from the left. it should have a picture of an arrow pointing to the right. It will compile the code and then send it to the robot. When it says upload complete your work is done!
UNO is not supported. you might want to try older, no longer supported firmware like
Thanks, prenic! You rock!
Nice. I have the same results here.
No luck with a DM320T. 🙁
by default makelangelo-firmware is already set up in configure.h so that the default mode is POLARGRAPH and the default board is RUMBA.
You may want to go into robot_polargraph.h and check that the makelangelo version is 5.
Then upload and you’ll be set.
check the firmware setting for the pin number. What pin are you connecting the servo? What pin is used in the firmware? They must match.
Perhaps @arditoseku means something like this?
yes. afaik no one’s ever done it that way before…
None of which affects the -1. the board is trying to save the machine number into EEPROM, the tiny hard drive like space in it’s head. If that write is failing then the number stays at -1. also if the phone call to get the UID fails, the number would never be updated.
Since you have a custom setup it’s really hard to tell where the point of failure occurs.
Huh. Ok. Machine -1 means that the device has never phoned home to get a unique id. they try to and – in return – i get to track how many machines have been built. it’s probably overwriting settings for machine -1 every time the app starts.
easiest fix is put the computer online, connect to the robot, it will be given a number, and then you’re good after that.
100g and 200g.
Hm. I normally test from my mac laptop and have no trouble. I will schedule time later today to run a test on our new setup:
Does the USB port show up when you use the Arduino app? that will tell us if it’s the software or the hardware.
I like it. For which robot were you thinking?
home position is too low. use the “border” button to check that the machine correctly traces the square edges of your paper. if it comes out like a happy face, your home position is too low. If it is square but your paper is in the wrong spot… move the paper.
send a picture so i can see what “corrupted” looks like. also which settings you used to convert the picture, please.
eh, you can only have one phone call at a time, so to speak. disconnect makelangelo software, the upload firmware. the same will happen fi you have the arduino serial window open and you try to connect the makelangelo software. beeep beeeep beeep line is busy.
That sounds really neat. Do you have a motor shield for the ESP? I would transmit the entire drawing as a single gcode file, store it on a microSD card, and then draw it from the robot. Heck, the ESP has enough power it might be able to conversions IN FIRMWARE. wild!
the six motors are arranged counter-clockwise. the first and second motors are on the same shared face.
the limit switches match the order of the motors, with X- next to the 1st motor and Z+ next to the 6th.
Does that help?
Is your machine #-1?
