Difference between revisions of "Diagnosing SVNET Data Errors"
From ATTWiki
(→Diagnosing Incorrect Data) |
|||
| Line 1: | Line 1: | ||
[[image:cncbender_logo.jpg|400px]]<br> | [[image:cncbender_logo.jpg|400px]]<br> | ||
| − | ===Diagnosing Incorrect Data=== | + | ===Diagnosing Incorrect Data in a Supravision-Based Communication=== |
After a transmission to CNC Bender from an SVNET-based measuring center, follow these steps:<br> | After a transmission to CNC Bender from an SVNET-based measuring center, follow these steps:<br> | ||
Revision as of 18:36, 17 May 2009
Contents |
Diagnosing Incorrect Data in a Supravision-Based Communication
After a transmission to CNC Bender from an SVNET-based measuring center, follow these steps:
- - At the bender, skip the AUTOBUILD (which automatically saves the part)
- - At the bender, reload the part before it was corrected.
- - At the bender observe the data to be sure it is reasonable. Look at the values of both nominal and adjusted. Especially look at the values that were received incorrectly last time.
- - At the measuring center - Observe the corrected bender data to see if it is reasonable.
- - If it is, then send it to the bender.
- - At the bender, check the received values. Are they what you expected?
Corrected Data
In SVNET communications, the corrections are always made at CNC Bender to the adjusted data only. However, the determination of how much adjustment to apply is calculated by adding the nominal and adjusted first before comparing the data to the incoming Supravision data.
=Bender Numbers
Be sure that each bender has a unique number in Benderlink. Two or more benders answering the measuring center at the same time will cause problems.
