Hi,

I have created a new screen using MachScreen. I took the standard mill screen set and deleted all the pages accept diags and settings. Then I created another page that would be the main page for all stuff. The main screen is designed for a touch screen with and has large buttons.

It seems to work fine except for several things which I can't figure their relation to a specific screen:

1. I define arrow keys to jog from the keyboard, but they just don't work. Simply loading the standard screen fixes it.
2. Some commands don't work from the MDI - G1's work fine while G0s not.
3. I have job buttons on the screen (which is a touch screen), but pressing them the axes would only jog some distance (which is not constant, but very close to such) and then just stop - feels like jogging is set to incremental, while it's not.

Any ideas why would any of these happen?

Thanks,
Dan

1) You must have a Jog On/Off  button on each page you want to jog on. Or is it the LED? One or the other, but you can't jog without it.

2) Do you mean nothing happens if you do a G0 X1? Or it's not using the rapid speed?
 Are you using G Zero, or the letter "O"?

3) Are you 100% positive you're in continuous jog mode? Put a continuous mode LED on the screen to check.

Hi Gerry,

Thanks for the tips.

1. Now works. It appears to be the button that is required.
2. Yes. Nothing happens. But put the same screen on this PC and it seems to work... Will go back to the machine PC and see if there was really a problem or it was my fault.
3. Yes, I am positive I am in continuous jog mode. It seems to me like the the touch screen quirk - as if it doesn't like to be held continuously and quits after a couple of seconds. Is it possible? 

Regards,
Dan

I had a similar problem that resolved when I redefined the arrow and pgup/down hotkkeys in config

If you don't have the parallel port driver installed, certain things will not work. I found that out when designing a screen on the laptop I'm typing this on. Even though it's not capable of running a machine, it needs the driver installed when testing screen functions.

Issue number 2 is resolved - apparently was my fault of some sort. Now seems to work.

Issue number 3 appears to be a touch screen issue - if you statically hold your finger on one spot it just quits after a couple of seconds. Moving the finger around on the button keeps it thinking you're still there. Hope I can find some parameter in the touch screen software to resolve this.

Thanks,
Dan