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
32
Definitely the wrong place for questions not relating to our PLC. Topic has been moved to General discussion.

http://www.tri-plc.com/yabbse/index.php?board=5;action=display;threadid=878

33
Frequently Asked Questions / Connecting to Barcode or Smart Card Readers
« on: December 13, 2005, 04:05:38 PM »
It is very simple to read from a barcode or smart card/RFID reader if the barcode reader can be connected to the PLC using RS232. Most bar code readers return data as ASCII string terminated by a Carriage Return (CR character, ASCII 13) so you can simply use the INPUT$(1) command to read the data from the COM1 port. The PLC keeps a 256 bytes circular buffer for incoming serial characters so you don't have to be monitoring the serial port all the time. As long as the data are read before the buffer overflows (i.e. more than 256 bytes are received) the buffered data will not be lost.

First, decide how often you need to check whether the bar code has read something. e.g. every 0.5s, then form a circuit:

   Clk:0.5s     Fn_#1
|---||--------{dCusF}



Within function #1:

  A$ = INPUT$(1)   ' read from COMM port 1

  IF LEN(A$)=0 RETURN: ENDIF  ' nothing from barcode
                              ' so just return
  ....          '  continue what you need to do

In the above code, if A$ receive an empty string from the COMM1 port it means there is no data available, so the function just quit. Otherwise, continue to process the data received in the string. You can convert strings to integer such as:

  X = VAL(A$)  or for hexadecimal string,
  Y = HEXVAL(A$)

function such as MID$() can be used to extract a certain
segment of a string from the string variable.

34
Technical support / MOVED: TLServer21.jar may not like J2SE 1.5.0
« on: November 14, 2005, 06:21:26 AM »
Moved to Frequently Asked Question page due to increasing interest in the same topic.

http://www.tri-plc.com/yabbse/index.php?board=2;action=display;threadid=760

35
Archived Tech Support / Using MX-RTC / MX-RTC Battery Life
« on: October 27, 2005, 05:35:21 AM »
MX-RTC is an optional battery backed real time clock module that you add between the 28pin SRAM and the 28pin socket on any T100MD+ or T100MX+ PLC. It keeps the real time clock running even when all power to the PLC has been shut down.

If you turn on DIP Switch #1 to the PLC, then MX-RTC will preserve the values of all the internal variables when power is removed. These includes A to Z, A$ o Z$, DM[1] to DM[4000], as well as timers  and counters present value.

There are also data and logic states that are NOT PRESERVED,such as the values of INPUT[], OUTPUT[], PWM output, DAC outputs and Stepper motor ouputs.  The PLC will reset all the outputs regardless of the presencee of MX-RTC. This is to prevent a situation where after a power failure, some outputs that should NOT be turned ON unless with some user intervention to ensure that it is safe to do so, became active due to its ON state before power failure.

As such a scenario may be hazardous, it was decided that the output logic states will not be preserved after a power on reset. However, all internal relay logic status are preserved. So if your program requires that an output must return to its pre-power down states, then you can turn on an internal relay first and the contact of the internal relay is then used to drive the output. This give a degree of control to the user to determine which output is allowed to be turned ON based on its pre-power down logic state. Similarly, all PWM output and DAC outputs will not be set to their pre-power down values, so the programmer must take this fact into consideration.

36
Technical support / Server Down on Oct 24 & 25th 2005
« on: October 26, 2005, 07:10:07 AM »
                                    Notice of Web Server Failure


37
Technical support / MOVED: RS232 to USB port adaptor
« on: January 14, 2005, 10:04:09 PM »
Since this topic affects many new users whose PC do not have built-in RS232 port, this topic has now been moved to the FAQ board.

http://www.tri-plc.com/yabbse/index.php?board=2;action=display;threadid=409

38
Frequently Asked Questions / WinTRiLOGI disappear after selecting PLC Type
« on: December 01, 2004, 06:39:27 AM »
This is most likely due to the serial driver not being able to load properly and the WinTRiLOGI closes itself down when the exception occurred. There are a few possibile reasons:

1) There are more than one version of Java runtime Environment in the PC (JRE). Some newest Windows PC now comes pre-installed with a JRE (1.4.x), and if you install the JRE 1.3.1 over it, a conflict may occur causing the serial driver file not being able to load properly. To check if you have a pre-installed JRE, go to the "Command Prompt" and enter the following command:  

   C:\> java -version

If it shows that the PC already has a version 1.4.x, then do not install the JRE 1.3.1 over it. However, if you have already installed the JRE 1.3.1 then a conflict would have occurred.

To resolve this conflict, you need to first uninstall both the JRE 1.3.1 and the JRE 1.4.x that have been  installed on the PC by going to the "Control Panel" to remove both the JRE. Next, go to the following link to download the latest version of Java JRE 1.4.2:


   http://java.sun.com/j2se/1.4.2/download.html

