Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - support

Pages: 1 2 3 [4]
46
Frequently Asked Questions / How to expand Analog I/Os?
« on: March 20, 2003, 04:57:23 AM »
The M-series PLC has fixed 8 analog inputs or 6 analog inputs and 2 analog outputs and is not expandable.

However, since all M-series PLCs have built-in RS485 port, you can easily use it to connect to RS485 based analog I/O boards. ?For example, you could use another low cost T100MD888+ to add another 8 analog I/O (plus many other functions, of course), or you could use a 3rd party analog I/O board to give you different selection of resolutions and voltage/current interface.

We have thoroughly tested two units of the I-7000 modules made by ICP-DAS. One of them is a 16-bit, 8 channel analog input module, ?and the other is a 2 channel, 12-bit analog output module that support 0-10V, 0-20mA or 4-20mA. Both modules proved to work readily with the M-series PLC via the RS485 port. We have written an application note and some sample .PC5 programs for working with these modules. They can be downloaded from the following link:
 
[/b]


Multiple units of I-7000 can be multi-dropped from a T100MD+ or MX+ PLC, allowing hundreds of analog I/Os to be connected to a single PLC. Since the PLC can also be a MODBUS slave this can also serve as an ultra low cost RTU subsystem.

ICP-DAS also have other modules that may be of interest to M-series PLC users. These include one that connect up to 8 channel of thermocouple input directly (model I-7018). That means no need for expensive signal conditioners! Just plug the J,K or other types of thermocouple to the module's inputs, connect up to the PLC's RS485 port and instantly the PLC will be monitoring up to 8 temperature zones. ?There is also a 4 channel analog output module for those who needs lot of D/A outputs.
 
To find out more about the I-7000 modules and their prices, please visit:



47
Frequently Asked Questions / Using PLC as MODBUS or RTU master.
« on: July 14, 2003, 03:47:26 PM »
The M-series PLCs have built-in READMODBUS, WRITEMODBUS, READMB2, WRITEMB2 ?commands which allow the PLC to act as a MODBUS master and interface to third party MODBUS or RTU slaves. These commands use the MODBUS function 03 for reading and funciton 16 for writing to the slaves. Function 03 and 16 are considered MODBUS level 1 functions and are the most fundamental MODBUS functions that all MODBUS slave devices must implement.

However, if your device requires other function (such as 04 to read Modicon input register 3xxxxx, etc), then you will not be able to use the abovementioned built-in commands.

Fortunately, the amazing flexibility of the M-series programming language allows you to implement your own Modbus RTU master by using INCOMM, OUTCOMM and CRC16 commands (for PLC with firmware revision r44 and above only). ?You can also implement your own MODBUS ASCII master by using the PRINT n and INPUT$(n) commands.

We have posted a sample program that you can download from the following link:
 
http://www.tri-plc.com/trilogi/modbusFunction04.zip
 
This sample implements the RTU function 04 and is tested to work with a slave T100MD888+.

48
Frequently Asked Questions / TLServer Ver. 2.0 could not start
« on: June 04, 2003, 08:20:18 PM »
The " SetupTL5.exe" in TRiLOGI version 5.1/ TLServer 2.0 automatically searches the default Java JRE directory and install the relevant communication library files there ("jspwin.dll"). Hence it is important to install the JRE first BEFORE running the SetupTL5.exe so that the setup program can find the JRE.  
 
If TLServer could not start at all, then try to search your harddrive for the file "jspwin.dll". It should be stored in the following JRE folder by the installer:
 
   C:\Program Files\JavaSoft\JRE\1.3.1\lib\ext\x86
 
However, if you have multiple copies of JRE or JDK it may confuse the installation program when it tries to install the "jspwin.dll" file into the correct folder. You can manually copy the "jspwin.dll" to all the JRE or JDK folders using the above path.
 
A customer told us that by copying the "jspwin.dll" to the following folder it works better for his Windows XP:  
 
 C:\Program Files\JavaSoft\JRE\1.3.1\bin
 
If all else fail you may like to try to copy the "jspwin.dll" to the above destination and try.

49
Technical support / Visual Basic Communication Program
« on: September 30, 2002, 06:13:39 AM »
Dear All,

We have just posted a new webpage with sample codes for using Visual Basic 6.0 to communicate with TRi's PLCs. For more details please click on the following link:

http://www.tri-plc.com/applications/VBsample.htm


Pages: 1 2 3 [4]