Globals

System variables

INOS system variables are defined in either a system.dt2 or a ch.indel.data.system.xml file. They mainly contain KEY/VALUE pairs, which define various configuration possibilities.

Example of a simplest system.dt2

// ! table-name
SYSTEM
// ! column-name
KeyName                     ; KeyValue  ;
// ! column-structure           
text_32                     ; text_32   ;
// ! table-data-records         
"DIGITAL.NumberOfInputs"    ; "4096"    ;
"INOS.SimulateProcessImage" ; "no"      ;
"INOS.SchedulerLogEntries"  ; "65536"   ;

Example of a simplest ch.indel.data.system.xml

<object id="ch.indel.data.system">
    <object id="digital">
        <property id="numberofinputs" type="string">4096</property>
    </object>
    <object id="inos">
        <property id="simulateprocessimage" type="string">no</property>
        <property id="schedulerlogentries" type="string">65536</property>
    </object>
</object>

Networking

Multiple IP addresses

If one needs multiple IPv4 addresses per network interface, one has to enable the iDev feature Network.Allow multiple IPv4 addresses and define the additional IP addresses in the following way as system variables:

ETHX.IpAddressY;xxx.xxx.xxx.xxx
ETHX.NetMaskY;xxx.xxx.xxx.xxx
ETHX.GatewayY;xxx.xxx.xxx.xxx

where X is the target ethernet device number, usually '0' and Y the number of the virtual interface address, allowed are 1..3. Example how to define an additional IP address 10.10.10.64 :

system.dt2

ETH0.IpAddress1;10.10.10.64
ETH0.NetMask1;255.255.255.0
ETH0.Gateway1;10.10.10.1

ch.indel.data.system.xml

<object id="ch.indel.data.system">
    <object id="eth0">
        <property id="ipaddress1" type="string">10.10.10.64</property>
        <property id="netmask1" type="string">255.255.255.0</property>
        <property id="gateway1" type="string">10.10.10.1</property>
    </object>
</object>

To avoid any routing problems, one has to ensure unique combinations of IP address and netmask :

(IP0 & Netmask0) != (IP1 & Netmask1) != (IP2 & Netmask2) != (IP3 & Netmask3)

The maximum allowed number of additional IP addresses is 4.

Hint: Currently transing is only possible over the default IP address, where debugging, INCO communication, burning a target is possible over all configured IP addresses.

If one doesn't want to define the IP addresses in the system variables but persistent in the target, one can edit them directly with the Indel INCO explorer under e.g.

Target.Devices.ETH0.Prop.IPv4Addresses.1
Target.Devices.ETH0.Prop.IPv4Addresses.1.NetMask
Target.Devices.ETH0.Prop.IPv4Addresses.1.Gateway

These values are stored persistent in the ch.indel.data.target container. This container lies in either flash or nvram depending on the target.

Allow IPv4 support over GinLink

To avoid any address conflicts, IPv4 traffic is by default disabled over ETHG0 devices (ethernet over GinLink). If one has unique IPv4 addresses on its GinLink slaves, one can enable IPv4 traffic with the following entry

system.dt2

ethg0.ipv6only;no

ch.indel.data.system.xml

<object id="ch.indel.data.system">
    <object id="ethg0">
        <property id="ipv6only" type="string">no</property>
    </object>
</object>