innoaloe

Make sure you're not assigning physical input addresses to the push buttons on the HMI. For example if 0.00 is addressed to an actual physical input address, you must not assign it as a push button address, because no matter how many times you press the button, the PLC will take priority of the actual physical status of the input signal.

Omron NS-Series HMI can supports both FINS and EIP protocol, depending on which is selected during program design of the HMI.   Seeing the packets between CJ and NS in your capture, it uses Omron specific Class ID and Service Code (I see 0x54 there) which is non-standard EIP Packet. That's why Wireshark cannot decode it since the resulting packet is unique to Omron. 0x54 I believe is about finding list of available Network Variables. I cannot say for sure though, since this specific packets are not listed anywhere on any Omron manuals. Did your NS and CJ already connecting? I mean like can you read any value of a memory inside the CJ from the NS screen? Because I believe if you already reading at least on memory, it will show different Service Codes, like 1C, 1D, 1E, 1F, depending on what kind of data you are reading.   I suppose you are trying to replicate CIP Protocol that NS uses to communicate with CJ PLC?

Hello, just got back to check it. What I had in mind is that for the Rcv Function Block you use similar parameters as what I posted above. For Rcv Function Block the major difference is with the Option.isNonResp part, which you need to set to FALSE.   In the Send FB, we can just send the data and ignore any acknowledgement from the other PLC, that's why the Option.isNonResp was set to TRUE in my previous example. You may also change it to FALSE so you can be sure that your data is sent correctly to the other party. In Rcv FB case, actually the NJ will send a request code to the other PLC when this instruction is sent, then in order to fetch the data, it has to receive the response from the other PLC. That's why for Rcv you must set Option.isNonResp to FALSE in order to be able to fetch the data. So it should be something like this :

Your Wi-Fi router might block the Port Number required to access the NB. Check Port Forwarding settings in your router then allow NB Port Number that is used for Web Server.

Both Send and Recv instruction don't have any help files, since Sysmac tried it's best to discourage usage of Omron older PLC functions. Basically these two FBs works the same as SEND and RECV instructions in CX-Programmer, so you can actually refer to the CX-Programmer counterpart to get to understand the meaning of the inputs. Since I don't know what are you trying to accomplish, I'll just put up a sample here on how this instruction is used. It may or may not work, depending on you network configuration. Personally I use this instruction when I need to communicate from NX/NJ PLCs to CP1/CJ/CS-Series PLC. For NX/NJ to other NX/NJ, I prefer to use Ethernet/IP.

NB is "that kind of product", if you know what I mean... As for Sysmac, it was now under Japan for continuos development, but the original release was from Europe I believe.

Everyone these days mentions that it's the era of Industry 4.0... but the truth is IT and Automation people are still not in a good relationship

Cannot really say anything since we don't know how you made the program... also it'll up to you to set the CMMO driver parameters in order for the Modbus to work properly.

Your issue is with the "End Code" settings in your RS-232C settings menu. Currently it is set to "Received Bytes of 256 Bytes". This means the "Reception Complete Flag" (A392.06) will not turn On, unless it managed to receive a total of 256 bytes, thus the RXD will never be called. If you look at the EK's manual page 22 (25 of PDF total page), you'll find the "Terminator" info which are CR,LF. These are typical End Codes used for RS-232C that informs the receiving device like PLC that EK has send the last part of it's data. So, you just need to change your "End Code" settings from Received Bytes to the "CR,LF" one, then download all programs and settings. Restarting the PLC Power after downloading might be required to make sure the new settings is implemented. You mentioned that when the PRINT button is pressed in EK, the LED in CP1E blinks, so I believe the wiring is already correct. PS : Buruan dicoba :D

Hi there! I think your problem lies with the Dividing part. You are using the (/) instruction which results into 1-Word Quotient and 1-Word Remainder. Maybe your actual required Word to contain the Quotient are 2-Words, thus since your allocated memory is not enough, you will get a wrong result. For Dividing function I tend to make a save bet by using the (/L) instruction instead. This is safer since my Quotient will have 2-Words allocation, as well as 2-Words for the Remainder.

I'm no expert, but some Wireless Routers uses Network Bridge / Switch to separate the so called "Collision Domain" between their Wi-Fi and Wired-LAN. So even though both Wi-Fi and Wired-LAN are on the same subnet (e.g. 192.168.250.XXX, and having 255.255.255.0 Subnet Mask) they are still unable to communicate with each other. This is why on some Wireless Routers we need to key in the "Gateway IP" of the Wi-Fi section in our device that connects through Wired-LAN (like the NA in this case). This is to let NA know that any transmission must be routed from the Wired-LAN domain to the Wi-Fi domain. IIRC this type of routers uses what's called "Managed Switch" inside them. Other kind of Wireless Routers uses Unmanaged Switch which basically combines the Wi-Fi and Wired-LAN domain together, so no need to key in the gateway. This typically will cause communication lags if the amount of device connected to the said switch (both through Wi-Fi and Wired-LAN) are a lot, because they need to queue lots of transmission in a single Collision Domain.  

