[gio666]

[gio666]

Every joining part are all machined

[gio666]

[gio666]

[gio666]

[gio666]

Been getting no stop emails on Raptor machine. When i don't plan on making a machine i seem to get more interest in that machine.
Will now have Raptor 30 inch wide only, be all in one inch aluminum just like Predator

[DiaLFonZo]

Been getting no stop emails on Raptor machine. When i don't plan on making a machine i seem to get more interest in that machine.
Will now have Raptor 30 inch wide only, be all in one inch aluminum just like Predator

Damn...

Eric Nantel (DiaLFonZo)
[email protected]
(Sent from my phone with Tapatalk)

[gio666]

XZero Forums

[gio666]

[gio666]

[gio666]

Should have turnkey pricing on site this week for turnkey ViperXZ and Predator machines

[gio666]

Trying to lower machining costs

[theremin]

the parker stepper drives dont need a kanalog board. they would work the same as any other stepper drive.

on the ui, yeah, i expect it to be somewhere above EMC, but nowhere near as friendly as mach3. trouble with mach3 is it will stall in complex contours and eat the work piece. i cant have that.

What does this situation look like in Mach 3 when it happens? I've had a couple of oddball things happen the past few days--I'll have certain cuts running much slower than I set it up in Madcam, even though the G Code isn't telling the controller to run slower. I've also had some situations where my Y axis suddenly stalls and loses steps for no apparent reason--nothing that I can see in the G code causing it here either. I'm running the current beta version of Madcam 5 and Rhino 5, so it could be a glitch there. But I don't see anything in the G code that looks funny. It is a fairly complex contour that I'm doing, but one very similar to ones I've run in the past without a hitch. I'm wondering if I'm hitting that Mach 3 glitch or if it's something else....

Any ideas? Thanks,

Dave

[Ruby582]

Every joining part are all machined

[ihavenofish]

What does this situation look like in Mach 3 when it happens? I've had a couple of oddball things happen the past few days--I'll have certain cuts running much slower than I set it up in Madcam, even though the G Code isn't telling the controller to run slower. I've also had some situations where my Y axis suddenly stalls and loses steps for no apparent reason--nothing that I can see in the G code causing it here either. I'm running the current beta version of Madcam 5 and Rhino 5, so it could be a glitch there. But I don't see anything in the G code that looks funny. It is a fairly complex contour that I'm doing, but one very similar to ones I've run in the past without a hitch. I'm wondering if I'm hitting that Mach 3 glitch or if it's something else....

Any ideas? Thanks,

Dave

its a random stall, usually in a contouring operation at a direction change. basically it doesnt calculate acceleration correctly, overloads the motor and stalls.

[inventor83]

its a random stall, usually in a contouring operation at a direction change. basically it doesnt calculate acceleration correctly, overloads the motor and stalls.

Does this happen even when you are in CV mode? Usually there is no accel/deccel unless programmed by the CAM soft.

[ihavenofish]

Does this happen even when you are in CV mode? Usually there is no accel/deccel unless programmed by the CAM soft.

errr, no, accel decel is controlled by mach3, nothing to do with cam/gcode.

cv mode does seem to be the root of this bug though.

[theremin]

its a random stall, usually in a contouring operation at a direction change. basically it doesnt calculate acceleration correctly, overloads the motor and stalls.

Thanks--that's pretty much exactly what I'm experiencing. I've been going over all of the Mach3 CV issue threads so I have some things to try now. I did at least upgrade to the newest Mach release. Mine was getting pretty darned old. In the meantime, I'm rethinking some tool paths to try to avoid the situation if I can...

Dave

[gio666]

[gio666]