Internet PLC Forum

Hi Gary
          Thanks for this response. On the face of what you are explaining it would appear that the wx100 must default to set system 16,5 because inputs 81 onwards seem to retain a forced state via the monitor I/o control or as I have found out by using input[6]=dm[10]. In these cases it seems not to be overwritten with a 0. So with your suggestion in mind I will try a set system 16,1 and see how it responds when I get back to work next week. You may be wondering at my thought process regarding storing of (data) at input points. It is simply that because the (data) is data related to physical inputs from a remote i/o block via modbus, I prefer to map them into into an input area of the plc for the clarity of inputs being inputs and subsequently being prefixed with an (i) eg i81 when looking at a ladder diagram. As you have rightly perceived data is after all data whether it is I/O or other my problem is that I can get a bit picky sometimes about how I want that data to appear in the context of the program. Thanks for your input into this post much appreciated, I will let you know how I get on.
Regards Peter

Your attempt to use INPUTs as general purpose data storage has a small problem. When the PLC ladder logic is running it will overwrite all of the INPUT values during each scan of ladder logic. You are using INPUTs that your PLC does not physically have but the ladder logic code does not know how many INPUTs your PLC actually has (or are actually being used) so it scans  the maximum number of INPUTs that ladder logic can handle.  This number is way more that 16. This is why your are seeing your "special" INPUTs getting cleared to 0.

I suggest that you store data in either DM[] or RELAYs. If you store your DATA in RELAYs you can make it visible on the first page of the simulator / on-line monitor.

If you insist on using INPUTs for data storage you may need to use the SetSystem 16,n statement on the the first scan of your PLC program. The SetSystem 16,n sets the number of I/O pins that will be accessed.  The "n" argument affects the number of I/Os to access. When n=1 the I/0 pins 1-16 will be scanned. When n=2 then pins 1-32 will be scanned.

SetSystem 16,n is intended to help speedup the execution of ladder logic by restricting the number of I/Os that must be processed on each pass thru the ladder logic.

I use SetSystem 16,n for it's intended purpose to speed up the ladder logic execution. It works for this purpose You will need to test and verify if SetSystem 16,1 will solve the problem that you have created. 

Gary Dickinson

Thank you for the report.

We have added the following section to the Wx100 online documentation:

https://docs.triplc.com/#7304

You can use STATUS(22) which indicates a successful WiFi connection when it returns a 1.

E.g.

IF STATUS(22) <> 1      ' WiFi is not yet connected. Do nothing now.
   RETURN
ENDIF

Hi Tech Support
                       Here's an attached screen shot of the problem when just after the failure occurs. In this case the monitoring lasted for about 10 secs before locking. The time period before locking does appear to be variable. The dos window contains everything from a clean restart of the iTrilogI so it seems to include the initial connection data log.

Regards Peter