Difference between revisions of "How to change the Supravision Configuration Setup"

Revision as of 19:27, 12 September 2012

It is possible to change the configuration of Supravision two ways - either inside Supravision (like in Bender Setup), or by manually editing the CONFIG.SV file.

Editing the config.sv file is more powerful, so we will cover that method.

Manually Editing the Config.sv File in an Editor

The bender setup can be changed in the config.sv file in the the same folder that the Supravision executable is running. Be very careful with this - as an incorrect entry will often cause Supravision to bomb at startup.

Sample config.sv contents:

$user ABC Tube Fab
$mach STINGER II
$rmrd C:\Program Files\Supravision 5\
$prtd C:\Program Files\Supravision 5\parts\
$altp 
$rptd C:\Supravision 5\reports\
$anad C:\Program Files\Supravision 5\analysis\
$igsd C:\Program Files\Supravision 5\iges\
$clbt calibrmr.bat
$ssbt \ss3.bat
$lang ENG
$ptns 8 8 8 8 32
$tscr 1018
$pmos 1
$prtr EPSON
$unit E
$deci N
$prob 5
$dncn 99
$ccod 1054
$optm 1
$msgm 0
$msvd 0
$mssm 0
$mses 0
$skdv 1
$snds 1.0000
$bndr 12
 2 ELST   1  20 "VB100" ""
 3f8 NTSV   0  30 "KEINS 30 Left" ""
   9 ELST   0  30 "KEINS 10 1" ""
  11 ELST   0  30 "KEINS 10 2" ""
 3f8 NTSV   1  30 "KEINS 10 Righ" "c:\"
 3f8 NTSV   1  30 "KEINS 10 Left" "c:\"
 3f8 NTSV   1  30 "SMT 300 Right" "\\Left2\C\CNC\svparts"
 3f8 NTSV   1  30 "SMT 300 Left" "\\Left1\C\CNC\svparts"
  4 ELST   1  20 "VB100" ""
  3 ELST   1  20 "VB100" ""
  11 NTSV   0  20 "VB100" ""
 3f8 NTSV   0  30 " General Inspection" ""

General Rules for Configuration

1. Be sure Supravision is NOT running when you edit and save this file.
   
   
2. Do not change any parameter that you are unsure about (see the warning above). If you do make a change that you are unsure about - be sure you know how to get back to the original file contents. (Make a backup file.)

Rules for Configuring the Bender Network

1. Change the benderlink configuration in the $bndr section
   
   
2. The number of rows that follow the $bndr section must match the number following the $bndr name. This sample file shows "12". There are 12 rows below. If the row count does not match, then SV will probably bomb at startup. You can add or delete rows in this section. Just be sure that the number of rows matches the number following the $bndr section value.
   
   
3. Supravision can handle up to 99 benders.
   
   
4. Each row represents one bender. Row 1 represents the configuration for bender 1. Row 2 is for bender 2, etc.
   
   
5. The columns are SPACE separated. The number of spaces is not significant.
   
   
6. VALUE 1: The first value on the left in a row is the COM port number. The COM port is either a HEX address (old method for direct addressing of a physical COM port), or a HEX number (not a decimal number). For example, "10" is decimal port 16. This value has no effect when using the Supravision Network Protocol.
   
   
7. VALUE 2: The second value is the COMMUNICATIONS PROTOCOL. "NTSV" indicates the Supravision network protocol. "ELST" indicates the standard Eaton Leonard protocol for single radius benders. "NSTD" means non-standard - for unknown protocols.
   
   
8. VALUE 3: The third value is the enable byte. Set this value to 1 to enable and 0 to disable communications. Please remember that COM-based protocols should reference a good port number - or Supravision will slow down trying access a non-existent COM port.
   
   
9. VALUE 4: The forth value is the timeout. Set this value to a reasonable time to allow communications to complete before SV times out. 20 seconds is good for most protocols.
   
   
10. VALUE 5: The fifth value is the name of the bender. This has no impact on the protocol - but is for the benefit of the operator to know which bender is communicated with. This value should always be enclosed in quotations.
    
    
11. VALUE 6: The sixth value is the SV Network PATH. The path can be a drive (like "c:\") or a UNC name (like "\\SMT14905\c"). The path needs to be legal - or Supravision will display errors at start-up - and performance will also suffer. This path has no effect on COM-based protocols (like ELST).