PC-DMISPlease share your ideas and suggestions to help us ensure we add features that will benefit the majority of users.
Thanks for your assistance in helping us shape the future...
We need a possibility that an user can only open the measuring routine (.PRG) for execution. User in that case means also an operator with full PC-DMIS access and administrator privileges.
Here is the story:
- Customer has 2 Leica trackers from us with PCDMIS.
- Customer constructs big machines for producing car tires. At several moments they measure the setup from their machine with the tracker. Works all fine.
- Next step: if they sell a VMI machine to a customer they think about also selling a Leica Tracker with PC-DMIS as a kind of measuring tool for their customers.
- They create the .PRG, and want that the routine can only be run in Operator Mode. Reason: they do not want that their customers can edit the original .PRG
- Note: the protected mode in PC-DMIS is not an option.
Another example is the ISO acceptance routines. We have to make sure that they can't be changed.
Command mode, exposing all parameters, can result in very lengthy routines, but it is fast to make edits. Summary mode was intended as a simplified view, but is seen as too slow to traverse into the tree to find the parameter to make edits. This is especially true when a lot of values are changing.
It has been requested (by a customer - I'm filing this on their behalf) that having a button on command mode - to only show important parameters by default (XYZ, IJK) - so each command is only a couple of lines long. To see all parameters, you would click the button, in order to see all the parameters (as now).
It is possible that such an enhancement could also include adding the icons you get in Summary Mode - to help commands stand out.
We're interested to see how many votes this idea would attract.
Your program is finished but some points or features were added and their out of numerical order.
A Re-number feature would put them all in ascending order.
Having the option to select a variable as a lighting option instead of a percentage in lighting parameters
For example, in vision, you save lighting settings to percentages you want. I would like to have a setting where I can pick a lighting that I want on with a preset variable. Like Bottom Light = V999. Then the programmer can assign the variable at the top of the program.
So instead of it saying "Bottom Light=<off, 100, on>" it would say "Bottom Light=<off,V999, on>"
Instead of having to manually type this for every feature, it will hold the value as a variable rather than a number. This could potentially solve all lighting issues going forward and make it super easy for a programmer to update/change programs if needed. And if possible
Command mode has visual challenges. Small text (fonts), while difficult to see, is good for seeing the whole program - especially features with long widths across. Large text (fonts) is good for detail and visibility, but the field of view gets cropped.
Changing fonts by pressing F6, then clicking "Edit Window", and THEN selecting the font size, is archaic.
A huge improvement would be if Command Mode allowed Dynamic Zoom (or Font Scaling) using <CTRL> + Mouse Scroll. Examples of this are available in Visual Studio's editor, MS Word, and Notepad++.
Note the attached MP4 of Visual Studio scrolling in and out of code details.
Customer support service by UserEcho