Forum Replies Created
-
OK, I’ll assume a PC running Windows10.
What browser do you use to run Chilipeppr?
Chrome is generally considered to be the most stable and reliable browser for running Chilipeppr. I have goof luck with Firefox as well.
Chilipeppr is built on javascript, needs leading edge javascript support.I suggest the following to get started.
TinyG wiki can help https://github.com/synthetos/TinyG/wiki> Reboot windows, which should terminate any SPJS processes that might be lurking in the background. Double check that by opening the Windows Task Manager and searching for SPJS.
> Focus on getting CoolTerm connected to tinyG. Get familiar with the command line interface. Send a ?, get a response, send a $, get a response. Send a $$, get the full parameter list.
Copy that full parameter list to a text file, upload the text file to a Cloud resource (GDrive, etc) and post the sharing URL here.Once you know the basic Win10 interface to tinyG is working, you can consider trying Chilipeppr again. A good Forum for Chilipeppr help is https://groups.google.com/forum/#!forum/chilipeppr
Motors- If you want to understand why LED seems a bit random, scan thru this
Step to winding translation is a rather complex process
Motors:
Here is a link to a motor schematicYou will see that the LEDs are connected to Motor winding B1 on each motor.
The LED will be on, with random intensity, when B1 is Positiive relative to Gnd.
The A winding and B winding level and polarity is controlled by the stepper driver device. The LEDs are a VERY relative indicator of voltage being applied to the motor, nothing more.I’ll dig into your parameters in a bit
This info would be helpful in jump-starting a solution for you
? What CAM interface do you use? (ChiliPeppr, CNCjs, CoolTerm)
? What OS on your main PC?
? Create a text file and copy a $$ Parameter dump into the file, then post the file to a Cloud service (GDrive, etc) and provide a URLMotor 4: Make a long Y move, something like G1 Y100 F100 and observe the LEDs
Then move back to 0 with a G1 Y0 F100.
Do the flashes on M3 and M4 LEDs complement each other over the round trip?I am not an Ox owner, but there do seem to be many happy with their machines over at the Ox Forum
.
Let’s not kid ourselves, even the big industrial machines need good maintenance. It would appear you have discovered the critical areas to keep track of.There is no easy answer to the screw vs belt question. Screw machines are costly to scale(in size) but perhaps more rugged.
Generally speaking, the lower the value of $_tr, the more usable holding torque from your motor spec you get.The torque/pulley issue.
AFAIK, Ox specifies the smallest pulley that is generally available for GT2 belts, which are more rugged than MXL belts used in ShapeOko designs.
Smaller pulley diameter is better, from a torque load perspective.
It is perhaps easiest to think of the issue in terms of holding torque.
If you energize your motors to hold a position, then try to push the gantry manually in X or Y direction, your pushing force is translated into a rotational load on the stepper shaft, the stepper pushes back with the torque available determined by how much current you dump into the stepper, which at rest is acting like a stationary electro-magnet.
In this mode, the pulley diameter acts to amplify the amount of torque on the shaft you are creating by pushing on the belt. That torque amplification scales, I believe, as radius-squared, radius of the pulley.
A long while back I did the math and came to the informal conclusion that an Ox with ‘good’ quality NEMA23 motors and ShapeOko with ‘good’ quality NEMA 17 motors had about the same gantry holding properties out-of-the box.
The Ox design wins here for heavy duty users because there are a lot more stepper options above ‘good’ level in terms of available holding torque. And some folks have even gone to NEMA 34 motors.
Alas, high torque motors, high current drivers, cooling systems and power supplies drive costs up quickly.I hope that helps, the math gets complex and there are way too many variables to get super specific.
3DPtr: I am not a player yet, searching like your for alternatives. If you dig into G2core
you will see that a lot of the recent work is targeted at 3DPtr enabling enhancements. G2Core is the motion engine for several evolving 3DPrinters.
My take is that the bigger question in that space is around the CAM layer software features, functionality and the entire 3dPtr tool chain.A lot more complexity, and a lot more opportunity in 3D space, depending on what you want the end result to be.
