Dan
Forum Replies Created
-
Posts
-
8-161 ?
filler?
Yes. The machine can do those drawings. The real question is who will write the gcode that the robot will run?
@Phi Le, your picture is great!… but the top corners should be at the center of the motor shafts.
@mrbernd you are 100% correct and thank you for answering Phi Le. Stay awesome 🙂I encourage everyone to join our Discord server, the response time is faster and we have a #showcase channel where you can post what you’ve been making.
Hi!
You should have received a receipt email, and shortly after a download email. Both contain a link to the download file.
We have received a few reports about 7.24.0 and are working on a 7.24.2 hotfix right now. You can get the up-to-the-second testing version in our Nightly builds (actually faster than nightly) right here: https://github.com/MarginallyClever/Makelangelo-software/releases/tag/Nightly
The one you want is makelangelo-nightly-[most recent date]-[checksum].jar
For live chat with our team find us on discord where – together – can tighten the feedback loop. https://discord.gg/QtvHqAv8yp
Your photo links do not load.
curvature in a picture is nearly always a miscalibration.
Ynan
Je croix que votre machine ne sais pas ces limites.
M101 A0 T<x max> B<x min> M101 A1 T<y max> B<y min> M101 A2 T170 B10@hopo28 and this helps, yes or no? https://mcr.dozuki.com/Guide/5.+Makelangelo+Software+Guide/5#s43
Have you tried to load a two-color SVG? It should already remember the colors and offer a pen change at the right moment.
Je comprends francais, si ca aide.
Veuillez partager votre log.txt et tout message d’erreur, svp.
Interesting! I’ve never seen this one before.
First i’d try disconnecting the HID Wacom table and try again.
Then the HIDI2C device, whatever that is.Do you have an extra fancy mouse or keyboard? It’s dying when it tries to make a list of all the buttons on your mouse.
I googled the bug and it seems the jinput library we use can’t understand how to talk to some of the input devices on your machine.
comments added to source code file robot_skycam.h
Your assumption about home position is correct.
Plotter size is the diameter of the tool head at the bottom of the four cables. you may find setting this number to zero gets better results, it all depends on the design of your tool head.
motor size is how far the motor projects inside the corner of the box. the machine size (ideal box) is not the same as the corner where the belt/cable last touches the motor and goes down in a straight line to the tool head.
i’ll add some comments to the code to clear this up for future users. Thanks!
Share pics/vid on our discord, we want to see what you’re making!
Well… i guess some picture of what “really bad” means.
Homing always double-taps the switches. once fast, once slow. then it goes to home. depending on your configuration that could be 0,0 or the stay at the bottom. it’s now customizable in the software.
again, what is really bad border? example pictures, please.
Come talk to us on Discord, we have several ESP32 people wanting to talk about it there.
Please describe the “issues with the windows software”.
The software is written in a way that relies on Java. So java must be installed first.
Here is an english guide, I hope it helps.https://mcr.dozuki.com/Guide/5.+Makelangelo+Software+Guide/5?lang=en
copy ./presets/makelangelo5.h? to ./local_config.h and it should work.
That is correct
“find home” is not “find limit switches”
True…. in the M5 my default is that the home position is also limit switch position. That is not the cartesian origin (0,0). Someone recently contributed a way to set your own home position and that may be part of the confusion. I like it bottom center because it’s reachable on all sizes of machine. Your mileage may vary.
Can you run the 7.23 from the command line? It’s probably spitting out an exception that is not logged to the file (boo). That exception will tell us more about what’s going on.
Also feel free to join our discord to talk live, it can often get faster response times.
https://discord.gg/Q5TZFmB idk why it was the other format. Sorry :T
I haven’t compiled ESP32, so I can’t confirm. Looks like they have their own implementation of Servos. Maybe come to our Discord and we can help more? https://www.marginallyclever.com/channels/
I like (and made a few comments on) your PR 🙂
From the code you posted it looks like chip select is pin 53 (matches board_ramps.h) and sd card detect is 48 (board_ramps.h has 49 as the default). Look for
#if LCD_TYPE == LCD_IS_128X64in the code. I don’t have a 128×64 screen so I can’t test it locally.
At the top of your code there’s an “const int chipSelect = 53;” and later the number 53 is used many times instead of the word chipSelect, which is the point of having chipSelect. in I would use a
#define CHIP_SELECT 53and then use the world CHIP_SELECT instead of ’53’ where appropriate. The pre-processing step of the compiler will replace the word with the equivalent number. it’s probably better than ‘const int’ because a const int might take up some ram if the compiler is dumb, and ram in an arduino is in short supply. also if it actually takes up ram then the firmware has to look up that number every time it is used, which is slower than having the number hard coded on hand ready to go.
48 should have been been done the same way. The point of defines like that is so that only one place has to be changed to update all the code.
did you branch from the main repository? You should be able to submit a PR with either github desktop or through the github website. I haven’t contributed to many other projects so I’m not confident enough to guide you. Come to our Discord if you need more help or to chat live about development. https://www.marginallyclever.com/channels/
