Author: Srini Komandur
Created: April 14 1988
Revised: January 14 1997
Last Printing: January 30, 1997
You will always find the most updated version of this document at http://www.impactsys.com
1.0
Link ID List for Impact-Host communication software on CD-net2
We have documented a link board for CD-Net 2 links. We envisage being able to put ALL the standard links on this board and simply use "setup data" to select which link is required. A link is chosen using the "link type" setup data item which asks for a value between 0 and 49. The following table gives the numeric Link Type IDs for the major link types. Other IDs, will be allocated as required; some of the links need additional link dependent setup data.
0-9 ACCURAY
0: Current standard link as per License Agreement
10-19 MEASUREX
10 LEVANT SOYSAL(old/new), SCL, SPCL
11 200/100 link
20-29 SENTROL
20 SIM(snooper)
30-39 IMPACT
30 Type 1, Where Type 1 refers to the old stand-alone protocol, usually from HP Measurex / BACI boards.
31 S type
32 Binary link (Special. Check with engineering before use.)
40-49 Miscellaneous
40 YEW (Japan)
2.0
Setup Data for Net 2 Links
2.1
Network Setup Data
Each setup data item is listed in the order they appear while entering setup
data through the CD Opcenter or maintenance panel or monitor port. A
functional description of each item along with the limits are provided.
Wherever possible, an example is provided. Finally, Voikkaa system is taken as
example and the corresponding setup data entries are illustrated.
2.11
Path count
Path count Limits 1 - 8
The number of data paths that this node is on.
2.12
Path A...H
Path A...H Limits 0 - 500
The path numbers that this node is on (there will be "path count" items, prompted in setup data as PATH A, PATH B etc.)
For a better understanding of data paths please refer to the document "The
Session Layer 2 (Layer 5)" (Mark Greening 1986).
2.2
Link Core Setup Data
All links on Net 2 are written around a set of "core" modules providing
many useful services to the link applications; such as, I/O handling across the
link and the net and message buffering and routing. See--"Link Core
specification for CD-Net 2 Data Links" (Srini Komandur 1987). The following
list gives the setup data items added to the link node by the core software.
2.2.1
USER LANGUAGE
Language Limits 0 - 8
0 FOR ENGLISH 1 FOR SWEDISH 2 FOR FRENCH 3 FOR FINNISH 4 FOR GERMAN 5 FOR FRENCH-CANADIAN 6 FOR DUTCH 7 FOR SPANISH 8 FOR NORWEGIAN
REMOTE LINK BAUD RATE
THE BAUD RATE OF THE LINK TO THE HOST COMPUTER
ENTER THE DESIRED BAUD RATE
75, 110, 150, 300, 600,
1200, 4800, 9600 OR 19200
If an invalid number is entered (not one of the above), the link will default
to 9600 baud.
2.2.3
Data Bits
Data Bits Limits 7 - 8
REMOTE LINK DATA BITS
THE NUMBER OF DATA BITS IN THE LINK
TO THE HOST COMPUTER.
ENTER THE DESIRED NUMBER OF DATA BITS
7 : SEVEN DATA BITS
8 : EIGHT DATA BITS
If an invalid number is entered, the link will default to 8 data bits.
2.2.4
Parity
Parity Limits 1 - 3
REMOTE LINK PARITY
THE PARITY OF THE LINK TO THE HOST COMPUTER
1 : NO PARITY
2 : EVEN PARITY
3 : ODD PARITY
ENTER THE VALUE CORRESPONDING TO THE DESIRED PARITY
If an invalid number is entered then the link will default to odd parity.
2.2.5
Stop Bits
Stop Bits Values 1, 1.5, 2
REMOTE LINK STOP BITS
THE NUMBER OF STOP BITS IN THE LINK
TO THE HOST COMPUTER.
ENTER THE DESIRED NUMBER OF STOP BITS
1, 1.5 OR 2
If an invalid number is entered, the link will default to one stop bit.
2.2.6
LINK TYPE - CONSULT LINK ID LIST
Link Type Limits 0 - 49
ENTER 00 - 09 FOR ACCURAY
ENTER 10 - 19 FOR MEASUREX
ENTER 20 - 29 FOR SENTROL
ENTER 30 - 39 FOR IMPACT
ENTER 40 - 49 FOR MISCELLANEOUS
Link types are explained in the first section of this document.
If the link type specified in setup data is not implemented or unassigned, the link will default to type 30.
Example 1: If the profiles are coming from a host link then set the link setup data to ORIGINAL..
Example 2: If the profiles are coming from our own Aplus scanner then set set the link setup data to DUPLICATE.
Example 3: If the profiles are coming from a host link then set the link setup data to ORIGINAL. If the same profiles has to go to another host via another link on the CD-NET set it to DUPLICATE in the second link board.
Example 4: If the same type of profiles are coming from our own Aplus scanner at the reel and a Measurex link at the size press, the Link board should be set to ORIGINAL for all profiles.
Example 5: If the moisture profile is coming from our own Aplus scanner at the reel and a basis weight profile is coming from Measurex link at the size press, then Link board should be set to DUPLICATE for moisture and ORIGINAL for basis weight.
1 = ORIGINAL
2 = DUPLICATE
1 = ORIGINAL
2 = DUPLICATE
1 = ORIGINAL
2 = DUPLICATE
2.2.7
Number of types
Number of types Limits 1 - 9
NUMBER OF TYPES
THE NUMBER OF NODE TYPES ON THE NET
THAT THE LINK IS COMMUNICATING WITH
********************************************************************************p> Definition of TYPEs or Link Types on the Link:
In the Link Board's perception, other nodes on the net with which it has any interest are designated as one of nine possible types: a scanner, controller and actuator node for each of caliper, weight and moisture.
********************************************************************************p>
A single Link Node may contain several TYPES in a system (ie: there may be several moisture controllers but they are all of type 1). The link board only needs to know about types with which it will be communicating so the number entered here will usually be only 1 or 2. For example, let's say we have an AccuRay link with Impact in control receiving 1 caliper and 2 moisture profiles. Accuray does not ask for status when they are not in control so the only nodes the link will be talking to will be the controllers for Moisture and Caliper. Thus the "Number of Types" will be 2. The scanner types are included for future use only--currently they should not be selected.
2.2.8
Next Type
Next Type Limits 1 - 9
SELECT NEXT TYPE
* = SELECTED
1: MOISTURE CONTROL 2: CALIPER CONTROL 3: WEIGHT CONTROL 4: MOISTURE ACTUATOR 5: CALIPER ACTUATOR 6: WEIGHT ACTUATOR 7: MOISTURE SCANNER 8: CALIPER SCANNER 9: WEIGHT SCANNER
To continue the example above, you would enter 1 to specify the Moisture Controller and then 2 to specify the Caliper Controller. The menu above will be displayed for the "Number of Types" that you selected earlier. Each time you enter a value between 1 to 9 depending on the mill system configuration.
2.2.9
Number of Groups
This refers to the number of HOST control groups.
Number of Groups Limits 1 - 9
A group is a data set which is a unique, single entity independent of other groups and which is specific to a declared node TYPE on a given PATH.
********************************************************************************p>
Thus, data GROUPS may be arrays of zone dependent information (eg: status or setpoints) or data-box dependent (eg: profiles). An element of data from a link is uniquely specified by the Type, Group, Path, Start and End--no overlap is permitted.
2.2.10
Next Group
Next Group Limits 1 - 9
Groups on the link may have a value between 1 and 9 inclusive.
This setup data item is repeated as many times as the data entered for number of groups, each time a group number is entered. This to be considered the Host's designation for control group.
Example: Say Type 30 has 2 moistures, using TYPE 30 link, (old link type 1),
[H3/xx/xx/xx]
[H4/xx/xx/xx]
Where H4 or 4 refers to Host control group, H3 or 3 refers to host control group 3.
These are repeated as many times as the number of types entered for the setup data item.
2.2.1.1
Group Path Number
Group Path Number Limits 0 - 500
This is the network data path number that group Y in type X is on. It must be one of the paths specified in the network setup data (see section 2.1.2) and has to be the same path as the target node of type X.
2.2.1.2
Group Start
Group Start Limits 1 - 512
To understand GROUP START, you must first understand how an Impact Control Group works. In general, moisture controllers, Infra Pac PUCs, and Aqua Pac(s) actuator computers use this concept.
Example: One power unit drives 2 Infra Pac frames, one at the reel and one at the size press. Both frames are on Net 2 data path 0, each frame has 10 zones .
For purposes of Impact's Moisture controller or the Host's Mositure controller will outputs into 2 control groups. But from the MAC's standpoint, % power data inputs will come from 1 array on path 0. Knowing where to place the data, ie index, the % power array determines which frame gets the power.
In the following array of 20 elements, the first 10 zones are hard wired to the size press frame. The second 10, go to the reel frame.
1,2,3, ... (frame 1), 8 ,9, 10 - 11, 12, (frame 2), 18,19,20,21
Say in the case of [H3/xxx/ and [H4/xxxx both are on the same path. Where [H3/ is size press and zone 1 through 10 are frame 1, then for this group, the start would be 1. For [H4/ reel Would start at 11.
If both groups were attached to different frames; having different power units'; having different data paths. Then both would start at 1 because there are 2 power units, each with different unique path numbers.
2.2.1.3
Group End
Group End Limits 1 - 512
Note that for groups describing profile data, the link will now handle 512 data-boxes. Requests or data from the link only has to fall within bounds to go through the core to the net--an exact match of start and end is not required.
In the above example, group 1 would end at 10, and group 2 would end at 20.
2.2.1.4
Impact Group
Impact Group Limits 1 - 8
This is the Impact's control group number. Enter the Impact control group number to which the host group is to be mapped.
Section 2.2.11 to 2.2.14 are repeated as many times as the number of groups in each system type.
Depending on the type of link selected, additional setup data items may need
to be setup. The link setup data automatically prompts you if it needs
additional data. Link type 0, 10 and 11, 20 needs additional setup data. You
may have to enter the additional data.
2.3.1
Accuray Setup Link Data
When Impact is in control with AccuRay as the host computer, the profiles sent
across the link are identified as Caliper, Weight or Moisture by a 4 bit Access
Code (see AccuRay specification). In the link agreement that we have with
AccuRay, these codes are 2 -> Caliper, 8 -> Basis Weight, 11 (0B Hex) or
12 (0C Hex) -> Moisture. Unfortunately, at some sites these values are not
adhered to; so, the following setup data items permit any access code between
1 and 15 to be assigned (note that code 0 is the link reset code).
For standard configurations, enter the standard values indicated; otherwise, use values between 1 and 15 inclusive. Each number may be used only once.
Old link between Measurex and Impact can only handle one type of system (moisture or caliper or weight) and one profiler through a single link interface computer. New link is capable of handling multiple systems and profilers through a single link interface computer. For the link computer to distinguish between the new and old type link, the following additional setup data is necessary. You will be prompted automatically to add the following link dependent setup data items.
If you entered 0 to the previous question, you will be prompted with the following messages:
Select the profiler or scanner # by entering a value between 1 to 9.
SWAPSD = 0 (Do not swap the source and destination field.
Do not swap the source and destination field in the reply message to Measurex Levant Soysal Link)
SWAPSD = 1 (Swap the source and destination field.
Swap the source and destination field in the reply message to Measurex SCL Link)
Sometimes times Measurex requires, on all return messages, the first 2 2-byte fields reversed on all replies. This performs that function.
SEND LOCAL/REMOTE = 1 (Measurex can send local remote status)
2.3.3
Measurex 200/100 Link Setup Data
This link between Measurex and Impact can only handle one type of system (moisture or caliper or weight) and one profiler through a single link interface computer. You will be prompted automatically to add the following link dependent setup data items.
FX = 0
2002ET = 1
Select the profiler or scanner # by entering a value between 1 to 9.
2.3.4
Sentrol Snooper Link Setup Data
This link between Sentrol and Impact can only handle profiles. It is a snooper link. You will be prompted automatically to add the following link dependent setup data items.
Select the scanner # by entering a value between 1 to 9.
This link between YEW BM800 and Impact can only handle profiles. This link can receive only profiles from YEW. You will be prompted automatically to add the following link dependent setup data items.
PROFILE TYPE = 0 Original
PROFILE TYPE = 1 Duplicate
WEIGHT SENSOR POSITION
Enter the weight sensor position.
MOISTURE SENSOR POSITION
Enter the moisture sensor position.
CALIPER SENSOR POSITION
Enter the caliper sensor position.
2.4
How to do setup data for a Net 2 link - a real example: Voikkaa Systems 264
& 268
It is probably already apparent if you've read through this document and
various referenced documents (unlike some cheats who skip straight through to
the example here) that setting up the new link is not a piece of cake; this is
the price we had to pay for the flexibility the system now allows. The best
way to configure a link (and the other nodes) is to sketch out the node
configuration and decide ON PAPER how you're going to set up the system before
you even get anywhere near the CD-OpCenter and try entering values--the odds
are that otherwise you will get it wrong.
A great example of what sort of complexity a full Net 2 system allows is the configuration for the Voikkaa systems. This system comprises 11 nodes on a single network -- (refer to the sketch)
2 Accuray Data Links
2 Moisture Controllers
2 Moisture Actuators (MACS)
2 CD-OpCenters
1 Caliper Controller
2 Caliper Actuators
One of the links is for data groups where AccuRay is in control, the other for Impact in control. Note that the "AccuRay in Control" link communicates with both MACS because AccuRay controls half the frames on each. Impact, of course, controls the other half. The "Impact in Control" link has to send profiles to both Moisture Controllers for the same reason. The net must be broken up into TWO data paths because there are otherwise duplicate nodes on the same net; so, the links will have to be configured to run on two paths. For this example, let's choose paths 0 and 1 and deal first with the link where Impact is in control.
2.4.1
AccuRay Link with Impact in Control
Link 1: Impact in control receiving 2 moisture profiles and 1 caliper profile
of 108 dataÄboxes each.
Thus link 1 needs to communicate with:
TYPE GROUP PATH START END Impact IMPACT-GROUP
Group RESULT
1 1 0 1 108 1 M 1 prof to MC 1
1 2 1 1 108 1 M 2 prof to MC 2
2 1 0 1 108 1 C prof to CC 1
In setup data this translates to:
Path Count = 2
Path A = 0
Path B = 1
Language = 3 (Finnish)
Baud Rate = 9600
Data Bits = 8
Parity = 2 (Even)
Stop Bits = 1
Link Type = 0 (AccuRay)
Number of Types = 2 (Moisture Controller & Caliper Controller)
Next Type = 1 (Moisture Controller)
Next Type = 2 (Caliper Controller)
Number of Groups on Type 1 = 2 (There are 2 moisture profiles)
Next Group for Type 1 = 1 (First Moisture Profile)
Next Group for Type 1 = 2 (Second Moisture Profile)
Number of Groups on Type 2 = 1 (There is 1 caliper profile)
Next Group for Type 2 = 1 (First and only Caliper Profile)
Path Number of Group 1 Type 1 = 0 (Route of Moisture 1 Profile)
Start of Group 1 Type 1 = 1 (First box must >= 1)
End of Group 1 Type 1 = 108 (Last box must be <= 108)
Impact-Group of Group 1 Type 1 = 1(Moisture 1 Profile mapped to MAC control group)
Path Number of Group 2 Type 1 = 1 (Route of Moisture 2 Profile)
Start of Group 2 Type 1 = 1
End of Group 2 Type 1 = 108
Impact-Group of Group 2 Type 1 = 1(Moisture 2 Profile mapped to MAC control group)
Start of Group 1 Type 2 = 1
End of Group 1 Type 2 = 108
Impact-Group of Group 1 Type 2 = 1
Caliper Access Code = 2
Weight Access Code = 8
Moisture 1 Access Code = 11
Moisture 2 Access Code = 12
2.4.2
AccuRay Link with AccuRay in Control
Link 2: AccuRay in control sending two 50 zone setpoint arrays to each MAC with various status requests.
Thus link 2 needs to communicate with:
TYPE GROUP PATH START END IMPACT RESULT
GROUP
4 1 0 1 50 1 M 1 setpts to
MAC 1
4 2 1 1 50 1 M 2 setpts to
MAC 2
In setup data this translates to:
Path Count = 2
Path A = 0
Path B = 1
Language = 3 (Finnish)
Baud Rate = 9600
Data Bits = 8
Parity = 2 (Even)
Stop Bits = 1
Link Type = 0 (AccuRay)
Number of Types = 1
Next Type = 4 (Moisture Actuator)
Number of Groups on Type 4 = 2 (There are 2 Zone Sets)
Next Group for Type 4 = 1 (First Moisture Zone Set)
Next Group for Type 4 = 2 (Second Moisture Zone Set)
Path Number of Group 1 Type 4 = 0 (Route of Zone Set 1)
Start of Group 1 Type 4 = 1 (First zone in the set)
End of Group 1 Type 4 = 50 (Last zone in the set)
Impact-Group of Group 1 Type 4 = 1 (MAC control group for zone set 1)
Path Number of Group 2 Type 4 = 1 (Route of Zone Set 2)
Start of Group 2 Type 4 = 1
End of Group 2 Type 4 = 50
Impact-Group of Group 2 Type 4 = 1 (MAC control group for zone set 2)
Caliper Access Code = 2
Weight Access Code = 8
Moisture 1 Access Code = 11
Moisture 2 Access Code = 12
Note from above that a good way of describing the link configuration is by filling in the tables given at the start of sections 2.4.1 & 2.4.2. One final point: make sure that when the system is running correctly, the setup data is written down and kept where it would be easily available to whoever may have to install a replacement board!
Legend
MCn - Moisture Controller n
MACn - Moisture Actuator n
CCn - Caliper Controller n
CACn - Caliper Actuator n
OpC - CD-OpCenter
IC - Impact in Control
AC - AccuRay in Control
P - Profile Data
S - Setpoints and Status