hexagon logo
Register Sign in
  • Replies 2 replies
  • Subscribers 221 subscribers
  • Views 51 views
  • Users 0 members are here
Options
Related

Tip Radius Error

Marken199

I started getting this message box after I inspect an airfoil. It has the correct radius there and if I click OK, everything works. But why is it doing this.
I am using PCDMIS 2019.R1.... Bladerunner 5.4 and BLADE 5.0.79.0. We have another CMM that has same software and it does not do this
running same program. Not sure what software is generating this message.. Is it PCDMIS Bladerunner or Blade.?

Thanks for any help.
Parents
  • Hello, not sure if you resolved this yet or not (it's been a while since your post).

    From what I've read in the past, this happens if you let Bladerunner find the probe radius from the program ("TIP2" - why 2? No idea), and have any 'junk' probe files, though I think I've had it happen even with all probe files being good.


    The main solution is to 'hard-code' the probe radius into the brun.ini file. This is near the end of the file, under 'Miscellaneous'. This works fine if you only ever use one probe size for scanning, but we don't, so the workaround I came up with, was to make a brun.ini for each probe size, and let PC-DMIS decide which brun.ini to use based on the currently loaded probe's radius. 

    $$ NO,
            Editing brun.ini to ensure proper probe radius.
            THIS ASSUMES A 'SETUP' brun FILE EXISTS WITH THE DESIRED PROBE RADIUS
            For example: "brun3mm.ini" assumes 3mm probe tip diameter and has
            "ProbeR = .059055" specified.
            (this needs to be inserted below 'LOADPROBE' and above 'PRINT' command!!!)

            ASSIGN/PD=ROUND(PROBEDATA("DIAM")*25.4)
            ASSIGN/BRUN="C:\\Bladerunner\\brun"+PD+"mm.ini"
            FILE/COPY,BRUN,C:\BladeRunner\brun.ini,OVERWRITE​


    So, basically you start off with your base "brun.ini", and copy/paste it for each probe radius needed, renaming those files as "brun1mm.ini", "brun2mm.ini", "brun3mm.ini, etc... and each of those has the corresponding probe radius declared (these should all be located in the "C:\Bladerunner" directory). When you run your airfoil program, PC-DMIS checks what your loaded probe size is, then copies the corresponding brunXmm.ini file, and renames it "brun.ini".

    This may seem silly and circuitous, but that is only because it is. However, it also works. If you end up using different probe sizes for different parts, you will see some wacky profile plots when it tries to spline your ball center data to the wrong radius (unless you take the time to edit brun.ini every time it changes).
Reply
  • Hello, not sure if you resolved this yet or not (it's been a while since your post).

    From what I've read in the past, this happens if you let Bladerunner find the probe radius from the program ("TIP2" - why 2? No idea), and have any 'junk' probe files, though I think I've had it happen even with all probe files being good.


    The main solution is to 'hard-code' the probe radius into the brun.ini file. This is near the end of the file, under 'Miscellaneous'. This works fine if you only ever use one probe size for scanning, but we don't, so the workaround I came up with, was to make a brun.ini for each probe size, and let PC-DMIS decide which brun.ini to use based on the currently loaded probe's radius. 

    $$ NO,
            Editing brun.ini to ensure proper probe radius.
            THIS ASSUMES A 'SETUP' brun FILE EXISTS WITH THE DESIRED PROBE RADIUS
            For example: "brun3mm.ini" assumes 3mm probe tip diameter and has
            "ProbeR = .059055" specified.
            (this needs to be inserted below 'LOADPROBE' and above 'PRINT' command!!!)

            ASSIGN/PD=ROUND(PROBEDATA("DIAM")*25.4)
            ASSIGN/BRUN="C:\\Bladerunner\\brun"+PD+"mm.ini"
            FILE/COPY,BRUN,C:\BladeRunner\brun.ini,OVERWRITE​


    So, basically you start off with your base "brun.ini", and copy/paste it for each probe radius needed, renaming those files as "brun1mm.ini", "brun2mm.ini", "brun3mm.ini, etc... and each of those has the corresponding probe radius declared (these should all be located in the "C:\Bladerunner" directory). When you run your airfoil program, PC-DMIS checks what your loaded probe size is, then copies the corresponding brunXmm.ini file, and renames it "brun.ini".

    This may seem silly and circuitous, but that is only because it is. However, it also works. If you end up using different probe sizes for different parts, you will see some wacky profile plots when it tries to spline your ball center data to the wrong radius (unless you take the time to edit brun.ini every time it changes).
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement