Difference between revisions of "Supravision Network Protocol"
Line 9: | Line 9: | ||
==Intro== | ==Intro== | ||
− | + | ||
This is a protocol that specifies how to communicate with measuring centers software packages like [[VTube-LASER]] (our software for FARO), Supravision software, and DOCS software (ROMER) using command and data files. | This is a protocol that specifies how to communicate with measuring centers software packages like [[VTube-LASER]] (our software for FARO), Supravision software, and DOCS software (ROMER) using command and data files. | ||
Line 16: | Line 16: | ||
==Design Purpose== | ==Design Purpose== | ||
− | + | ||
This protocol is designed mainly for enabling bi-directional corrections loops with CNC bending machines with the measuring center as the master data center. It can be used for importing MASTER data from benders that support this feature. | This protocol is designed mainly for enabling bi-directional corrections loops with CNC bending machines with the measuring center as the master data center. It can be used for importing MASTER data from benders that support this feature. | ||
− | + | ||
<br><br> | <br><br> | ||
==Capabilities/Limitations== | ==Capabilities/Limitations== | ||
− | + | ||
The SVNET protocol... | The SVNET protocol... | ||
− | + | ||
*SUPPORTS up to 99 benders<br><br> | *SUPPORTS up to 99 benders<br><br> | ||
Line 41: | Line 41: | ||
− | + | ||
− | + | ||
<br><br> | <br><br> | ||
==Networking Issues== | ==Networking Issues== | ||
− | + | ||
<li>'''STANDARD LAN CONNECTION:''' The protocol requires a standard network connection between the bender and the measuring center running Supravision. In many cases, we place our Benderlink software between Supravision and the bender that never has supported the SVNET protocol. The protocol requires that both computers have access to a shared folder over the network. | <li>'''STANDARD LAN CONNECTION:''' The protocol requires a standard network connection between the bender and the measuring center running Supravision. In many cases, we place our Benderlink software between Supravision and the bender that never has supported the SVNET protocol. The protocol requires that both computers have access to a shared folder over the network. | ||
Line 75: | Line 75: | ||
<li>'''[[UNC]] or Mapped Drive?:''' [[UNC]] means (Universal Naming Convention)[http://www.google.com/search?hl=en&lr=&defl=en&q=define:UNC&sa=X&oi=glossary_definition&ct=title] We prefer to use [[UNC]] style paths over mapped drives. They are more descriptive, and your computer may lose the address associated with the mapped drive if the network connection fails.</li> | <li>'''[[UNC]] or Mapped Drive?:''' [[UNC]] means (Universal Naming Convention)[http://www.google.com/search?hl=en&lr=&defl=en&q=define:UNC&sa=X&oi=glossary_definition&ct=title] We prefer to use [[UNC]] style paths over mapped drives. They are more descriptive, and your computer may lose the address associated with the mapped drive if the network connection fails.</li> | ||
− | + | ||
<br><br> | <br><br> | ||
==History== | ==History== | ||
− | + | ||
1 - The older versions of the DOS-based Supravision software did not support SVNET communications. It was a later addition by Foad Rekabi. | 1 - The older versions of the DOS-based Supravision software did not support SVNET communications. It was a later addition by Foad Rekabi. | ||
Line 86: | Line 86: | ||
2 - Not all versions of the measuring center software packages have the SVNET protocol feature support it properly. It is important that users check their version of Supravision to be sure that what they are using a version of Supravision that uses SVNET properly. This is true for early versions of the DOS and Windows versions of Supravision. | 2 - Not all versions of the measuring center software packages have the SVNET protocol feature support it properly. It is important that users check their version of Supravision to be sure that what they are using a version of Supravision that uses SVNET properly. This is true for early versions of the DOS and Windows versions of Supravision. | ||
− | + | ||
<br><br> | <br><br> |
Revision as of 17:47, 13 July 2011
Contents |
Intro
This is a protocol that specifies how to communicate with measuring centers software packages like VTube-LASER (our software for FARO), Supravision software, and DOCS software (ROMER) using command and data files.
Design Purpose
This protocol is designed mainly for enabling bi-directional corrections loops with CNC bending machines with the measuring center as the master data center. It can be used for importing MASTER data from benders that support this feature.
Capabilities/Limitations
The SVNET protocol...
- SUPPORTS up to 99 benders
- Some versions of Supravision for Windows software cannot address COM ports above 9 without producing an error during communications. This is, no doubt, an unintentional bug in some versions of Supravision. This is only a serious problem if you plan on communicating with more than 9 benders.
- The VTube-LASER implementation of SVNET can handle any number of COM ports.
- SENDS master xyz, corrected LRA, tube diameter, cut length, and bend radii to the bender
- RECALLS - For Supravision and DOCS, recalls occur before they perform a new measure. This approach is less logical than the recall approach by other measuring centers (see the "Compare" note below). The data recalled is corrected LRA, tube diameter, cut length, and bend radii
- RECALLS - OTHER MEASURING CENTERS: The VTube-LASER and Eaton Leonard Laservision only recalls after a measure and during the correction - and ONLY if the correction needs to occur. We consider the VTube-LASER approach superior because not every measurement will result in the need for a recall from the bender. For example, if the part qualifies to be within tolerance, then there is no need for a recall.)
- EL FLOATING POINT Problem: Some versions of Supravision cannot properly handle the floating point conversion of incoming values from the older EL legacy protocol (which does not follow the IEEE 754 protocol for binary floating point arithmetic). This problem explains why some Eaton Leonard values may be reset to zero or some huge value when transmitting back to the EL Velog, EL-2000, or Premier controls from Supravision.
Networking Issues
History
1 - The older versions of the DOS-based Supravision software did not support SVNET communications. It was a later addition by Foad Rekabi.
2 - Not all versions of the measuring center software packages have the SVNET protocol feature support it properly. It is important that users check their version of Supravision to be sure that what they are using a version of Supravision that uses SVNET properly. This is true for early versions of the DOS and Windows versions of Supravision.
VTube-LASER Versions to Use for SVNET
|
DOC Versions to Use for SVNET
DOCS 2.1 and earlier |
|
DOCS 2.2 |
|
DOCS 2.3 |
|
SV Versions to Use/Not Use for SVNET
Windows Version 6 |
|
Windows Version 5.00.0 |
|
DOS Version 4.00.9398 |
|
DOS Version 3.58.9570 |
Download sv_3_48.zip to update your DOS Supravision executable. The zip file contains a text file and VR.EXE, which is the Supravision file to replace your existing older version of SV for DOS. |