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 ... 210
Technical support / Re: MBTCP Time-out was 0 , what does it do
« on: December 02, 2022, 05:45:01 AM »
I assume you have an Ethernet switch that provides Ethernet port connection to the Fx1616-BA, the Weintek HMI and the MOXA?

The HMI connect to the PLC using Modbus TCP protocol and that part is working fine according to your experience.

The PLC connects to the MOXA using <TCPCONNECT....> command. I assume once connected MOXA works transparently and will transfer data from the PLC to its serial port and vice versa.

1) Does the PLC use this connection regularly?
2) Does the PLC close the TCP connection after transferring data with external serial port or does it keep it open?
3) Does MOXA has a timeout for this connection if it is idle? 
4) Did you define the client connection time-out value on the PLC?

What version is your PLC's firmware? if it is an older firmware (current release is F91.8) you can try to upgrade the firmware to see if it makes a difference. Contact for upgrade instructions if you don't have it.

Technical support / Re: EEprom Cycles for a data log
« on: November 29, 2022, 04:43:35 PM »
Sorry the FRAM-RTC on the Nano-10 and FMD PLC cannot be used on the Wx100. They are different interface.

To use FRAM on the Wx100 would require custom-designed carrier board since we don't provide this on our standard Wx-TERM8 or Wx-TERM16. It is therefore not an option for one off type of projects.

Technical support / Re: EEprom Cycles for a data log
« on: November 29, 2022, 08:11:57 AM »
The EEPROM on Wx100 has erase/write cycle life of 1 million cycles. Erasing and writing of EEPROM cells does take a bit of time and may affect the PLC scan time. When you save a string to the EEPROM you are saving multiple bytes of data (up to 40 bytes per string) so the time delay multiplies by the number of bytes.

If you are developing an OEM equipment that you intend to manufacture in quantity (> 100 per year) then it is possible to add other useful components that can enhance your application need such as FRAM (works like EEPROM but with no life limit and a lot faster - writing to FRAM takes very little time since there is no "erase" cycles to deal with).

Wx100 is an excellent brain board platform (similar to our SmartTILE-Fx brain board system) that allows OEM customers to design and build their own custom carrier board (we call these "terminal boards" in Wx100) which can include customized components such as FRAM and battery-backed RTC (for applications that have no internet connection but still need to keep a real time clock running).  Please contact to discuss your application if you wish to pursue an OEM custom terminal board design.

We are currently also adding new HTTP client capability which allows Wx100 to very easily connect to a HTTP or HTTPS web server to upload data via HTTP POST protocol, or download data from a web server via HTTP GET protocol. You can also log data to local data files in your PLC file system and then periodically upload the selected files to web server via HTTP mutlipart POST protocol before deleting it. This is in addition to the support of MQTT protocol already available on your Wx100 and thus further enhancing its IIoT capability.

You may like to consider using these new capability to log your data to a web server for permanent storage when it becomes available (should be pretty soon). Please register your interest by emailing to: and we will contact you to provide free upgrade instructions when the new software and firmware are released.

Technical support / Re: MBTCP Time-out was 0 , what does it do
« on: November 15, 2022, 06:50:13 PM »
If the MBTCP time-out is set to zero then the firmware will automatically adjust the MBTCP server time-out to 20 seconds.

Note that this time-out is for the PLC acting as slave (Server) to an external Modbus TCP master (client). 

Did you try to run "PRINT #4 "<TCPCONNECT xxxx>"? Note that TCPCONNECT is for the PLC to act as a client to access an external TCP server. It is not to be used to configure the PLC as a Modbus TCP server.

I checked the Moxa 5230 - it appears to be a MODBUS TCP-to-MODBUS RTU gateway converter? If you want to access the serial port on the Fx1616-BA PLC from an external Mobdus TCP master then MOXA 5230 can be used but you must configure the serial port on the MOXA to be compatible to that on the PLC. I don't understand why do you want to do that since you can already directly access the PLC via its Ethernet port...

Technical support / Re: PLC INPUT Interrupt Behavior
« on: October 14, 2022, 01:44:07 PM »
Hi Gary,

Thanks for the details explanation of your setup.

One thing about the particular CPU chip family that is used on Fx, FMD and Nano-10 PLCs is that the interrupt input operates using the "input capture interrupt" mechanism and due to the CPU chip hardware limitation, when used in "input capture interrupt" mode the logic level on the input pin cannot be reliably read by the firmware. Hence when a digital input has been defined as interrupt input (especially for input 1 to 4) the pin logic state are no longer visible to the ladder logic. This is due to chip hardware limitation that could not be overcome by the firmware. When you INTROFF an input pin inside an ISR , it will be reset to become a general purpose input again.

