Forum Replies Created
-
Some random thoughts since you are willing to dig in and experiment.
I am not a developer and have not dug into the code, so these comments are based on accumulated input from the devs.Your reasoning is OK but , I think, misses the point that the predominant errors are math rounding errors because the hardware is only an 8 bit machine. More digits into that machine will not improve results, most likely.
Working in mm rather than inch settings helps because all tinyG calcs are in mm, so specifying mm data and parameters minimizes the error introduced by repeated calls to the inch-to-mm conversion routines.
The most significant issue seems to be “Large I and J” parameters in arc specifications. My guess is that the work to improve performance has been to refactor the equations to minimize computational error when radius values>>increment values need to be dealt with. I might suggest that relaxing the allowed deviation accuracy in the Post Processor, which would have the effect of turning “almost straight arcs” into short linear moves.
Not using G2/G3 almost always works, but results in very large Gcode files.The devs do not like the idea of relaxing the tinyG tolerance, as the accumulated errors in a long job could be worse than the current result.
These are thoughts, not necessarily solutions.
Hah, Sending $ej=1 is one of those init Items Chilipeppr sends.
CP SPJS does all communication with tinyG in JSON, translates text mode commands on the fly.
That way SPJS always receives JSON formatted status messages, which are quicker to parse.
You should be able to make $ej=1 stick.
Enter it via console, then reboot immediately.But, once it sticks, should you want to go back to text you will have to send “$ej=0” equivalent in JSON format.
I think you are better off leaving it =0 and change when running CNCjs.From looking at parameters, I see an XXYA machine,
2 X motors, a Y motor and a rotator, presummbaly pen up, pen down.With so lille mass being moved (pen vs spindle), jerk could be much higher,
perhaps 5000 to 10000 mm/min^3.I doubt the jerk value is the issue, however.
set $1tr =79.7966, same as $2tr. They should be the same if moving the same axis.Maybe post a copy of gcode to cloud as well?
G2 Wiki pretty good on how to install G2. https://github.com/synthetos/g2/wiki
If you anticipate tweaking, clone the Edge branch to you PC and build it’I suggest this because you will likely find tweaks you want to make in header files or perhaps even some codeDownload the binary to DUE and connect up your external drivers using https://github.com/synthetos/g2/wiki/Arduino-DUE-Pinout-for-g2core as a guide. Since the gSheild has not changed, Motors 1-4 should probably be good and Motor 5 as well.
If you want to skip the build phase for now, download and install https://github.com/synthetos/g2/releases/download/101.03/g2core-gShield-101.03.bin
You should be able to move motors with that build.
If Pinout definition sounds tentative, well it is. If you don’t have access to the right pins for your 5 motor interface, you can move some around with Motate changes, a whole nother layer of complexity.
Numerous folks are experimenting with G2 on various hardware platforms.
