Forum Replies Created
-
AuthorPosts
-
aldenMember
Eduardo,
Thanks for posting your experience. I have some questions to diagnose this.
– Are you using the JSON protocol? It appears so, but I want to confirm.
– Which parameters time out? None of them should. Could it be that you are writing parameters when the queue is full? You can determine how many of the 254 bytes in the receive queue are available by requesting (rx:n}. It returns the number of available bytes.
As for SR’s, you should set up a listener for them and handle them when they come in. They are not synchronous commands such as request/response pairs. The normal communications is:
– Send request, get response almost immediately. Listen for SRs. Most people look for the stat:3, which means the machine has stopped.- This reply was modified 9 years, 5 months ago by alden.
aldenMemberPutting 2 NEMA17’s (or NEMA23’s) in parallel will not damage the driver. Adjust the Vref until the driver runs smoothly. If the drivers take too much current – as might be the case with very large NEMA23s – the driver may go into thermal shutdown but should not be damaged. In that case we recommend fan cooling.
aldenMemberThanks for the note. We have been refactoring the digital IO system and will include M53 as an option.
aldenMemberThank you for the report. We are still doing some work on arcs. Thank you for your patience – we should have this resolved soon.
aldenMemberIt sounds like the motor / wiring. Stuttering may be an indication of thermal shutdown of the chip (see if the chip is hot to the touch), but more likely one of the motor phases is not connected or is intermittently connected.
aldenMemberFinally back to my shop. I’ve just run part1.nc on build 440.14 – our current edge build. It’s working well – other than I don’t have quite enough table for it and it crashes into the edge on my Shapeoko2. 440.14 is what Chilipeppr is running these days so I’d recommend updating to that build.
aldenMemberCan you post the makercam file somewhere where we could try it out?
–thanks
aldenMemberTry a series of moves going back and forth, like
g1 f1000 x1000
g1 f1000 x0Or simply
g1 f1000 x1000
x0
y1000
y0
z1000
z0…etc
You can enter them individually or in the Coolterm “Send String” dialog in the Communications menu item. Do you get any movement?
aldenMemberCan you please post what build number you are on? That’s the $fb value in the $ display — Thanks
aldenMemberHave you checked your stepper wiring? If the problem moved from the Y axis to motor 4 that’s in indication that something’s wrong in the motor, or often the wiring itself. Your symptoms sound like 1 of the 2 motor phases is not energizing.
If you have a spare motor lying around try attaching that to the Y axis (Motor 2, I assume) and see if that works – or just re-arrange your profile to map the X axis to motor 2 and see if that works. This would be useful to isolate the problem between the motor driver and the the wiring/motor/mechanical system.
aldenMemberWe’ll get that posted to the download page shortly. Sorry for the delay.
aldenMemberThe RX and TX lines on the v7 and v8 are set up to be 5v tolerant specifically so you can connect one up to an Arduino.
Realize that you cannot use the USB and the RX/TX connection at the same time, but you may be able to “snoop” on the RX/TX with the USB. But it’s probably best to unplug the USB.
- This reply was modified 9 years, 9 months ago by alden.
aldenMemberIt’s past time to move the edge branch to Master. Edge is fine and recommended at this point. At that point edge will become more “edgy” as we introduce new functionality.
November 2, 2014 at 2:36 pm in reply to: JSON level 5 responses are hard to check for correctness #6963aldenMemberHow are you parsing? Most UI’s using JSON are using the native JSON capabilities in JavaScript, Python or whatever. Floats are floats, so it doesn’t matter.
There is a list of precisions in the config_app.c file. The table sets what precision the results are returned. There may be a few special cases where the answer may be different in mm mode or inches.
aldenMemberI think I cross posted to the wrong thread. The seeeduino is not an Arduino R3 pinout and the power connector is different. See here for guidance.
https://github.com/synthetos/grblShield/wiki/gShield-v5-Notes#5-volt-power-right-position
-
AuthorPosts