The general purpose input logic state are only updated during the I/O scan which normally occurs only at the end of the ladder logic scan. or after running a REFRESH statement. So right after your ISR has disabled the input interrupt, the digital input status will not change regardless of the actual physical voltage level. At the end of the ladder logic scan the I/O scan routine is the one to update the the physical input but the software filtering may yet filter out the new state and therefore requires another scan before the new logic state is finally determined.

The new Wx100 CPU is different in that the actual logic state of the physical input is still visible to the firmware when it is being defined as an interrupt or a HSC input so I believe your experience with Wx100 CPU should be different.

Technical support / Re: PLC INPUT Interrupt Behavior
« on: October 09, 2022, 01:02:28 PM »
It is generally not recommended to use a digital input both as a general purpose D/I and an interrupt input at the same time by manipulating with INTRDEF and INTROFF especially if you need the D/I to function immediately within the next scan. Note that the interrupt is edge-triggered whereas the general purpose digital input is level-determined. The PLC firmware also deploys a software filtering mechanism to filter out what it deemed as "glitches" whereas when defined as interrupt input there is no filtering and that can also add to some uncertainty. For most PLC logic if the current scan misses the new input state change it is generally harmless to delay to the next scan to pickup the new input level.

My guess is that when the ISR is triggered the voltage level may still be midway between logic '0' and logic '1' but the edge transition has triggered the ISR to run and after you have disabled the input as interrupt it still may not reach the logic '0' or logic '1' voltage and hence is not picked up by the I/O scan (throw in some switch bouncing and that may further complicates the scenario). I hope that make sense...

BTW which specific PLC model are you using for this test?


Technical support / Re: Small quibble on Version 7.5 Build 14
« on: September 10, 2022, 12:12:40 PM »
Thank you for your feedback. We will look into these reported issues and fix them in future release of i-TRiLOGI. Please continue to feedback to us any quibbles :)

Technical support / Re: EZWire1616 Stepper controller OUTPUTs
« on: September 09, 2022, 09:09:27 AM »
Currently you can print out the entire online manual into a single PDF by using the browser's PRINT function and select "Save to PDF".

We just did that and uploaded the current version to our documents page:,%20Compiler,%20Simulator.pdf
It doesn't have a bookmark page linking to each chapter. We may manually put up one in future. i-TRiLOGI is still being updated with more cool IIoT functions being introduced so it is best to refer to the most up-to-date version online (

Technical support / Re: EZWire1616 Stepper controller OUTPUTs
« on: September 08, 2022, 01:19:54 PM »
Thank you for letting us know.

The best way to access the documentation for Fx1616-BA is to go to:

Scroll down and click on the "Documentation" tab and all the updated links are presented there:

Anyway, please see updated documentation links as follow:

Technical support / Re: EZWire1616 Stepper controller OUTPUTs
« on: September 07, 2022, 09:48:41 PM »
EZWire1616 is controlled by the SmartTILE-Fx CPU which is the same as that on Fx2424 and Fx1616-BA.

The default stepper motor channels for STEPPER 2 is indeed Outputs 9 & 10.   If you run a function that comprises only the following two lines:

   STEPSPEED 2,100,10
   STEPMOVE 2, 5000, 5

You should observe that the pulse are sent out of the output 10. If you run negative pulses then the direction signal will turn on Output #9.

SmartTILE-Fx does support 3 stepper channel so EZwire1616 should support 3 stepper channels as well.

When Fx1616-BA was released, there were only 4 high speed digital outputs 5 to 8  as all the other outputs are all relays. To support application that may want to use two stepper channel, we provided a special way of using output 7 & 8 as pulse and directional output for STEPPER #2. However, this is only activated when you run the stepper using

      STEPMOVE 32, count, relay#

I wonder if you have accidentally run the above command and thus observing stepper output on 7 & 8?

Technical support / Re: NANO-10 and Weintek MT8050iE 4.3" Touch panel
« on: August 15, 2022, 11:52:49 AM »

The simplest way to have all three devices connected simultaneously is to use Modbus RTU over the RS485 port for your TX4S as you had been doing, and then connect the HMI to the PLC via Ethernet.

