GUI for PlasmaC - QtPlasmac

snowgoer540 wrote:

rodw wrote:

I don't understand why we are wasting screen real estate for a spindle and associated tools on a plasma machine. If you must retain it, put it on a secondary tab that is not displayed by default.

Are you commenting on my concept specifically, or the Plasmac GUI in general? Just ask because I didnt have any spindle stuff on my concept.

On both. I did not see the laser reference on yours.

I am way late here so I may have missed some points.

1. How is the machine taken out of or E-stopped?
2. How are the axis/machine homed?
3. How are the work piece offsets entered?
4. What about the reverse run? This is a very use full feature for cutting error recovery!

High contrast and brightness rule for old guys.

John

islander261 wrote: I am way late here so I may have missed some points.

1. How is the machine taken out of or E-stopped?
2. How are the axis/machine homed?
3. How are the work piece offsets entered?
4. What about the reverse run? This is a very use full feature for cutting error recovery!

High contrast and brightness rule for old guys.

John

Hey John,

I hit most of that in the explanatory slides. But I'll touch here quick.

1. click the machine button, if it's not physically E-Stopped, it will allow it to power on. If it's physically e-stopped you'd get an error message telling you such. E-Stops should be physical hardware for maximum safety. I never understood the need for the software estop.

2. Click Reference. Right now I have them individually, but I could add a home all as well. I was waiting to hear Phil's comments.

3. Either click Zero Axis, or you could type manually in the DRO window is the current plan.

4. Good question. I dont have reverse run as I am on 2.8, but I Am open to suggestion as to what might be necessary there!

-Greg

snowgoer540 wrote:

Clive S wrote: I personally prefer the colour scheme in V1. to V2 as I find it easier to read.

Please take a look again and see if you still find it hard to read, I suspect some of that was due to it being a screen shot, and not the real deal.

Yes that is much better and is good but my preference is V1 because for me the yellow around the boxes stands out.

I personally don't like touch screens.

I am no commenting on the content as I think that is for the pro's that do it for a living .

I do hope this will get finished Thanks for the work you are putting into it.

Sorry for the long reply but it was easier to do it all in one post.

snowgoer540 wrote:
Attached is V2.0 with some explanation slides.
Let me know what you think!

I think it is a good starting point.
I like that it looks like it will fit in a 1024x768 window which I think we need to do. Obviously it needs to be resizable for higher resolution displays.

rodw wrote:
Definitely need a home all button.

islander261 wrote:
How are the axis/machine homed?
How are the work piece offsets entered?

With QtVCP the REF buttons are for touchoff and the HOME buttons are seperate so we would need a REF button and a HOME button for each axis plus a HOME all button.

islander261 wrote:
High contrast and brightness rule for old guys.

CliveS wrote:
I personally prefer the colour scheme in V1. to V2 as I find it easier to read.

It is relatively easy to change colours using stylesheets. We could probably supply a few to begin with but they can be customised. I think we need to concentrate on the layout now and we can sort out colours later.

rodw wrote:
Don't loose Phill's laser reference buttons. Thats all I use to pick 0,0.

They were actually part of Jims screen that I was thinking of using as the base. I would have removed or repurposed them.
forum.linuxcnc.org/qtvcp/38247-sample-qt...eens?start=20#157367

rodw wrote:
The concept of testing ohmic sensing to trigger the enable relay is going to be obsolete (it is for me now) with hyper sensing with a THCAD-5

That would be fine if everyone did the same but I am sure they won't.

rodw wrote:
Need a decent size button to accept MDI input

Agreed

rodw wrote:
I don't understand why we are wasting screen real estate for a spindle and associated tools on a plasma machine. If you must retain it, put it on a secondary tab that is not displayed by default.

Again, that was Jims and I would have removed or repurposed them.

rodw wrote:
I think the onscreen estop/machine on probably needs to be retained to keep Linuxcnc happy. If you do hit estop, you need to hit a screen button to confirm its been cleared to continue.

islander261 wrote:
How is the machine taken out of or E-stopped

Unfortunately I have to agree.
IMHO This was a mistake having this as a button LinuxCNC GUIs from the beginning but folk are used to it and that is what they want.
Estop should be physical Estop, not softbuttons. That is how I have it on my mill and lathes, the "Estop" button in AXIS is only used as an indicator.

islander261 wrote:
What about the reverse run? This is a very use full feature for cutting error recovery

I also think his should be on the main screen

CliveS wrote:
I personally don't like touch screens.

I can't comment because I don't have one but we do need to allow for them.

Well guys hopefully we can come to some sort of consensus on a layout then I can start coding.

phillc54 wrote: Sorry for the long reply but it was easier to do it all in one post.

Well guys hopefully we can come to some sort of consensus on a layout then I can start coding.

I can keep modifying what I started (I am happy to do so)!

I will try to work down the list of things you commented on and update the layout as I understand it. Phil can you double check me?

1. I am hearing Ref and Zero are synonomyous. Arent these just buttons? They can be coded to do whatever the action is when clicked. Does it matter if it's called Zero or Reference? I really dont know what I dont know, so that's some of the issue here. I dont really know how QtVCP works. But if it HAS to be called reference, I can change Zero to Ref, and then add a Home All button.

2. Am I reading to leave the 0,0 pick off? I Would think it's a bit redundant, as you can just click zero on the X and zero on the Y, correct?

3. Agree, I dont mind the ohmic light being there either way.

4. When you click the MDI Box, it could display an accept button to the right? Are we expecting a virtual keyboard to come up with touch based people? Otherwise one could just press enter.

5. My GUI didnt have spindle stuffs.

6. Looks like Phil you agree that estop buttons in software arent necessary? Thats how it reads, I think (it looks like you agree to what you quoted which was people asking for them, but then you said how you dont think they have a place either). Pathpilot doesnt have them, so it's possible.

7. I need guidance as to what the Reverse run GUI requires. I keep meaning to go to 2.9 and update, frankly I just dont know how without starting fresh. Screen grabs would help me here.

8. I think most of what I proposed is touch accessible. My layout was based on Pathpilot, which is touch friendly.

SO to recap I need to add:

1. Home All Button, maybe change Zero to Ref.
2. Plans for a Accept button on MDI box
3. Reverse Run GUI Requirements

Did I get that right?

-Greg