hexagon logo
Register Sign in
  • Replies 10 replies
  • Subscribers 222 subscribers
  • Views 135 views
  • Users 0 members are here
Options
Related

Discussion> Implement colors for easier adjustment?

Chris_BMA
Hello!

Im quite new here to the forum and this is my first official post.
I've been thinking quite alot about how to make the PC-DMIS program easier for operators and users who are not to educated in the program itself.

In my type of work area, I have around 12-15 people who are using the measurement machine.
And not everybody are well educated in the program so they can use it to find out the information they want to.

Also if a result is not correct and the report only says "from point A to point B is not correct" and to the other personel they dont know what to do.
And if im not around it's quite annoying cause I myself cant handle to much support via telephone, im much more useful behind a computer with the same parameters.

So I have a solution to discuss with the others and I want to throw around the ball.

The suggestion I want to bring is in text aswell as Im giving you some picture examples.

Suggestion:
*Picture one*
While programming a program I think there should be a possiblity to give every code a color (for example in this the Teal and Red dot - At The Moment in PC-DMIS they are used for Bookmark aswell as a breakpoint)
But lets forget what they are for the moment and join me in on this idee, instead the colors will represent a Tempo in the ongoing process of the NC Machines.
*Picture two*
So when I add to the result that "Plane8 to Plane10 (X-axel)" the Teal and the red dots are shown besides the result.
That's because "Plane8" in this case are from a Tempo 1 machining while "Plane10" is from the Tempo 2 machining.

In the result below the first one we have "Plane8" which we know is Temp 1 to "Plane7" In this case we havnt placed any color on "Plane7" but still the result will show a teal dot cause "Plane8" is defined as a Tempo 1 and we then can assume that "Plane7" is aswell.

This may be the weakness in this method, if a code is without a color for which tempo its from this form turns out just like coding without colors at all.

Even tho I think this is a potensial to help alot of programmers out there who have other personel who aint trained in programming the Machine and understands it to a potent way.

Attached Files
Picture one*

Picture two*
  • Hej Christofer och välkommen till forumet!

    Would it help your colleagues if you named the features after which tempo they reside from?
    Example, rename "PLAN8" to "TEMPO1 PLAN8"?

    If this is not enough, you could (theoretically) create a custom label for your report, where you include a small BASIC expression
    that checks for the naming convention above and adds a graphic to it.
  • Thank you, I will enjoy my stay here! Slight smile

    It's not impossible to make that possible, but colors are much more rememberable than tons of text, dont you agree?
    Tho I have never tried to make Custom labels tho. I will look into that.

    I have been doing report text which states where operator should look on a drawing. But since Drawings does not state which tempo we make the detail in, it brings alot of question marks and lots of questions to me.

    Im hardly in touch with the ones programming the NC, tho I can make programs which will review what tempo is where when they are done with it, but its alot of extra work if I need to rename many code names such as "PLAN8" to "Tempo1 PLAN8" to like 250 codes.

    With a coloring system just lite the "marking" selection I can instead CTRL + Left select my sections of "TEMPO1" and then right-click and go to a color section and make all Teal dotted and then the rest Red dotted if I only have two Tempos.
  • Well, you can always file it as an enhancement request to tech support.
  • colors are much more rememberable than tons of text, dont you agree?

    Not for the color blind, or those printing out in B/W...

    Welcome, by the way - I hope you know the Support phone number Slight smile
  • Not for the color blind, or those printing out in B/W...

    Welcome, by the way - I hope you know the Support phone number Slight smile

    Lol!
  • I would say Identify features according to colors you would like for them is easy in the Edit Window. Transferring them to your report is a horse of a different color. (pun intended)
    As vpt.se suggests, it could be done color-wise with custom report/label perhaps?
    Also, AndersI has good point with B/W printouts or those not so able to differentiate color. Personally? I'd be lost without color in the Edit Window. Everyone else doesn't care, as long as it's not RED. Sunglasses
    and a welcome as well to you, Chris.....
  • Also to add into the fact, that the symbols can be in different shapes (helps out in a B/W printout)
    and to those who are unfortunate to have color blindness, its mostly to colors of red-green, If you have a great case of color-blindess you might not even see a report thats red so you still have to rely on the bars and the other visuals such as shapes.

    So combinations of both colors and shapes should work out pure-theoretically?

    Sealevel: I hardly have any colors in my edit window, I mainly combine my knowledge of CAD and editing to find everything I need and manipulate it in the way I want to. So the only colors I use are Black/White and teal (when codes are marked and skipped)

    (And yeah AndersI - I know the number ^.^)
  • What you can do, is to take a look at the PPAP report template.
    The PPAP report uses the "OK" and "NOK" symbols to differentiate between the two by looking at (I think) the DEV-value.

    If you don't use a naming convention, you will have to add the symbols manually for each label, which is cumbersome to say at least.
  • I really like the PPAP concept, (Im amazed now cause no one has ever showed me how to switch between report layouts and I just figured it out myself Smiley)
    It's good an clean, tho the position accuracy dimensionals does not show if they are OK or rejected when they show the measurements.
    Only the position accuracy result itself. (for a customer not used to reading isnt it a problem cause not everything has a cross if it's OK or a Reject?)

    Even tho the problem stands in the simplicity of a PPAP report, Good show if its good or not.
    But no report text is show. So even in the use of a PPAP report we can use some to help the ground-stone of my discussion thread, but the problem still stands.
    but now with the problem that we have no information to the other users.
  • The PPAP-report won't help you in this case, but it gives you an idea of how it could be done and applied to your issue.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement