Difference between revisions of "Supravision Network Protocol"

From ATTWiki
Jump to: navigation, search
(→‎SV Versions to Use/Not Use for SVNET)
(→‎SV Versions to Use/Not Use for SVNET)
Line 163: Line 163:
 
<ol>  
 
<ol>  
 
<li>All versions of 6 OK for Use with minor limitations (Use this version or HIGHER)</li><br>
 
<li>All versions of 6 OK for Use with minor limitations (Use this version or HIGHER)</li><br>
−
<li>Details: The only known issue is that a PART COMMENT of more than 95 characters in length will crash SV 6.  Some setup technicians will enter much more than 95 characters.
+
<li>Details: The only known issue is that a PART COMMENT of more than 95 characters in length will crash SV 6.  (Some bender setup technicians will enter much more than 95 characters in their BendPro setups - causing SV 6 to crash during a RECALL.)</li>
−
</li>
+
 
</ol>
 
</ol>
 
</td>
 
</td>

Revision as of 20:55, 9 October 2013

Svnetwork logo.jpg

Contents


The Advanced Tubular VTube-LASER works with FARO and is a direct replacement with Supravision. It uses the Supravision Network protocol.
The original DOS Supravision main menu (circa 1980s and '90s)
The newer Windows Supravision main menu (circa late 1990s to current)


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

  • 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.


  • MEASURING CENTER IS MASTER/CLIENT: Typically the measuring center is used as the master controller of the connection. It typically initiates all RECALL and SEND requests between itself and the bender. This would make Supravision software the CLIENT. It is the one sending data and making requests. The bender is usually the SERVER because it "listens" (or monitors) for commands from Supravision.


  • WHY NOT USE BENDER AS CLIENTS?: There are few customers that use the protocol in the opposite way. They make the bender the CLIENT and initiate all communications from the bender. We never recommend this method of communication, because I believe that the measuring center is the MASTER and should be asking for data only when it needs it. It should also only SEND data when it wants to correct the bender.


  • PERFORMANCE ISSUES WHEN NETWORK IS DOWN: In addition to this, there can be huge drags in SV performance when SV is monitoring for commands from benders. This problem occurs when the network connection is poor or lost. If any bender connections are ENABLED in Supravision, and the network is down, SV slows to a crawl because [i]Windows[/i] slows the Internet Protocol to crawl. I have advised Romer of this issue, and they may resolve the issue in there new DOCS software. Hopefully they will design the DOCS software so that it does not monitor for commands from the bender, except for when DOCS requests a RECALL of data.)


  • SHARED FOLDER SETUP: Most customers don't mind if the bender's root drive is shared on the network. Supravision is then configured to look at this shared drive over the network. This setup minimizes the possibility that a Windows-base bender controller will slow down or shutdown bender communications if the network connection fails. Some bender control developers prefer to do the opposite; they request that the bender look through the network at a shared connection on the ROMER computer. This method works well for ROMER because it creates a setup where the ROMER computer will always have a connection and never bog down - even if the network is slow or down.


  • UNC or Mapped Drive?: UNC means (Universal Naming Convention)[1] 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.




    • 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

    VTube-LASER

    1. All versions support full SVNET protocol

    DOC Versions to Use for SVNET

    DOCS 2.1 and earlier

    1. Does not support SVNET protocol

    2. Details: Switch to version 2.2 or higher.

    DOCS 2.2

    1. All versions of DOCS 2.2 are OK for use (Use this version or HIGHER) -

    2. Details: No known issues exist for the Supravision Network Protocol in this version. Requires TUBE SHOP MANAGER add-on software

    DOCS 2.3

    1. This was BETA software (as of the time we added this note)

    2. Details: It was not released to the general public yet. However, it should work with the SVNET protocol when released. Requires TUBE SHOP MANAGER add-on software

    SV Versions to Use/Not Use for SVNET

    Windows Version 6

    1. All versions of 6 OK for Use with minor limitations (Use this version or HIGHER)

    2. Details: The only known issue is that a PART COMMENT of more than 95 characters in length will crash SV 6. (Some bender setup technicians will enter much more than 95 characters in their BendPro setups - causing SV 6 to crash during a RECALL.)

    Windows Version 5.00.0

    1. DO NOT USE (Upgrade to HIGHER version)

    2. Details: Causes the program to report "This program has performed an illegal function and will be shutdown" when it attempts to perform a Supravsion Network communication.

    DOS Version 4.00.9398

    1. DO NOT USE (Upgrade to HIGHER version)

    2. Details: No TIMEOUT Recognized for Supravision Network

    3. File Info: VR.EXE 364,080 05-22-98 12:19p

    DOS Version 3.58.9570

    1. OK for Use (Use this version or HIGHER)

    2. Details: Older versions will not work properly or don't have the feature

    3. File Info: VR.EXE 375KB 11/2/98 2:49PM

      4. 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.

    Retrieved from "http://www.advancedtubular.wiki/index.php?title=Supravision_Network_Protocol&oldid=23090"