Forum Replies Created
-
For your entertainment, here is one thread on the topic of issues related to stepper pulsewidth.
I don’t have precise records, but 435.1 fw is in the timeframe that this issue appeared. Dialing $yvm way back to 1000 worked fror me, but the ultimate solution was fw 438.02 at the timr.
And, a newer build, 440.13, is an even better choice. available here
or try the new downloader
Sorry, I missed your question in the queue.
Motor settings should look like:
(hint – developers use MACOS, zero indexing)
[1ma] m1 map to axis 0 [0=X,1=Y,2=Z…]
[2ma] m2 map to axis 1 [0=X,1=Y,2=Z…]
[3ma] m3 map to axis 2 [0=X,1=Y,2=Z…]Are you sure you sure physical motors are wired as you report?
I know of no easy way to get a particular rotational speed , such as 8rps.
If you just want to slow them down, Try
G1 X10 F800
and keep lowering F800 until you get the speed you want.G0 moves are made at $xvm (for x axis)
G1 moves are made at “F” speed (usually specked in the Gcode ), Fspeed is the desired machining speed,
Same for G2 and G3 (arc) moves.Note – these are big moves for a typical machine. Your motors are not connected, just spinning in air, correct?
If you really want 8rps, then do some calculations
1 rev = 62.83 (mm?) (are you sure, implies a rather large pulley?)
8 revs = 8*62.83 mm = 502.64mm
So G1 X502.64 F30158 [F is in mm/min (502.64*60)]
Should cause X motor to rotate 8 times in one second.In one second, you won’t notice tinyG jerk and third order control.
But if you issue
G1 X502.64 F3015.8
it should take 10 seconds to move 8 revolutions.
You should see tinyG ramp the motor up and ramp motor down (3rd order motion rather than on-off linear)Hope this helps
Two loose screws in one 7 day period – an epidemic! (We always overlook the obvious, and reproducibility DOES seem to be a software trait, not mechanical).
Your $$ listing does look strange.
if it persists making double reports, then a $defa=1 and parameter reload might help. What are you using to send commands to the machine(CoolTerm, etc)?
Edit – Well that was a dumb question, Chilipeppr of course. Before running $defa=1, try it in CoolTerm.Otherwise, you appear to be good. Have fun
Greetings, Stefan
The binaries available atare very old.
I suggest you only build your own, as you are attempting.
In G2 space, Edge is much more ‘edgy’ than in tinyG.
I might suggest you try Master initially, it will build $fb=71.04 at the moment, I believe.
If that does not work for you, then try Edge.You will need to be both comfortable and proficient with building binaries to use G2 for now, as you are doing.There is continuous change and new development going on, and pre-built binaries are not likely to be available.
Here are two links you should review, probably several times – lots of details.
Start with the Readme.md on gitHub atThen read this, or all the wiki items so you know where to look for info.
There is way too much detail to address your specific question, I’ll leave it to you to carefully review the above.
But here is a hint – don’t delete or modify any files in your cloned gitHub directory – that might cause the build process to fail.
I have not run a build in AS6.2, have done my builds in Linux, where the command would be:
make PLATFORM=gShield SETTINGS_FILE=settings_shapeoko375.h
You will need to find the appropriate fields in AS6.2 to specify the PLATFORM= and the SETTINGS_FILE =Once built and flashed, yes, you can make parameter updates either from the CLI widget in CP or using the configuretinyG widget in the tinyG widget.
Once you know what your custom setting for your machine are, you might want to open the file ‘settings_shapeoko375.h’ in the github cloned directory, make your modifications, then save the file in the settings directory as settings_shapeoko375_stefan.h.
Then rebuild the binary withSETTINGS_FILE=settings_shapeoko375_stefan.hAfter flashing, any reset of the DUE will have your personalized settings as the default.
If you try Master (fb=71.04), run Chilipeppr with
There is a bug in Master that does not initiate well with CP. If you go right to Edge, the bug appears fixed and you can run
Frank
IIRC, the 3040 is a Threaded rod machine. Is your wood router belt driven, like a ShepeOko?
I would be suspicious of power management settings on the wood machine, looks like the inactive motors may not be holding position. There is much less holding torques required on a rod machine.You could try setting your $mt=60 sec (experiment with it on a short job).
I think there may be a issue with the Power manaagemnt FW that is still timing out motors when $_pm=1. That, and other issues, will be corrected soon in a new FW build.Your wood machine, with the large wheels, (resulting in large travels $_tr=120) has 1/3 the holding torque with the motors energized as well (compared to SO2 with $tr=40).
Do you have the current pots maxed out? Yours is the largest $_tr I have seen, I’m not sure there is a lot of experience there.
If you turn the motors on, can you move the gantry (against the holding torque) by hand?You settings listing above also looks strange, many , but not all, rows repeated. Could be the Forum tool. Configs are easier to view in an attached file. See
