Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
Technical support / Re: E10 Relay+ inputs
« Last post by support on December 11, 2022, 10:32:42 AM »
Input 1-6 on the E10-Relay+ are all the same. If there is a problem with input #5 please check:

1) The wire from sensor to input #5. Make sure there is no partially broken wire that may intermittently conduct.

2) The input #5 screw terminal. Check that the solder pad at the bottom of the PCB is properly soldered and that the solder is not broken. Also check the solder pad of the resistor arrays connected to input #5 to make sure no broken solder.

You can write a simple program that when input #5 is toggled a counter will start to count down. Now apply a constant +24V DC to input #5 and try to pull the wire to input #5 and observe if the counter is triggered. If that happens it indicates that there are some problem with the input connection and you can continue the troubleshooting from there or request an RMA to send back to the factory for checking.
72
Technical support / E10 Relay+ inputs
« Last post by leonstonebank on December 11, 2022, 10:16:06 AM »
Hi i am using some switches to inputs 1-4 and a sensors on Input 6, Input 5  is causing a problem from a PC IO card
I do not see the input consistently ?
They are 24v PNP inputs
They are using a external PSU, Same as PLC supply do i need to add a wire to the Common?

I have tried Difu in the programme no joy.
I also have removed all the programme so i am just setting a latching relay from the difu from input 5

Thanks



73
General Discussions / Re: Bluetooth LE Apps
« Last post by BetterBath on December 08, 2022, 08:07:34 AM »
Thank you for your efforts. I think they can be very helpful. Unfortunately, the "mymobilehmi.com" link about the app is not working right now, so you can't find out more about it(
LocalhandymanservicesnearPort St LucieClick hereRoofingcontractorsnear mePort St Luciehandymanservicesin Port St LuciehandymanSt Luciehandymanhandymanin port stLucieFloridahandymanservicesnearPort St LucieAbout usclick hereour sitevisit ushandymanhomerepairPort St Luciehandymanin Port St Lucieroofingroofersrepairrepairhandymanservicesclickhandymanservicesin port st lucieroofingroofersrepairinstallationroofrepairroofingroofersroofinstallationclick hereservicesroofrepairrooferspsl roofersour sitevisit usroofinstallationroofingclickhereaboutour servicehandymanservicehomerepairin pslfloridahandymancompanyclickhereformoreinformationaboutour serviceshomerepairservicehandymannear mein Port/url]St Lucie

74
Technical support / Re: MBTCP Time-out was 0 , what does it do
« Last post by support 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 support@triplc.com for upgrade instructions if you don't have it.




75
Technical support / Re: MBTCP Time-out was 0 , what does it do
« Last post by graham.burgess@stfc.ac.uk on December 01, 2022, 07:28:22 AM »
I am trying to add an extra serial port to the PLC, (1 x RS232 and 2 x RS485 is not enough!!!!) this is what the Moxa 5230 is for.
I also have a Weintek MT8071iE HMI that uses modbus on the ethernet to connect to the PLC.
The PLC HMI link works fine until I try to connect from PLC to Moxa, it appears to connected but upsets the HMI PLC link, hence the original question about the timer.
Moxa is server, PLC is client and will execute a <TCPCONNECT 192.....>
which appears to work but, after about 30 minutes, it varies quite a bit, the PLC Moxa link fails without indication.
I am trying to look at messages but not getting very far, my scope is meant to decode but does not.
Update December 2022
The HMI has 1 x RS232 and 2 X RS485 which I am trying to use instead of the moxa as this link is normally very good, especially where the moxa is not connected.
The HMI serial port idea is progressing but it has it's own issues, should this method fall apart I might have to try the moxa idea again.
any thoughts on what is happening?
Cheers




76
Technical support / Re: EEprom Cycles for a data log
« Last post by support 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.
77
Technical support / Re: EEprom Cycles for a data log
« Last post by uknanoman on November 29, 2022, 10:33:20 AM »
Hi Tech
          Thanks for this prompt response. I have used the Fram before on Nano's but it does not look like there is anywhere
left to plug into as I already have the TERM8 I/O Board fitted. Having said this I noticed that there are 4 reserved pins on
the header, is there a way the standard FRAM RTC can be utilised with these pins?

Regards uknanoman
 
 
78
Technical support / Re: EEprom Cycles for a data log
« Last post by support 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 support@triplc.com 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: support@triplc.com and we will contact you to provide free upgrade instructions when the new software and firmware are released.
79
Technical support / EEprom Cycles for a data log
« Last post by uknanoman on November 29, 2022, 01:50:29 AM »
Hi Tech
          I am currently using your new wx100 series to develop a control system for a silo filling control system. One of my requirements is to be able to log data as various events happen,
currently for each event I have used the code below - albeit with varying text on the end according to the event - to write the data to the EEprom area

X$ = STR$(DATE[3])+ " "+STR$(DATE[3])+" "+STR$(DATE[2])+ " "+STR$(DATE[1])+ " "+STR$(TIME[2])+ ":"+STR$(TIME[3])+ " "+ "Enter Button Activated"
Save_eep$ X$,Datalogpointer
Call Incdatalogpointer

The datalogpointer variable simply gets incremented by every call to Incdatalogpointer and eventually reset after say 100 datalogs.
this seems to work ok apart from some strange goings on of the eeprom manager when reading back what I have written.

My question is twofold
1) How many times on the wx100 can the eeprom be written / rewritten
2) Is this the fastest way to do it as I notice a delay in the plc scan cycle when actuating this code

 

80
Technical support / Re: MBTCP Time-out was 0 , what does it do
« Last post by support 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...
Pages: 1 ... 6 7 [8] 9 10