Created a new lookup table for an analogue output (AO) object to provide 10% steps and not 1% steps. Displaying the object value always shows 1% steps.
Sigma Controller (All Versions)
The analogue output object value is the input value for the lookup table and the output of which is then passed to the A to D converter and then to the physical output.
The value can be seen by a multimeter connected to the physical output.
If the value of the output needs to be displayed via the Sigma front end then a programmable object is required to process the lookup table and then cross referenced to a standard analogue output object (with the default lookup table).
Example of programmable object:
10 Xflo = POINT 0|51
20 YFLO = LOOKUP (1812, XFLO)
30 RETURN VIA TEXT 92 VALUE YFLO
Where POINT 0|51 is the control/input object and 1812 is the lookup table number.
ModBMS will not allow an OPC Client to write OPC DA values to Sigma. But, reading the ModBMS/Sigma values does work.
Sigma 4.04 and below
ModBMS uses the DDE functions to read/write data to the Sigma server. A Sigma release 4.04 and below the write function was not supported and was fixed in Sigma release 4.05 onwards.
Upgrade to Sigma 4.05 (onwards) where the DDE write function has been fixed.
1. The Sigma default user name TAC USER does not work with Sigma 4.05 SEB
2. Tried the user access password and could not logon
Sigma 4.05 SEB
The default user name changed at Sigma 4.05 SEB
From Sigma 4.05 SEB onwards the default user name is SIGMA USER.
The password remains unchanged.
The text on the prog object does change but the graphic does not show the same change.
Sigma all versions
BAS all versions
Controller only update server graphics when the object changes state or exceeds the set tolerance. If prog objects are written with the same condition but different texts in the return statements then the correct text may not be displayed until the whole graphic is updated. For example
10 If P0|1 on then return true "Object 1 on"
20 if P0|2 on then return true "Object 2 on"
30 if p0|3 on then return true "Object 3 On"
Write the programmable object to that will change state to update the graphic. This may well have to be a dedicated object for the graphic. For example using a time statement to check for a change;
10 if not time left then goto 50
20 If P0|1 on then return true "Object 1 on"
30 if P0|2 on then return true "Object 2 on"
40 if p0|3 on then return true "Object 3 on"
50 set timer 10
60 If P0|1 on then return false "Object 1 on"
70 if P0|2 on then return false "Object 2 on"
80 if p0|3 on then return false "Object 3 on"
Which files can be backed up safely with an automatic/manual method.
Backing up a live Sigma system is not a recommend as copying ‘live open’ files can not guarantee the integrity of the data.
For either backup method (automatic or manual) those files which could be potentially 'open' by Windows should not be backed up unless the Sigma server and clients have been shut down.
1. Those data locations that can be backup safely while the Sigma is running are those in which archive data is stored, namely;
Removing the files from these locations should only be done as a space saving measure as Sigma can be configured to view these data files by the user.
2. For all other files the recommendation is to shut the system down (clients and server) before taking the backup.
3. Restoring data must only be performed after shutting down the system first.
What entries are needed in the INPUT_XLATE table for the Sigma digital input to work?
IC GEN DDE
IC GEN OPC
The Sigma digital inputs operate a reverse logic of 100.0 = off and 0.0 = on. This needs to be reflected in the IC GEN Gateway.txt file XLATE table
1. For the IC GEN gateway.txt input XLATE table when mapping to digital input objects;
Item0=1 / 0.0 ;DDE input of 1 = DI on
Item1=0/ 100.0 ;DDE input of 0 = DI off
2. For the IC GEN gateway.txt output XLATE table when mapping from digital output objects;
Item0=0.0/ 0 ;D0 off = DDE output of 0
Item1=100.0/ 1 ;D0 on = DDE output of 1
The IC3 Modbus IP interface is a client. How can this be linked to another Modbus IP client such as the Carrier i-VU gateway?
IC3 Modbus IP Client server
The IC3 Modbus only supports the IP client and cannot be directly connected to another IP client. Other systems such as Carrier are similarly only IP client.
Using the BCX1 as a Modbus IP server to hold a mapping table will allow both clients to read/write data to it.