I have been searching for a possible solution to my problem and not had a whole lot of luck. For starters I have 7107 silver advantage CMM with 2014.1 PC DMIS. My problem is that i need a way to ask for an operator input of "YES" or "NO" without the operator having the ability to use the "Cancel" button that is in the input pop up screen. I need a definitive way to get a YES or NO answer without the operator being able to hit cancel and stop the program instead of answering. Any suggestions would be greatly appreciated
.
Sounds like you need new operators if they don't follow instructions.
But seriously, couldn't they always cancel the program another way, like the E-Stop button? Someone here might talk you through how to create a custom form without a cancel, but it could be dangerous not to be able to stop the program at all.
Sounds like you need new operators if they don't follow instructions.
But seriously, couldn't they always cancel the program another way, like the E-Stop button? Someone here might talk you through how to create a custom form without a cancel, but it could be dangerous not to be able to stop the program at all.
The CANCEL in the execution box isn't the same thing.
You CAN keep them from ignoring (canceling) that using CODE. Easiest way off the top of my head is to use numeric values as inputs (and clear previous instances in a setup menu). Such as:
1) YES
2) NO
And then put a label BEFORE the input and IF/GOTO after so that if they don't enter a valid number, it just keeps looping through that comment/input
here is an example I did for a part that may or may not have nuts put in it:
If a number less than 1 is entered or a number greater than 2, it loops back to label L1 and asks again.
(later in the program I use the value to branch for nuts or no-nuts)
I understand that they can still use the e-stop. i can explain in a little more detail the reason behind why i need what this setup. The company i work for does not use data page, and the way we gather and store our data is through our Hertzler system. At the very end of the program we have a tail made up of variables that go through and grab all the significant data that they want and stores them into those variables. Those variables are then sent through a program and made into a format that our hertzler program can understand. I know its a very round about method and it is very far from ideal. My boss wants me to set up a way for the operator to be able to say yes get this data and send it to our hertzler system or no do not send it to hertzler system and skip over our data variable tail. By skiping over the data tail it still stores our layout sheet in a paperless file on network so we can look back if we need to but doesn't go into our master system. If an operator hits the cancel button during that question then the program ends where it is and no data is captured what so ever in our paperless file or master system. So they want me to try and idiot proof this process by taking the away the ability for the operator to cancel the program, at least as much as possible.
I understand that they can still use the e-stop. i can explain in a little more detail the reason behind why i need what this setup. The company i work for does not use data page, and the way we gather and store our data is through our Hertzler system. At the very end of the program we have a tail made up of variables that go through and grab all the significant data that they want and stores them into those variables. Those variables are then sent through a program and made into a format that our hertzler program can understand. I know its a very round about method and it is very far from ideal. My boss wants me to set up a way for the operator to be able to say yes get this data and send it to our hertzler system or no do not send it to hertzler system and skip over our data variable tail. By skiping over the data tail it still stores our layout sheet in a paperless file on network so we can look back if we need to but doesn't go into our master system. If an operator hits the cancel button during that question then the program ends where it is and no data is captured what so ever in our paperless file or master system. So they want me to try and idiot proof this process by taking the away the ability for the operator to cancel the program, at least as much as possible.
see my previous post, it will work like a champ. After the IF/GOTO as shown, you simply add a label at the END of the program, past all that data collection stuff, and then use NO-NUTS (NO) value to send it to the label at the end of the program.
The CANCEL in the execution box isn't the same thing.
You CAN keep them from ignoring (canceling) that using CODE. Easiest way off the top of my head is to use numeric values as inputs (and clear previous instances in a setup menu). Such as: 1) YES 2) NO And then put a label BEFORE the input and IF/GOTO after so that if they don't enter a valid number, it just keeps looping through that comment/input
here is an example I did for a part that may or may not have nuts put in it:
If a number less than 1 is entered or a number greater than 2, it loops back to label L1 and asks again. (later in the program I use the value to branch for nuts or no-nuts)
This is the setup that we are currently using. the problem is in the comment input box that opens up. That comment box has a place to put in the input value and it has an OK button to accept the information or a Cancel button that just ends the program where its at. I need a way that the operator is not able to press the cancel button in the input pop up box.
I create the form with two radio buttons and a continue button, the form can only be moved on by pressing the continue button. If nothing is selected it loops back to the form again, if both are selected again it loops back. Of course the wrong one can always be selected
At the very end of the program we have a tail made up of variables that go through and grab all the significant data [...]. By skiping over the data tail it still stores our layout sheet in a paperless file on network [...]. If an operator hits the cancel button during that question then the program ends where it is and no data is captured what so ever in our paperless file or master system.
Why not move the question so that the "paperless file on network" is written
before you ask the question? Then it doesn't matter if they answer "NO" or "Cancel".
Here is a small applet that simply offers a YES NO dialog box. Optionally you can add the question to dialog through a command line parameter or use a file that is located in the same folder.
This is a standalone program that can be launched from another program to get a response of yes or no.
Example:
yesno.exe Do you want to print?
This will give you a YES NO dialog box with Do you want to Print" in the instruction window.
After the operator selects one of the choices, a text file called
yesno.txt is created with the answer on the first line. Other lines include the question and the date and time of the response.
You may also use a file instead of the command line parameter to ask the question. The file is named yesno.ask. Place the question to be asked on the first line only. It will be read in when the yesno.exe is launched.
When used in PCDMIS, use the external command function and select to have PCDMIS wait for the called program to close.
the yesno.exe file can be placed anywhere you want such as the folder where your parts are stored or if you organize your parts into their own folders, you could put it into each folder. There is no install required.
