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 ... 3 4 [5] 6 7 ... 208
Opinions & Feedback / Re:Fantasic Tech Support
« on: February 26, 2018, 11:04:52 AM »
Thank you very much for your feedback.

Regarding documentation we will try to improve on the examples provided for each command. For us it is important to strike a balance between giving good examples without "thickening" the documentation (which can scare off new users) unecessarily. The power of the Ladder+BASIC programming language is in its simplicity one you understand how the Ladder and BASIC part work together. But at the same time because it can do so much that it will take time to master all its capabilities.  Most users may need only a fraction of what it can do and we would like to facilitate the users to be able to quickly learn what they need.

Now that all the help files for the latest i-TRiLOGI versions have now been moved online, so it will be easier for us to expand on the examples provided for the more sophisticated functions:

There is a thread in this forum that could be helpful for new users to follow:;action=display;threadid=1817

Technical support / Re:SAVE_EEP
« on: February 21, 2018, 11:25:54 AM »
Which location of EEPROM do you want to save these data to?

E.g. if you want to save DM[700] - DM[704] to EEP location 100 to 105.

FOR I = 0 to 4
   SAVE_EEP DM[700+I],   100+I


To load values from EEP location 100-104 back to DM[700] to DM[704]:

FOR I = 1 to 4
   DM[700+I] = LOAD_EEP(100 + I)

Technical support / Re:SmartTile I2C Addressing
« on: February 19, 2018, 08:41:00 PM »
You can study the example on how to use the I2C commands from the I2C-FRTC manual:

The example accesses the M24M01 I2C EEPROM available on the I2C-FRTC itself which is not available on the SmartTILE but you can study the example by also refering to the datasheet of the M24M01.

I have attached another example program which is to read the RTC chip DS1338 available on the SmartTILE-Fx itself so you can experiment with it directly.

By studying these two examples you should be able to adapt them to access your own I2C device.

Note: The I2C signals go directly to the CPU so be very careful when you are interfacing with external I2C device as any wrong connection or bad voltage can damage the CPU pin directly.

On the I2C-FRTC used with the FMD PLCs there are additional I2C buffering IC to protect against damage to the CPU due to installation error. This is not available on the SmartTILE-Fx since the signal pins go directly to the CPU.

Technical support / Re:SETSYSTEM 16
« on: January 16, 2018, 07:47:55 PM »
SETSYSTEM 16,4 will not affect the internal OUTPUT bit. It just will not update the physical output affected by the command but the computed value will stay.

Technical support / Re:PRINT #4 Shutting down
« on: January 16, 2018, 07:45:10 PM »
It appears that your code exited the WHILE loop after receiving the first line and then you execute the PRINT #4 "</>" command, which then close the connection.

So you may need to change the program a bit. Yet you do not want the CPU to be stuck in the WHILE loop inside one custom function all the time. So you should implement a state machine so that the ladder program get to continue to execute and this custom function is then re-enter on the next ladder logic scan.

Technical support / Re:Excelink
« on: January 16, 2018, 07:40:30 PM »
Unfortunately ExcelLink is not programmable to do what you mentioned.

You may be able to program an Excel Macro based spreadsheet to retrieve the data and the macro program can then decide which other data to pull based on the result of the first set of data it retrieved. However, you do need to write the code in Excel to execute the hostlink commands interaction with the PLC via TCP/IP (Ethernet or TLServer with USB-RS232 adapter)

The following web page is a bit old but does describe one Excel spreadsheet that we wrote before using Macro to send host-link command on the PLC and process hostlink response from the PLC:

Technical support / Re:SD card on a SmartTILE-Fx
« on: December 19, 2017, 07:55:49 PM »
Thank you for your interest in the SmartTILE-Fx. At this point there isn't any on-going development to add the SD card support as there are a few other options for data storage and transfer.

SmartTILE-Fx based PLCs are often connected to the Ethernet network and data can be written directly to a network server as they become available, so that these data can be accessed by other applications without having to physically remove the SD card to access the data.

SmartTILE-Fx also has data file space that allows you to store quite a lot of data locally on flash memory. The data file created by the CPU can be downloaded from the SmartTILE using a web browser.  Alternatively, you can also program the PLC to upload the data via FTP to a FTP server and that can automate the data collection without human intervention.

Technical support / Re:One Wire Sensors
« on: December 15, 2017, 06:31:33 PM »
Thank you for your suggestions.

If you are using the FMD PLCs, or developing a SmartTILE-Fx based custom PLC you could use the I2C interface (require the I2C-FRTC module for FMD) to interface with other electronic components that support the I2C interface. I2C interface is a much more popular, faster and more robust communication interface than 1-wire.