Please download only the "J2SE Java Runtime environment", not the SDK (unless you plan to write Java program using the SDK). Now install the JRE 1.4.2 and make it the only JRE on your system.

You can now run the "SetupWTL3.exe" program to install the WinTRiLOGI program again. The setup program will now be able to properly install the serial driver into the correct JRE sub-folder and you should be able to run the WinTRiLOGI program properly.
 


40
Technical support / MOVED: FX2N-1HC
« on: September 26, 2004, 01:12:40 AM »

41
Frequently Asked Questions / How to scale an analog input data
« on: February 16, 2004, 03:03:23 AM »
The built-in analog ports on all the M-series PLC return data in the range of 0 to 4092 which corresponds to the full range of voltage input presented at the analog pin. However, very often a user needs a formula to translate this numeric data into units meaningful to the process (e.g. degree C or F, psi etc).  To do so, you need to know at least two reference points of how the native unit map to the PLC's ADC reading.

Reference Point              ADC Reading      
===========             ==========
      x1                                  a1
      x2                                  a2

Hence, for any reading A = ADC(1), the corresponding X is derived from:
   
  X - x1          A - a1
---------  =  -----------
 x2 - x1          a2 - a1

==>  X = (x2 - x1)*(A - a1)/(a2 - a1) + x1

Note that since x1,x2,a1, and a2 are all constants the actual formula is much simpler then it appears above.

E.g. Temperature measurement
========================

    Temp            ADC(n)
        30               200
      100              3000

So for any ADC readings A, the temperature is:

   X = 70*(A - 200)/2800 + 30

Note: To get better resolution , you can represent 30 degree as 300 and 100 degree as 1000 so if X = 123 it means 12.3 degree.
 
[Edit 2014/7]: If you are using Fx PLC or the SmartTILE-Fx then you can use floating point operation directly without having to use integer to emulate the decimal point. So the formula could be:

X# = 70.0*(A-200.0)/2800.0 + 30.0


42
Frequently Asked Questions / Interfacing to two-wire 4-20mA sensors
« on: February 14, 2004, 06:46:59 PM »
Many 4-20mA analog sensors only has two wires connection and are designed to be powered by the 4-20mA output current that flow through it. These type of sensors can be interfaced easily to the 0-5V analog inputs of the PLC as shown in the following diagram:



The sensor output will be converted to a 1-5V analog voltage and can be read by the PLC using the ADC(n) statement which will return readings of between 820 and 4092.

If the ADC is of 0-1V type (such as ADC1 & 2 on T100MD1616+) then just change the resistor to 50 ohm.



43
News / Visual Basic Communication Sample Program
« on: September 30, 2002, 06:15:56 AM »
We have just posted a new webpage with sample codes for using Visual Basic 6.0 for communication with TRi's PLC. For more details please click on the following link:
 
http://www.tri-plc.com/applications/VBsample.htm
 

44
Technical support / TLServer Could not run in Windows 95
« on: April 09, 2002, 03:02:39 PM »
If you get a "java.lang.nullpointerexception" error message while trying to run the TLServer under Windows 95, then you will need to upgrade the Microsoft's java VM in the Windows 95. You can get a patch from Microsoft website:

http://www.microsoft.com/java/vm/dl_vm40.htm

You can also install Internet Explorer version 5.0 or later which should fix the VM problem automatically too.

45
Technical support / TLServer Version 1.0 shows no COM Port
« on: March 13, 2002, 11:22:59 PM »
SetupTL5.exe installation program assumes that the Java JRE has been installed in the default directory: C:\Program Files\JavaSoft\JRE\1.3.1\..... ?and will install some Javax.comm related files in the JRE directory in order to utilize the PC's serial port. If you have installed the Java JRE into a different directory, ?then you will have to following the instructions in the README.TXT file found in the folder:

 ? ?C:\TRiLOGI\TL5\java lib

and manually copy the following three files into your Java JRE directory.

 ? ?comm.jar - ?<JRE directory> \lib\ext
 ? ?javax.comm.properties - <JRE directory>\lib
 ? ?win32com.dll - <JRE directory> \bin

Once you have copied these 3 files to the correct location, restart your computer and TLServer and you should be able to see the COM port 1 to 4 in the TLServer.

Note: If you have installed the educational version of TRiLOGI you might already have installed a different version of JRE (the latest at Sun website is version 1.3.1_3 and version 1.4) from that supplied on the CD-ROM. In that case, you may also have to manually copy these files to the correct JRE directory, or remove the JRE installation first and then re-install the version supplied on the CD-ROM.

Pages: 1 2 [3] 4