Recent Posts

Pages: [1] 2 3 ... 10
1
Technical support / Re: HMI to FMD write INPUT
« Last post by Forum Admin on January 02, 2026, 11:38:52 AM »
Happy New Year!

The highest physical inputs for FMD, Fx and Nano-10 PLCs are 128.
2
Frequently Asked Questions / Re: Explain how the SmartTile differs from your PLCs
« Last post by Forum Admin on January 02, 2026, 11:34:38 AM »
[Admin's note]:  The following answers are supplied by our A.I. chatbot which we have verified to be largely accurate and thought it could be useful.
________________________________________________________________________________________________________

The SmartTILE is not a standalone PLC in the usual sense – it is the CPU “brain board” used inside TRi’s Super PLCs, made available so OEMs can build their own custom PLC hardware around it.

Here is how it differs from complete PLCs:

1. Role in the system

    SmartTILE:
  • Described as “the brain of Triangle Research's high-end, time-tested and proven F-series PLCs.”
  • Each F‑series PLC is made of two parts: 1) “The SmartTILE‑Fx CPU board, which is the brains of each F‑series PLC. It is identical throughout the PLC family.” 2) “The carrier board, which is the electrical interface between the SmartTILE controller and more common industrial voltage level I/Os.”

    PLC (e.g., Fx1616‑BA, Fx2424, FMD series, Nano‑10):
  • A finished controller that already combines the SmartTILE CPU with a carrier board, industrial‑level I/O, power conditioning, connectors, and mounting options.

