I have not noticed that. How short are the pauses? 2 sec? 0.2 sec? Just ballpark.
1 Like
Something like 0.5 to 1 sec
Ah bummer. That’s not good. Can you post a gcode file here (you have to rename it .txt). I’ll see if my machine does the same pauses, and maybe submit a bug report to cnc.js. I think they rely too much on timeouts for stuff, and I bet they are missing an ‘ok’ somewhere, and they wait for the timeout to send the next command.
1 Like
Here are the files, I tried one without arcs enabled, but there it pauses at even more points. I think it happens when one move is finished, so it happens also at the same time the view updates to display the current code line.
Thanks for looking into it
Gripper-handle.txt (53.4 KB)
Gripper-handle-arcs.txt (7.19 KB)
What power supply is everyone using for the pi? I keep getting under voltage warnings when the rambo is plugged in.
I need a good quality power supply and cable. The ones I have seem to be under powered.
Shoot I have been looking all over for my USB power cable that came with my Zero. I know it wasn’t that big, the control board and PI should easily be ran off the power supply in my kits.
Do your power supplies provide 5V?
Ohhhhhh, forgot, nope
The Rambo shouldn’t be taking much power. So that’s weird.
Any of the 1.5A ish ones should work fine.
I’m not suggesting this, but I have my pi powered off the 12V with one of these (I don’t have this exact one, but it’s similar):
It has a set screw for adjusting the voltage, so you’ll need a volt meter you trust. You can either wire it to a usb connector or solder it to the pins of the usb connector. I have mine set right at 5V and I have it plugged into 5V and GND on the big IO header, but that bypasses the power filter on the pi. I think that’s fine with aomwthing like this because the power filtering on these boards is probably bigger than the ones on the pi anyway, just don’t set it to 6V.
Jeff. Awesome work.
Maybe this has been asked before…I just can’t work magic with the search button to find it. Is there a way to do a static IP address? I would like to put a bookmark on my Android phone to link but if it is dynamic then it is anybody’s guess short of logging onto a computer to get there IP address.
Second thought/next revision suggestion. On the “.local” website front page, can you list the IP address on the pi? It could be a separate link or window on the front page.
Thanks again. Great work!
This is a great idea. Definitely in the next version.
There is. If you search for “static ip wifi raspberry pi” I bet you’ll find it. I haven’t tried it myself. I prefer to set up “static dhcp” on my router. Every time the pi asks for an ip, the router gives it the same number. There are also a few apps that can use avahi/mdns to resolve the .local address.
I had a fair amount of frustration this evening. It all started with V1Pi last week. Before I go nuts…it isn’t Jeff’s fault. Everything is working…just better now.
Background - I had built a MPCNC last year and wasn’t happy with the “z” axis rigidity. So upgrading this winter to the Lowrider2. Got it all built and running over Christmas, did some small prints (pen drawing stuff) and did some pockets for a vacuum table (scrapped that idea). Anyway, V1PI comes along and I think, “this could be awesome I want a pendant of some sort anyway.” So I bought my first Pi (happens to be a Zero W) and got it working. X and Y worked flawlessly, Z torqued me off. When I would do a Z move on the controller (full graphic display) to move 10mm upward, it did it without any problems. When I would move with CNC.JS 10mm up it sounded like the Z axis was being ripped apart.
I was confused and decided to put the PI away until I could figure it out. Went onto the forums and saw a post for 3D Fox. I put it on an old phone and started to play around with it. Moving in 1mm increments in the Z axis…no problem. Moving in 10mm increments and same issue.
OK. It isn’t the software…it has to be the operator. Beer 30 and sleep.
Today I got to play again. I started with the voltage going to the motors. I had it set for .6 vDC. I put it to 1.2 and tried moving. Not better. Took the X axis driver and swapped the Z (lower the voltage back to .6 also). Not better. Head scratch…firmware?
BINGO! Acceleration Vmax was set to 30. I switched it to 20 and we got somewhere. Changed the A-travel Amax Z from 200 to 100 and she started to purr. Sweet. Made the changes and started to look for the “save settings” and (insert price is right losing horn) FAIL. Menu item was not to be found. Okay. I have a pendant…I’ll do a “M500” to save the settings. Eprom settings not enabled. PEOPLE…I’M ALREADY BALD!!! STOP THIS MADNESS!!!
Collect composure, remove Ramps board, off to the basement because I don’t have an acceptable laptop for programming (stopping at the fridge for a beer). Find the settings to change the Acceleration, A-travel, and X axis steps (calibration done last week) and flash it over.
To save some people the headache (if you made it this far congratulations, you get 10,000 points but the points don’t matter). Remove the comments from the following items in the Configuration.h. This will allow you to make changes to steps per unit, max feed rates, and acceleration (and probably a bunch of other things). You WILL have to do a “M500” either from CNC.JS, 3d Fox, or whatever your favorite client is on your computer.
#define EEPROM_SETTINGS
#define DISABLE_M503
#define EEPROM_CHITCHAT
Compile, upload, enjoy. (sorry for the rant)
Does this fix the cnc.js first move error?
I made a note to lower theses, the few speed deamons that might want that can edit it themselves, I myself prefer these lower numbers. I am still not keen on enabling the eeprom, we had some sticky settings if the firmware updates were too close together, and the same can be done with an edit and flash, keeps the inexperienced away form changing something they don;t understand.
EEPROM_CHITCHAT just enables logging all eeprom related operations to serial port.
what didn’t see is that he had used M502
// M502 - reverts to the default “factory settings”. You still need to store them in EEPROM afterwards if you want to.
it’s first aid before M500 when something going wrong or after you have flashed different firmware
I think that’s been fixed. IIRC, it keeps telling me to run M502. or whatever. You could also add the M502 command to your flashing instructions.
Most of the settings are pretty straightforward, and asking someone who’s not comfortable to flash, especially with 2.0 sounds like a bigger consequence to me. The guides I’ve seen all just assume EEPROM is enabled. Add to that the fact that you’re doing the initial flashing, and even with my skill level I would be nervous to flash a board that had working firmware, and was maybe 3 months+ old. How would I know I was only changing the speed setting if I bought a flashed board from you and I was trying to flash from the latest in your github?
I also really like keeping M503, not sure why that needs to be disabled. Is this related to the CNC.js startup issue?
I’m really sorry that I haven’t tested this. It’s still on my todo list, but I just haven’t had much machine time.
2 questions,
I see there is an open report on github, is there any way to manually fix the having to send X0 command in cnc.js?
I’m running a mpcnc without the end stop switches, and I’m a little confused about how to set the home location for a job. In testing I have opened cnc.js, moved the pen to want I want to start and then load gcode. It seems like I have to move the pen and then reconnect to the rambo board to set the new home, is that how it’s supposed to be done?
Send
G92 x0 y0
This is to set home?