Single line mode works well, Auto is not soo good??

[Darc]

Fantastic, Camsofts suggestion of putting DECELSTOP in with G01,G02,G03 worked a treat, the only thing I noticed was the last 1 or 2mm of travel seemed to accelerate.
So using all my wisdom (O.K, O.K I guessed) I altered the BLEND and the SLOWDOWN in DESTINATION CONTROL and it seems to be working fine now.
I think I'll run it for a while with no job in there..........am not paranoid.

[HillBilly]

Hu,

M03 S3000
G01 Z-1 F10

If I run this in auto no problem. If I run this one line at a time through MDI the second line executes but cancels the SPEED of the first line.

Hence my conclusion and the [[MDI]] macro.

Darek

[HuFlungDung]

I don't think I've experienced a problem, mind you, I don't use S commands (I use M functions for geared head lathe).

Isn't running a program in Camsoft MDI really just "another mini-program"? Why would the action be any different in Single or Auto? What you say doesn't jive with the way I understand the interface, but then I haven't seen everything yet

[HillBilly]

DECELSTOP
RAPID x;y;r
GO x;y;z
RAPID x;y;r
-----G81

G00 X1 Y1
G00 Z.1
G81 Z-1 R.1 F10
X2
X3
X4
M30

Well try this logic and program in auto and single step mode and see what you think.
The G81 logic is provided in the HANDHELD.CBK.

Darek

[camsoft]

We want to point out that there are three separate topics here and some constructive advice is needed here before people get confused. We want to put these to rest in one cumulative response.

The default keyboard Jogging keys functions, distances, speed, directions, inter-action with other features ect.. are configured in the JOG.FIL file. For example use a negative value for GEAR to reverse the direction and then if need be a positive value back again when exiting the JOG.FIL file.

In addition to this you can reverse the polarity of the wiring and or use several other user definable methods for jogging by joy sticks, physical jog buttons, touch screens ect...

The questions Darc originally raised with single step verses auto mode, were solved on his system with an all together different approach and had nothing to with the modes them selves. As Hu mentioned a program running in MDI is really just "another mini-program.

To go on further the job file Hillbilly posted. This job works the same in auto mode verses single using the default cbk files, but the G81 logic wouldn't work as posted unless the proper rules.ini settings where set up or the logic was entered as shown in the default.cbk. This G81 logic doesn't go with an older system that doesn't have rules settings, but is provided for backwards compatibility. Restoring the default.cbk logic or using the rules setting in CNC SETUP is the way to go.

This is confusing and we would like to straighten this out because there are three separate topics here. With different causes and effects.

MDI, is a mode where one enters a program into an edit style window and runs it. It will run the same as a program that was loaded via G code. MDI should not need special Macros to keep Feeds and Speeds. Auto mode and single step mode should run a program the same.

We don't see the same things happen here or reported by others. The problems experienced are isolated to the setup. Older routines and older versions don't mix. If you really need help of further explanation contact us directly at CamSoft.

Tech Support
CamSoft Corp.
(951) 674-8100
support@camsoftcorp.com
www.cnccontrols.com