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.

Messages - support

Pages: 1 2 3 [4] 5 6 ... 208
Technical support / Re:Watch dog timer.
« on: November 26, 2018, 10:02:01 PM »
Sorry for the late reply due to all the holiday season lethargy...

The firrmware performs WDT reset when the program is inside a FOR.. NEXT loop. Some FOR NEXT loop may take longer than the WDT time-out period to execute and we didn't want the processor to be reset by the WDT when  the program is performing a legitimate FOR..NEXT loop that takes a long time to complete.

We believe more applications could be caught by an unexpected WDT reset if we don't automatically perform a WDT reset inside a FOR NEXT loop.  It is more likely for spaghetti GOTO statements inside a function to go ashray than a structured FOR... NEXT loop or WHILE..ENDWHILE loop, and hence we don't automatically perform WDT reset for the structured loop. We are not purist in this sense but just trying to minimize the potential problem that user may encounter if we let WDT expires inside a structured loop and depend on the programmer to reset the WDT in a timely manner.

You can use the INTRDEF 100, n, 1 to set an undefined interrupt trap. n is the custom function number. This command is described in the help file for INTRDEF.

Yes you can use both WDT and the undefined interrupt trap at the same time. That allows you to catch the undefined interrupt and you can decide if it is safe to let the execution resume or force a processor reboot.

General Discussions / Re:settimer sv
« on: November 24, 2018, 06:28:12 PM »
Yes both of these are TBASIC codes to set the timer and counters preset values.

Note that for Fx class PLCs the changes are immediately non-voilatile since they  are stored to the FRAM memory.

For FMD and Nano-10 you will need to run the SETSYSTEM command to store these new values to the flash memory. So it is not recommended to make changes to these set values very frequently as it will affect the SCAN time due to the need to erase a bank of flash memory and then backup the whole bank to the flash memory.

One other way to start a timer or counter in TBASIC is to assign their PV to a value.

TIMERPV[ tim1 ] = DM[100]
CLRIO  tim1   ' Timer #1 label name is tim1.

Technical support / Re:Saving a CSV File
« on: November 13, 2018, 08:21:23 PM »
Yes but you need to run a server software on your PC that can receive data from a connected TCP/IP device.

The simplest server for such an application would be the TLServer that you already have. You need to run the TLServer and the PLC would connect to the TLServer IP address and use the <REMOTEFS> tag.

You can refer to the sample program in "TestEthernet.PC6" that you can find in the following folder:


The example can be found in Circuit #10 and a screen short is shown below.

If your PC has a PHP engine running you could also write a PHP script and wait for HTTP GET command sent by the PLC. The PHP script can then save the data to data file or even directly update to MySQL database. You can design your own message exchange format between you PHP script and the PLC. This is more advanced stuff but can be as powerful as you want them to be.

Technical support / Re:cannot login to plc
« on: July 19, 2018, 10:49:15 PM »
When you turn on DIP switch #3 the PLC will be assuming the IP address of  - is that what you use to try to connect to the PLC?

You can reset the PLC's Ethernet setting by using TLServer and connect to the PLC via its serial port. Then at the :Ethernet & ADC Configuration" screen you click on the "Factory Default" button to fill up all the default parameters and you can then write these parameters to the PLC. After a power on reset you should be able to connect using the default IP address and port number.

Technical support / Re:cannot login to plc
« on: July 18, 2018, 09:32:02 PM »
Did you enable the username/password settings in the "Ethernet & ADC Configuration"? If so it will require you to key in the username and password that you have defined in order to login via the Ethernet.

If you are able to connect via the TLServer and serial port, then you can connect to the PLC and retrieve the Ethernet settings and disable the username/password or add in a correct username/password to protect the connection.

Technical support / Re:Suspending a program
« on: June 28, 2018, 09:54:16 AM »
You can add a PAUSE statement at the place you want the PLC to simply stop running until it is re-started.

Technical support / Re:16 or 32 bit DM confusion
« on: June 22, 2018, 03:20:32 PM »
In TBASIC all operators are operating on 32-bit  number.

Any integer numbers are always converted into 32-bit integer before applying the math or comparison operation.

So even if a number is contained in DM[n] the number is first converted ito a 32-bit number and thus any comparison has to be made against a 32-bit number. If DM[n] contains a negative number it will be sign-extended during conversion.

Technical support / Re:Webserver and excel link on startup
« on: June 06, 2018, 09:06:11 PM »
What is the MS Excel version?

Excellink communicates using a Java DDE client libary that makes connection with the MS Excel. The problem is that it is hard to pin point where the communication is lost. Is it from ExcelLink, the DDE client library, DDE server on the MS-Excel or Excel itself.

When you lose communication, would restarting the ExcelLink solve the problem? If not, do you have to also restart the MS Excel to resolve the problem?

If you reduce the number of active programs running on your computer to just ExcelLink, MS Excel and (optionally) the TLServer, do you still lose communication often?  How long do you run the program before it starts to lose communication?

Technical support / Re:Webserver and excel link on startup
« on: May 16, 2018, 08:04:23 PM »
Current generation of ExcelLink and TLServer are not able to run in the background without an open window. There really isn't a demand for such a feature so far. If the program runs in the background without you knowing there are people would wouldn't like it either.

Technical support / Re:Stepper Motor Demo Code
« on: May 03, 2018, 01:22:19 PM »
Dear Gary,

Our team at TRi greatly appreciate all your contributions to this forum!

The well-documented examples that you provided for the other forumers are invaluable tools to help both the new comers as well as experienced hands make the best use of our PLC's capabilities.

Thank you very much!

The Tech Support team,
Triangle Research International, Inc.

Technical support / Re:Two PLC'S on one router
« on: April 23, 2018, 11:35:20 AM »
Unfortunately the PLC node name defined in i-TRiLOGI is not recognized by the DHCP server and thus it is not displayed. So only the MACID should be used to identify the PLC.

In PLC application it is often better to use a static IP address. The DHCP IP address can change when the router loses power for some time. So if you want to use DHCP you should do an IP address reservation in the router so that the router will always assign the reserved IP address to the PLC. The reservation table inside the router often allows you to define a name for the device that you reserve the IP address. This is where you can put in a meaningful name.

The following picture is captured from a Cisco router that shows you where you can define the name of the device.

Technical support / Re:Two PLC'S on one router
« on: April 07, 2018, 03:44:49 AM »
What is the make and model number of the router?

For some reasons it seems that either the DHCP server is sending out the same IP address to two PLCs that are requesting IP address at the same time, or that both PLCs are picking the first assigned IP address from the DHCP server.

Is this repeatable?

We will try this on a different router to see if we get a different results.

Why is your router DHCP assignment jump from 130 to 161 when two devices are requesting DHCP simulataneously? Is it because there are other devices already been assigned 131 to 160?

Technical support / Re:PID negative saturation
« on: March 30, 2018, 05:36:43 PM »
The controller output represent the amount of control adjustment to be added to the existing open loop output value based on the error it receives from the difference between the measured value (feedback) and the setpoint value.

E.g. if  in order to achieve a 120 lux, a lighting controller should normally output 40% (open loop value). Now when sun light shine into the area adds more light to the place and this creates a higher feedback lux reading. An error is generated because the feedback is now larger than the set point (120 lux). The error is fed into the PID loop which creates a negative output. This will result in the controller reducing its output accordingly until either the total light output is brought back to the setpoint (120 lux) or if daylight is too strong then the output may eventually be reduced to 0.  

Technical support / Re:Webserver and excel link on startup
« on: February 28, 2018, 08:57:49 AM »
You can create a short cut for the "C:\TRiLOGI\TL6\TLSvr32Launcher.exe"  (right click and select Send To -> Desktop).

Next drag the shortcut into Windows Startup folder and then when you restart windows the TLServer will be loaded automatically.

You may try to do the same for "ExcelLink21Launcher.exe". But usually we recommend opening up Excel software first before running ExcelLink to ensure the DDE linke can be properly established. In any case you will still need to manually click to run the ExcelLink software so there isn't a lot of advantage to launch it automatically.

Technical support / Re:Auto Negotiate IP
« on: February 26, 2018, 11:14:58 AM »
Note that the IP address setting is only available to SmartTILE-Fx based PLCs (Fx1616-BA, Fx2424 and EZWire1616).

SmartTILE-Fx CPU board will only query for the IP address when it is first powered up. If the router is switched OFF then the PLC will not be able obtain a DHCP assigned IP address and therefore will become offline. It does not periodically request for IP address from the router so there should be no effect on the scan time after the PLC has been powered up.

Since in many applications the PLC is not connected to the router when in operation this design concept is to prevent the PLC wasting precious CPU cycle to query for IP address from router that it is not connected to.

For applications that are connected to a router we do recommend selecting a fixed IP address that it outside of DHCP range to ensure that the PLC is reachable regardless of when the router is powered up. Otherwise you will need an LCD display to inform user of the IP address that it obtains from the DHCP server before you can connect to it.

Pages: 1 2 3 [4] 5 6 ... 208