[Editor's notes:] FMD and Nano-10 do not use SmartTILE but have integrated the many of the SmartTILE functions directly into its own circuit board. They are slightly lower cost but are less powerful than the SmartTILE based PLCs such as the Fx2424 and Fx1616-BA.

2. Target users and purpose

    SmartTILE:
  • Offered “to small, medium, and large OEM equipment makers to easily build their own private‑labeled, low cost, network‑ready Super PLC… purpose‑built to fit their equipment perfectly.”
  • Lets OEMs “design their own carrier board to interface to the specific I/O and communication signals demanded by their application or industry.”
  • Intended to shorten time‑to‑market by prototyping on standard F‑series PLCs, then migrating to a custom SmartTILE‑based design.

    Standard PLC
  • Aimed at users who want a ready‑to‑use industrial PLC with fixed I/O mix and form factor (e.g., Fx1616‑BA, Fx2424, FMD88‑10, Nano‑10).

3. Hardware integration and I/O

    SmartTILE:
  • Integrates all key controller functions: “Ethernet port, UART serial port, FRAM, RTC, file system and of course, the 5V digital and analog I/Os.”
  • Exposes signals via two 40‑pin 0.1" headers so an OEM can design a custom carrier/interface board and still “fully access all the SmartTILE features.”
  • On its own it provides:
    • 16 digital inputs and 16 digital outputs (5 V CMOS), expandable “up to 128 Inputs and 128 Outputs
         with some additional circuitry on the OEM's carrier board.”
    • 8 analog inputs and 4 analog outputs (0–5 V).
    • 3× UART (3.3 V), 1× I²C port, LCD port signals via the headers.
    PLC:
  • The carrier board converts SmartTILE’s 5 V CMOS and header signals into field‑ready I/O (e.g., 24 V digital I/O, relay outputs, analog ranges like 0–10 V or 4–20 mA, terminal blocks, etc.), and provides mounting and power interface.
  • Example: Fx1616‑BA and Fx2424 are described as complete “Super PLCs” whose “brain board… is the SmartTILE,” but they are sold as finished PLC products with integrated I/O and connectors.
   

4. Flexibility vs. off the‑shelf completeness

    SmartTILE:
  • A platform: “Use SmartTILE as a platform for multiple carrier boards to serve different applications.”
  • Lets you “lower cost and simplify overall design by consolidating components” and tailoring I/O and connectors to your machine.
  • Best when you want a custom PLC that still uses TRi’s proven CPU, firmware, and i‑TRiLOGI programming environment.

    Standard PLCs:
  • Fixed hardware configuration – you choose from existing models and expansion boards rather than designing your own carrier.
  • Faster if you just need a controller you can mount, wire, and program immediately, without hardware design work.

5. Programming and software

    Both SmartTILE and TRi PLCs:

  • Programmed with the same i‑TRiLOGI (ladder + TBASIC) environment; SmartTILE‑Fx “is programmable by the Floating‑point version of i‑TRiLOGI Version 7.xx (TL7).”
  • This means software development is essentially the same; the main difference is whether you are using a custom carrier (SmartTILE‑based) or a standard PLC board.[/i]
In summary:
  • A TRi PLC (Fx‑series, FMD, Nano‑10, etc.) is a complete, ready‑to‑install controller.
  • SmartTILE is the embedded CPU core of those PLCs, sold separately so OEMs can design their own carrier boards and create custom PLCs that still use TRi’s proven hardware, networking, and programming tools.

For more details, see:
  • SmartTILE product page: https://triplc.com/smarttile.htm
  • Fx‑series manuals, “Create a Custom PLC with SmartTILE” section (e.g., Fx1616‑BA / Fx2424 User Manuals, Section 1.11).
3
Frequently Asked Questions / Explain how the SmartTile differs from your PLCs
« Last post by Forum Admin on January 02, 2026, 10:33:33 AM »
Why choose SmartTILE instead of a standard PLC model?
4
Technical support / Re: HMI to FMD write INPUT
« Last post by acxysty on December 22, 2025, 04:39:42 AM »
Thank you for your answer.
What is the highest physical input address  ?
Regards
Thierry
5
Technical support / Re: HMI to FMD write INPUT
« Last post by Forum Admin on December 17, 2025, 10:39:07 PM »
You are using input #150? Note that it is not a physical input on an FMD PLC, but it can be used as an internal flag for the ladder program to control something. So yes you can read and write to it and it will keep its last logic state written by the Modbus client.

When you write to Input #15 - this is a PHYSICAL INPUT.  What is written to the PLC's input will only exist for less than 1 scan time because af the end of the ladder program the PLC will update the physical inputs and outputs and thus the INPUT #15 will be overwritten.  We do not recommend writing to the physical input as it may or may not activate the circuit that is waiting for it to be set to "1"  - it depends on when the input is written relative to the rung of circuit in the ladder program.
6
Technical support / HMI to FMD write INPUT
« Last post by acxysty on December 16, 2025, 08:39:33 AM »
Dear Tri PLC

We try to use Weintek HMI to FMD with MODBUS TCP.
We manage to write in INPUT 150 using 1x format? It works fine.
However when we want ti write a value to input 15 using the same procedure it fails...
Not sure to understand why ?
Thank you in advance for your help.
Regards
Thierry



7
Technical support / Re: NANO-10 Analog Input Protection
« Last post by BetterBath on August 26, 2025, 12:24:48 AM »
I ran into the same issue protecting ADC inputs on soil sensors and solved it with a 10k resistor, 3.6V Zener, and small cap — worked well in practice.
tree removal fort myers
8
Technical support / Re: NANO-10 Analog Input Protection
« Last post by garysdickinson on August 18, 2025, 11:08:21 PM »
Nano-10 analog inputs update.

I did actually destroy one NANO-10 by connecting both ADC  inputs to 20 VDC.  This seems reasonable but stupid on my part.

The second and 3rd NANO-10s have not been damaged.  I simply wrote bad TBASIC code and the "flailing" ADC was the result of a a coding error.

Just wanted to come clean.

Gary Dickinson
9
Technical support / Re: Network Services <PING 192.168.1.99> command?
« Last post by support on August 15, 2025, 10:37:01 AM »
Sorry the TRi PLC currently do not send PING command to another device.

However, if the device has an open TCP port you can try to make a connection to the TCP port and check if connection is successful by examining the STATUS(3).  You can then disconnect from the device after making an initial connection.
10
Technical support / Network Services <PING 192.168.1.99> command?
« Last post by wnaegle on August 15, 2025, 08:44:15 AM »
I need to continually verify a non-TRI-PLC device is connected to the network.
Is there a way to ping another non-TRI-PLC device on the network?
The devices I need to ping do not have a published TCP connection.

For example, is there a Network Services command
PRINT #4 "<PING 192.168.1.99>"
Pages: [1] 2 3 ... 10