One possibilities is that your Access Point may block port 5900 which is used for VNC, although I'd say it's unlikely. Try to check the Port Mapping function.

Yes, the easiest way is to set a fixed IP on Ethernet Port 2 instead of checking the "Direct Connection" tickbox. The Ethernet Port 2 actually is assigned a specific IP Address when that "Direct Connection" is checked, but I can't remember what was it... If you don't want to change the IP, you can always try to ping that port using arp/a command in command prompt, or by sniffing with Wireshark software

You should be able to find it here :  

Hi again Luca... everyone is still in holiday mood, so it's me again :D How is the connection done between NA and the HMI Viewer app? I suppose you're using an iPhone / iPad? You need to have the NA and the mobile phone connected on a same network. For example you can connect the NA HMI Ethernet Port to a Wireless Router, then have you mobile phone connected to that Wireless Router as well via WiFi. Regarding HostName / IP Address, it depends on your choice. So far I only use IP Address. You can find the IP Address of NA Ethernet Port through the System Screen or from the Sysmac Studio project file.

Whoops, missed this one. I believe you should be able to find the FBs in the toolbox under "Communications" category. And yea,  Happy New Year to you too

Just wondering... since today I see a lot of birthdays, where most of them are most likely bots (you can guess from the names and profile pictures). This usually gonna let to spread of malwares throughout the forum. Anyway, happy new year guys :D

Currently it will only work with Omron's IO-Link Master. The FBs have certain input values that specify whether the Master Node is a NX/GX unit. We cannot specify other type of masters. If you have another IO-Link Master from other vendor that can communicate to PLC through EtherCAT, I believe you will still able to read/write the parameters through EtherCAT communication using EcatSDORead / EcatSDOWrite FBs. However it will require some manual learning of the IO-Link master PDO addressing and commands required that maps to the IO-Link sensors Index and Subindex.

Sorry, I mentioned previous post wrong. What I mean is that prior to Sysmac Studio 1.17, there is no IO-Link FB available. Also, if you have open a project made from previous SS version, most likely the NJ firmware version will be lower than 1.13. This will also cause the IO-Link FB not to pop up in the catalog, eventhough your SS is already 1.17 or higher. So what you need to do is converting the NJ firmware via SS (right click on NJ logo then Change Device), then change it to 1.13 at minimum. This also means your real NJ hardware must  have the same  firmware version as well.

Hello Luca, can you inform what firmware Sysmac Studio, and what firmware version of the NJ you are using right now? The IO-Link hardware, if memory serves me right, was only available after NJ firware version 1.17 and above. If you create a project with firmware version below that, it won't show up in the hardware catalog

Those two FB itself contains the help file you needed to understand how they're supposed to be used. Just press F1 after clicking on the FB. For Index and Subindex, instead of searching through manuals, it is easier if you open CX-ConfiguratorFDT program (should come along with installation of Sysmac Studio) and trace the IO-Link sensors through it. Any properties you want to access will have it's Index and Subindex (basically memory address) shown if you right-click on it (e.g. Operating Hours) For any properties that doesn't have Subindex, it means you put zero as the Subindex in the FB

I cannot really say since I never had experience resetting a PLC system using the Watchdog timer. Did it with microcontrollers, never did it with PLC. So far the only experience I had with watchdog in NJ is when we are using a Loop (e.g. FOR / WHILE loop) with improper counter variable data type that will cause the program to lock in that loop forever. This will return a Task Execution Timeout error. So I guess the only use of Watchdog is to let you know that your program somehow locked somewhere. Still, tracing the source of locking is a different story. As for what crossbow mentioned, it is this thing here. Typically the watchdog is set 5 times your task cycle time, but you can choose another multiplier (smaller).

I don't think it's possible. There's no function in NJ to restart the CPU automatically for whatever errors that may happen. The WDT timeout error also only generates a fatal error that will stop program execution, until the PLC is power cycled / reset manually. Just my own thoughts... isn't it quite dangerous to let the CPU resets by itself when it's running a machine?

Well... if you go to CX-Programmer Help-->Manual--> Function Block/Structured Text Part, you'll find this on page 147. The CP, CJ, CS manuals only talk about ladder instructions. Omron kept the Structured Text manual separated as a single manual for all PLC since it was implemented after initial series launch.

A Function Block is just another type of variable, so you need to define it in either Internal or Global Variables. E.g. make a MyPID Variable with type of PIDAT Function Block. Then in ST you just simply call the instance name MyPID. I will contain all the In/Out of the PIDAT Function Block