Technical support / Re:FX PLC interrupt and simulation
« on: December 15, 2017, 06:25:24 PM »
I think you were referring to the old T100MD (not FMD) that an input can be both an interrupt input as well as a regular input.

Unfortunately, there is some the peculiarity of the Fx and FMD MCU hardware such that the input can only be read if the pin is defined as a general purpose I/O (GPIO). When a pin has been defined as an interrupt input pin, the firmware has no way of reading the logic state of the pin unless the CPU switches it back to become a GPIO pin.  As such the PLC firmware is unable to report the logic state of the pin once it has been defined as an interrupt input.

The only way to get around this is to tie the interrupt input in parallel to a general purpose input so that you can still read the logic state of the input by reading it from the parallel input.

Technical support / Re:Forcing an IP address
« on: November 27, 2017, 08:54:08 PM »
Network routers have a different design purpose in that it is their job to look out for new connection and to assign IP address.

The PLC fimware initializes the Ethernet parameters during startup and most often the PLC is assigned a fixed IP address during the initialization so that will be the parameter it uses. If the fixed IP address has changed then it require a reboot in order to re-initialize the Ethernet port.

The PLC firmware does not want to spend precious CPU time to periodically check to see if it has if the IP address has changed in order to re-initialize the Ethernet port.

In many applications the PLC may not even be connecting the Ethernet port to the network, hence it is by design that the PLC only check for DHCP IP address (if IP address is set to for Fx based PLC only) during boot up and if it doesn't find an address it assume that there is no network connection or no DHCP server and thus would ignore the Ethernet port.

Technical support / Re:Update to i-TRiLOGI
« on: November 08, 2017, 11:58:34 PM »
We have moved the help files to the web but the upgrade.htm document is not moved to the web so that's why it reported a 404 error.

You can find your upgrade.htm document from the local folder:


We have fixed this issue with the next release of i-TRiLOGI so in future when you select "Upgrade TRiLOGI" it will fetch the upgrade.htm from the local folder instead from the website.

Technical support / Re:Device ID
« on: November 01, 2017, 10:22:20 AM »

Thank you very much for expressing your opinions as well as kind words about TRi Tech support!

We hear your grievances about the documentation and we will think hard about how to improve them.

I guess a lot of information is sprinkled across TRiLOGI Programmer's Reference, TRiLOGI on-line Help Files and respective PLC User Manuals. So sometimes, the information may not be available if you refer to only one manual.

One solution may be to replicate some of these information to the other manuals. However, many of our PLC User Manuals already run into more than 200 pages, and we are quite reluctant to add more pages, rendering our documentation unwieldy to new users. Also, many users probably don't use all the capabilities our PLCs possess, so the current documentation tries to cover what we think many users will need for common control applications. For users who require more information on topics that involve more in depth knowledge of the PLC capabilities, we are always ready to help with email and tech support on the forum.

Instead of creating one PDF document with hundreds of pages, we probably need to move our documentation online to enable information to become searchable.  We hope to spare the resources to make that transition in the not too distant future.

Thanks again for your feedback. They are always welcome!

Technical support / Re:Dip Switch 2
« on: October 31, 2017, 08:20:35 AM »
It may be a good idea for some applications, but unfortunately current version of the firmware does not support access to the DIP switch status via the PLC software (it is meant to be handled at the system firmware level only and we didn't want unsuspecting users to mess with the DIP switch settings which could trigger system level events that lead to more support problems).

Since you are a SmartTILE customer it may make more sense for you to add DIP switches to your carrier board as part of the expansion I/Os. That way you get many more DIP switches for your own use.

Having said that, it could still be offered in future firmware version if there is an actual need for it. You can register your strong wish with the development team and see if a customized, trial version could be offered for your testing and if it works well for you it could eventually find its way into standard production firmware.

Technical support / Re:Protecting the TRiLOGI program
« on: October 25, 2017, 07:23:34 PM »
If the user does not need to view the ladder logic, then all you need to do is to make a copy of your .PC6/PC7 file and then delete the entire program but keep all the I/O table and #Define table intact.

Your technician will still be able to go online monitoring to view the I/O status and View Variable screens to view all the data on the PLC.

You can set a create a user password on the TLServer with level 3 access (User level) and this user will not be able to change any variables inside the PLC nor reprogram the PLC.

Technical support / Re:Change TimerSV with Wientek MT8050iE
« on: October 20, 2017, 01:16:04 PM »
Yes you can start a timer using any values. So you can use HMI to store the SV into some DM area so that the Custom function can retrieve the value use it to load into a timer.

Regarding how to use the timer in Custom Function please refer to the following thread:;action=display;threadid=1046

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