Michael Walsh

If the orange COM1 light is on all the time with nothing connected, this sounds like you have a hardware issue with that port.  This is not too surprising considering that Omron has not sold C200HS PLCs in 20+ years (my guess).  

Use =$.  Note that the leftmost byte of the word after your data needs to be a NULL character (00 Hex) to signify the end of the string.   I created some pictures, but cannot attach them....You will need to populate three different memory areas with the hex values of your three different ASCII strings.  Then use the =$ function to compare the actual string in question against the three predefined memory areas.

The EtherNet options with the C200HG were somewhat limited, but Controller Link would work (CLK module), or serial.  Controller Link has a data link option, much like EIP Implicit messaging. For serial comms, you could issue Host Link Commands from the CJ2 PLC to write or read data to / from the C200H if you have a spare serial port available.  

Answered on your other post.  Please only ask one time.  Thanks!

It logs each of the following: 1)  When the alarm occurs 2)  When the alarm is acknowledged 3)  When the alarm turns off This is important to some operations as they want to know how long it took the operator to see what the fault was and how long it took the operator to resolve the issue.

Nothing, except put the PLC in Monitor Mode (for writing).  The cable is not a standard pinout. If the communication settings match and the 3rd party device has properly implemented Host Link communications, it will work.

Sorry, I have not been on here very much as of late.  Trying to catch up.  Conceptually, it looks like it will work.  I would use one Function block and move the info to the inputs and then move away the output data for each execution.  If you compile this code, it fails because the FBs take up too much non-retained memory and the defaults need to be changed.  That being said, if you change the default memory allocations to accommodate the FBs, it should work as is.  

Use the MoveDigit function.  You can pull a digit (Nibble) out of a word and store it in another word or byte.

Do you mean this: A bit turns on and the timer times for a fixed amount of time.  When the bit turns off, the timer continues.  When the timer is done, you can then accept another one shot of the bit. If so, then this should work:

I agree with Crossbow and would advise against trying to have the HMI and controller in different projects

Here is sample code on how to write to a csv.  You will need to create a login on the site to get to the file if you have not already done so. https://automation.omron.com/en/us/support/resources/sample-code/sd-card-write-sample-code-in-njnx-controller Here is a video that explains how to FTP the file from the SD card: https://www.youtube.com/watch?v=a1d81yiaHu0

Looking at your code, your coffee_stop bit will only turn off for 1 scan.  It will then immediately turn back on and the timer will start timing again.  The problem is not the timer in side the FB, but the code as written.

I did this and it worked just fine:

From your drawing it looks like 192.168.250.2 is the correct address.  I am not familiar with the Python side of things.  If I had seen this earlier, I would have suggested that you just write a FINS command (published Omron protocol that can be implemented over Ethernet).  If you let me know what address you want to write to, I can generate a FINS command and Wireshark it and attach the trace for you.  

One note on the NX102: only port 2 supports FINS.