I am a relative newcomer here. I have a Series I Boss 3, an old Series II NC (not CNC), a Grizzly X3, and I'm building a purpose built machine to automate a carbon fiber manufacturing process. As of now, I have the Boss 3 converted to Mach 3 and plan to get the Series II and the X3 done too.

For my setup on the Boss 3, I have an Elo 15" touch screen monitor and I want to eliminate the mouse and keyboard altogether.

All the different screensets I have tried have some amount of scrunching and squeezing of the bitmaps to fit the smaller confines of the usable space that's left after Windows puts up its headers and window borders. I prefer not to have this and, along with other desires, I am designing my own screenset. I have started with Gerry's Aqua set and have used much of the graphics as well as modified some for my needs. I don't know the protocol, I don't want to step on anyone's toes or take anyone's work and use it inappropriately. So if I'm violating any rules, please let me know!

I have installed Klaus's MachScreen and plan to use it to do the work. So far I have only cut and pasted (and otherwise edited) the graphics in Paint Shop Pro so nothing works yet. There may even be things I want to do that are not possible....

Anyway, It recently dawned on me that I could share my ideas with this forum. Here is an image of the run-screen. It is still a work-in-progress, but it has most of what I plan to do on this screen.

Since I have a touch screen, I am thinking I may remove the Jog section because it won't be too convenient to be eyeballing the tool/part while trying to reach for the screen. A pendant will preclude the need for that stuff.

Most of my CNC experience is with an old Fanuc 6m control. It was before there was a toolpath display, so I look at the part not the display - so to save space, I omitted the toolpath display on the run screen. The amber buttons across the top left will switch to the different screens. That old Fanuc had a "dry run" switch that ran the program at a rapid speed for testing. I used it all the time and I haven't seen one on any other screens.

Plus, I never plan on using mist coolant, so I don't have a button for it. I left off a lot of things I don't use...

I'll probably remove the MDI line too. Since I want to eliminate the keyboard, I'll need to figure a way to have one on the screen for MDI (so it will probably be changed to a button to open a different screen). I had planned on having the flyout be a keypad, but there are things about that I don't think will work well.

dotScott has a beautiful Settings screen that I want to use parts of also.

This is just the beginning, I can't believe how long it has taken me to just do this screen image. Since I am getting by with the 1024 screenset, I can still use the mill. It will probably be slow progress on this as I still have to learn to use MachScreen.

Your comments and suggestions are welcome! I may need to ask questions on making this all come together!

This is just the beginning, I can't believe how long it has taken me to just do this screen image. Tongue  Since I am getting by with the 1024 screenset, I can still use the mill. It will probably be slow progress on this as I still have to learn to use MachScreen.

Welcome to my world!  

I'll probably remove the MDI line too. Since I want to eliminate the keyboard, I'll need to figure a way to have one on the screen for MDI (so it will probably be changed to a button to open a different screen). I had planned on having the flyout be a keypad, but there are things about that I don't think will work well.

Just a thought, I haven't tried it yet, but if you're using Win7 you could use the built in screen keyboard.  I think there may be an add-in for Vista as well.

dotScott has a beautiful Settings screen that I want to use parts of also.

Thank you!  If you need any of the source graphics, please let me know.  You'll need Adobe Fireworks or Photoshop to manipulate the pages and layers.

Best of luck and keep up the good work!

I have started with Gerry's Aqua set and have used much of the graphics as well as modified some for my needs. I don't know the protocol, I don't want to step on anyone's toes or take anyone's work and use it inappropriately.

Feel free to do what you want with it.

This is just the beginning, I can't believe how long it has taken me to just do this screen image.

Imagine how long it took me to do it from scratch. 

Just a thought, I haven't tried it yet, but if you're using Win7 you could use the built in screen keyboard.

That's good to know. I am using XP, but I may want to switch to 7 for the keyboard

If you need any of the source graphics, please let me know.

Thanks! I'll keep it in mind.

Feel free to do what you want with it.

Thanks Gerry, you're both very generous.

Imagine how long it took me to do it from scratch.  

I don't think I can imagine!

So I've been trying out different looks. After combining the elegantly simple appearance that dotScott is using and the colorful buttons/LEDs that Gerry has, I have a new look. I am still playing with different colored "skins" but the buttons/LEDs are unchanged while the DRO background and panel background is variable.

I am sufficiently satisfied with the RunScreen that now I'll work on the others. It is still only am image with no functionality, so I still have a lot of work to do.

Man... this takes forEVER!

Looking good!  Keep up the good work.

Just some things to consider.  It's just my experience at creating GUIs for business apps that you want to make your labels slightly less visible than the data elements.  It makes the important information more easily accessible.   Normal labels and bold data or differentiate the two using color.  If you notice in my GUI and several others that the data elements are highlighted either by the DRO background or in my case I have light gray labels and bright red data.  Also remember when creating the interface to make all your DRO areas the same color.  You can only define a single background color for DROs and other elements.

you want to make your labels slightly less visible than the data elements.

Thanks! Good suggestion. I am familiar with the concept and have been experimenting with colors for that reason.

It gets interesting when the labels are also sometimes data as well. For example, I plan to have the LEDs for the axes be yellow then turn green when they are homed. But then they are also the label for the DRO for their respective axis. It is a balancing act to find the best method of visibility so the green axis label doesn't overpower the DRO but still easily distinguish when it is homed.

I haven't yet experimented with font color though.

Font color is easy as it's a global setting.  You'll find the right one.  Try a medium blue with your color scheme and lighten your labels.  Should pop

Thanks Scott,

I took another look at your screen. I see that contrast (between font color and background) plays an important roll in how something stands out. Also, you use the size of the label or object to affect visibility.

So I will play with the relative size of the label verses its DRO along with choosing colors that contrast sharply or softly, depending on what is desired.

I haven't yet been satisfied with that aspect of the screen. But to this point I have been focusing on the layout and what functions to include. Now that I'm happy with the RunScreen, I'll take your tips and do some experimenting.