To add to Pat's info:
PC-DMIS Blade is a 3-part system:
A) PC-DMIS (preferably 2015.1 or 2016!) with Blade option enabled on license to unlock special blade-only scanning and raw data exporting functions.
B) Blade software that takes the raw data, performs quite a lot of algorithm crunching, and delivers a full report.
C) Blade Runner software - a "front-end" simple operator interface that you setup to give the operators drop-down options to pick which blade to run so that it launches PC-DMIS to run the program, then launches Blade to crunch the results.
So you begin in PC-DMIS: your write a program to align the blade then perform an operation to extract nominal section data from the CAD file of the blade.
Then you add special Bladescan commands that use the nominal data to drive the probe to go scan those sections.
Then you add a command at the end of the program to export the raw data to a certain folder.
Then you do all kinds of fun special operations in Blade to setup the tolerancing. You end up with a bunch of special files with the same name but different extensions to keep track of.
The final step is writing a simple text file that drives Blade Runner to do it's thing.
The worst part is deciphering the blade blueprint and translating that to the cryptic abbreviations in Blade that stand for certain esoteric aerofoil dimensions like chord angle, leading edge thickness, etc - then customizing how they are calculated according t the blade designer's whimsy. That can get tricky.
To add to Pat's info:
PC-DMIS Blade is a 3-part system:
A) PC-DMIS (preferably 2015.1 or 2016!) with Blade option enabled on license to unlock special blade-only scanning and raw data exporting functions.
B) Blade software that takes the raw data, performs quite a lot of algorithm crunching, and delivers a full report.
C) Blade Runner software - a "front-end" simple operator interface that you setup to give the operators drop-down options to pick which blade to run so that it launches PC-DMIS to run the program, then launches Blade to crunch the results.
So you begin in PC-DMIS: your write a program to align the blade then perform an operation to extract nominal section data from the CAD file of the blade.
Then you add special Bladescan commands that use the nominal data to drive the probe to go scan those sections.
Then you add a command at the end of the program to export the raw data to a certain folder.
Then you do all kinds of fun special operations in Blade to setup the tolerancing. You end up with a bunch of special files with the same name but different extensions to keep track of.
The final step is writing a simple text file that drives Blade Runner to do it's thing.
The worst part is deciphering the blade blueprint and translating that to the cryptic abbreviations in Blade that stand for certain esoteric aerofoil dimensions like chord angle, leading edge thickness, etc - then customizing how they are calculated according t the blade designer's whimsy. That can get tricky.
