[Ri...] Posted May 23 Share Posted May 23 Hey Crazies, I have an interesting question: has anyone ever started an inspection of a part with say an active sensor, and then stop mid run, swap over to the RDS, and continue the run? I know swapping sensors on the RDS (XXT to LineScan or DotScan) is no issue, but primary sensor swap seems like it would at least be interesting to test. Anyone tried this? If so, what kind of results did you see? Thanks. Link to comment Share on other sites More sharing options...
[Ky...] Posted May 23 Share Posted May 23 Hello Richard, Coincidentally enough, I believe we have gotten this question before and, no, it is not a supported feature. You cannot hot swap sensors (specifically from VAST/VAST XT/VAST XTR to RDS). When you switch it, you also have to reconnect to the machine tab, or more accurately a different machine tab since if you reconnect to the same machine tab, there is a good chance you'll end up accidentally delete the styli since it is recognizing a different sensor. Hope you find that helpful. Link to comment Share on other sites More sharing options...
[Ri...] Posted May 23 Author Share Posted May 23 Please sign in to view this quote. Hi Kyle, I'm aware of how you swap from one sensor to another. I'm more so just interested in if anyone has attempted to measure everything with the first sensor, save, close Calypso, swap sensors, open Calypso, open measurement plan, and continue running. I have a backup plan on how you could do it via the Point Set option, or worst case taking all of the raw points into Inspect and performing the evaluation there. I like thinking outside the box - doesn't mean it's right or feasible, but it's fun to test concepts and see the behavior. Link to comment Share on other sites More sharing options...
[Ky...] Posted May 23 Share Posted May 23 Hey Richard, I understand a bit better now. The short answer is no, I at least have never heard of it attempted, much less working. At the very least, you would have to do trick the stylus database to think it had stylus systems with the same name and stylus numbers. Worse case scenario, the differences on how you plug in the machines might cause issues with results if you are comparing results from one probe head to another. Depending on the exact situation, you might be able to do something similar with the "merged measurement plan" ability in Calypso, but the work flow would be to make 2 separate programs, run 1, swap heads, run the other (they'd probably have to have the same features in the base alignment, mind), load in the data into the merged measurement plan and then it can calculate results. I did this a few months ago as part of a class. Hope that helps. Link to comment Share on other sites More sharing options...
[To...] Posted May 23 Share Posted May 23 I think there could possibly be an issue with the probe data. In other words, if you do a reference sphere position with one sensor, then execute a CNC reference sphere position with a different sensor, the MasterProbe doesn't go to the stored position. It seems like it's close in the X position, about 60mm off in the Y position, and I haven't gone far enough to see how close the Z is. Link to comment Share on other sites More sharing options...
[Je...] Posted June 4 Share Posted June 4 There are ways you could do this programmatically (much like what Kyle suggested) but it would not be dynamic. The break point would be very specific unless you worked in some very complex PCM and alternate measurement strategies. You would execute a portion of the program, save the measured points, save/close/drives off/swap/drives on/reconnect/open/load measured points/start inspection (uncheck "clear existing"). There would be several gaps that need to be filled in here and errors suppressed. Not "easy" but it has been done in some internal trials and can be done with some patience and creativity. I've personally worked on some experiments to automate the routine but ultimately the drives and connection portion of the routine are quite difficult to navigate around (intentionally). There is definitely a benefit to having the RDS enabled for speed and limited stylus need then utilizing the VAST for longer reach or increased accuracy/performance. This is not lost on our development teams 😉 Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in