Jogging Suprise ? A good one !!

[murphy625]

Well I'm just a newbie so if this is a dumb question and has some obvious answer, please excuse the post..

I have absolutly no code in my jogging file. There is no code anywhere (that I know of).

My jog button still works!!! What is up with this?

I was under the impression that I needed to write code in the jog file to make this work.. There is no code and it works fine.

Does this have something to do with some kind of "default" values in the camsoft software? I am just using the mouse and/or keyboard to activate it.

Thanks!
Murphy

[emti95]

Look in the inputio.fil file. That's where the jog button info is on my system. The jog.fil file sets feedrates for jogging the axes to something other than the defaults.

[howling60]

it is my interpretation (of course, it may be wrong...).. that the jogging file, is only called when you enter, and then when you exit your jogging mode. So, you can use it to change feedrates & such for your jogging... the keyboard/mouse combo.. which i am sure you will find soon is no fun to use, is really not the reccommended solution for jogging of the machine.

I personally connected 3 external buttons (jog+, jog-, no jog), and then used an m-code call to change my jogging axis, as i could not obtain fine enough control using the default keyboard jog. I still can't figure out why the camsoft system has that much "lag" in recognizing keyboard input.. but.. that is not a discussion i want to dive into here & now..

so, yes.. you do need to write logic/code to make the jogging work.. but only if you don't like the stock setup provided by camsoft

[intrusion]

I believe you are correct, the JOG.FIL file is there only if you need to modify the default jogging parameters. If there is logic in the JOG.FIL file when you press the JOG ICON then this file will run and execute whatever is in there - then when you press the JOG ICON a second time to turn jogging off then the JOG.FIL file will run again to reset whatever.

I also think that the lag in response is not due to the windows/softwares respnonse of the keyboard as all F-function keys work extremely quick as well as the arrow keys. The lag I think is due to motor tuning, that if the system see that the motors are moving or oscillating then the jogging will wait for them to stop before motion is allowed to beging.

[camsoft]

Here's some more advice:

Besides the keyboard jog there are these other user customizable pre-written macros in the MACRO.FIL, MACRO.MAC and various CBK's for jogging.

[Jog Buttons]
[Touch Screen Jog]
[Jog 2 Axes Mode]
[Jog Single Axis Mode]
[Jog in Increments Mode]
[JoyStick]
[Analog Joystick]
[JOYSTICK ANALOG-USB]

Plus of course each hanging, flush mount or hand held operator pendant CBK has it's own, such as

[CONTROLMATE_JOG-]
[CONTROLMATE_JOG+]

You also could always make your own custom jogging routine like howling60.

As Intrusion mentioned the lag in the keyboard jog is because of something else coming into play. Depending on your how busy your CPU is and operating system this should only be 10 to 120 ms which is roughly only 1/10 th second. There's no reason for us to make it any longer, but because of many factors such as servo tuning, busy CPU, Accel rate and most commonly motor movement/drift/oscillation the jog will delay until the encoder is steady.

The key board jog is never going to be snappy, but any delay is for other reasons so some times it's just best to make your own or use an alternate method that uses real physical buttons, joystick, game controller or touch screen. The great thing is , is that you have this choice.

Regarding G54-G53 and G53 canceling offsets. We watch the discussions go on without commenting, simply because this is your forum, but we also want to step in when a remark is made to clear a topic up. We should step in more often, just so people don't think some of the items written about here don't really work this way. If someone see's something written that doesn't sound right then they could always contact us directly and we'll straighten it out. The horse's mouth so to say.

For example:

N198 G54
N199 X4.5 Y2
N200 G53
N201 X4.5 Y2

When X is positioned in N199 at X4.5 it is moved to 4.5 plus the offset value in G54.

When X is positioned in N201 is it moved to X4.5 with out offset. Even if the X value isn't given the internal X register is still at 4.5. You should expect a movement in N201. The X value the same but the position is without offset. All axis are modal. No need to call them again if they havn't changed. Optionally, you can call the macro we provide in G53 to reset the internally register. A line without an axes value shouldn't move, but if you did call out the axis letter it should move. We leave the choice up to you.

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