The Nano-10 and MT8050iE can be connected directly via Ethernet or through a switch. I assume you are programming the Nano over Ethernet, so you would need a switch in order to have both the PC and HMI communicating with the Nano.

Using the TRi_Fx driver, you should be able to communicate via Ethernet. Alternatively, you can use the Modbus TCP driver provided by Weintek.

Technical support / Re: Omron Host Link communication with Tri-PLC
« on: June 19, 2022, 09:34:27 AM »
Thank you very much for letting us know that you are able to communicate with Omron PLC using the NETCMD$.

I assume that the "C-mode commands" protocol format must be backward compatible with its original "Host Link Command" protocol. So it is good to learn that TRi PLCs are still able to talk to these newer generation of Omron PLCs. As long as you get a list of the C-mode commands from Omron manual you should able to read/write to registers that are only available to newer generation of Omron.

Note that the new MQTT capable, WiFi/RS485 Wx100 PLCs also support the NETCMD$ command via its RS485 or TCPIP communication channel.  So you can use the Wx100 as a very low cost controller to serve the Omron PLCs. E.g you can use the Wx100 to read data from Omron PLC via RS485 and then publish the data to MQTT via WiFi when certain conditions are met (e.g temperature exceeds certain threshold) . It opens up a lot of possibility to perform very sophisticated industrial IoT functions.

Since Wx100 can also act as a Modbus RTU (RS485) master or as a Modbus TCP client it can interact with a mix of factory equipment that uses Omron and any Modbus compatible controllers to provide IoT service without the need to re-engineer older equipment that contain controllers which are not capable of doing IIoT.

For more info, please visit:

Technical support / Re: TCP-IP and ID goes to 0xFF
« on: April 13, 2022, 09:56:25 AM »
Does your FMD PLC have FRAM-RTC?

If the PLC does not have FRAM-RTC installed, then are you using a power failure interrupt routine to save parameters using SAVE_EEPx to non-volatile memory  during a power failure? Or is your program running the SETTIMERSV or SETCTRSV command during operation and need to be saved to non volatile memory before power failure?

Please refer to Section "1.7.2  Non-Volatile Data Store" in the FMD PLC User Manual which explains how the pseudo EEPROM works and why you could lose data if power failure interrupt routine is not given enough time to back up the pseudo EEPROM data to flash memory.

When you power down a machine by turning off the AC power, the DC output of the power supply usually have enough capacitance to gradually decay to zero so the power failure interrupt routine can work properly.

When you press the emergency stop button, did you cut off the DC power supply to the PLC immediately? If so then the interrupt service routine is not given enough time to save the parameters. What happens is that the flash sector is erased but the CPU did not have enough time to copy the pseudo EEPROM data to the flash and therefore you lose the Ethernet parameters as well.

If you wire your emergency stop button such that it only cuts off power to the I/O but not to the PLC, then this issue should not happen.

Alternatively, organize your program so that if you need to save some data to non-volatile memory or need to change the timer or counter set values using the SETTIMERSV or SETCTRSV, then do so in the main program itself and execute the SETSYSTEM 252, 0 command to backup the new data to the flash memory  immediately so that the CPU will not attempt to save the changed data to flash memory during power failure. Of course you should take into consideration that there is a 100K erase/write limit to flash memory and therefore your program must avoid erasing/rewriting to the flash memory so often that exceeds its life cycle limit and wear out the flash memory.

Technical support / Re: Nano10 MCU chip temperature
« on: February 27, 2022, 04:09:55 PM »
The Nano-10 CPU can get quite warm due to the integrated Ethernet PHY on the main CPU. It is however well within the chip's operating temperature range and has never become an issue for all the applications that it has been used in so far. If the control panel that contains the Nano-10 is very tight air space and completely sealed then adding a heat sink or a fan would certainly lower the temperature a bit.

Technical support / Re: Nano10 RS-485 Modbus termination
« on: February 22, 2022, 01:17:08 PM »
Thank you very much for sharing your experience which we are sure will benefit other users.

Some RS485 devices do require biasing on pull-up and down on its RS485 port to work properly. In most low speed and short cable applications the Nano-10 PLCs would not require biasing and it is likely that the power monitor is the party that requires biasing on its RS485 bus line.

Actually in Chapter 15.5 of the Nano-10 User Manual (please download from there is a section describing the RS485 that also suggest using biasing resistors for more robust communication, as shown in the screen capture below:

Pages: [1] 2 3 ... 210