Reading data from Keyence IV4-600CA camera over Ethernet/IP

[alemberskiy]

Hello everyone,

Was wondering if anyone has successfully performed reads and writes to Keyence IV4 camera using Ethernet/IP blocks.

I can connect to it no problem, it seems like i should be able to read the assembly - instance 100 returns 500 bytes for some reason, but 110 returns 104 bytes, matching the manual, but it always zeros. Changing the values for 'trigger', for example, also doesn't have any effect.

I've tried a few examples I've found here for other products without success. The manual doesn't mention class or attribute - perhaps that's my biggest problem as I'm trying to guess here. Class 4, attribute 4 returned two bytes, 244 and 1, whatever that means; otherwise it looks like only class 4 attribute 3 doesn't have an error.

Thank you all!

[ChuckyDoky]

Maybe you should modify your Output Size, I tried to use your VI with an IV2 (i found your topic when I was looking for information, or a guide to make my application), IV4 does not have a Fieldbus manual yet, but the manual have the info of the output size, as the 1ST image, when i update the file with that information, I'm having an error on the output, but if I make a Trigger, the program sometimes works, not every time, but if a press the button like 3 times, at least in one case, the trigger works, but sometimes shows the error on the output and input, if  i use other output size, it shows me the error: "not enough data" or when i use more than 12, shows me: "to much data", you should try with 12 as output size, If you found a solution i would appreciate if you share it

[alemberskiy]

I have tried changing the output size and getting an error if its not the correct size, but if it is, I get no error and the data is still all zeros. The support for Keyence said i can't make Ethernet/IP work from the PC, I would need to get the PLC in between to act as a scanner for this specific device. Not sure if I'm fully trust it, but since I couldn't get it to work and had to get the project moving, I gave up on Ethernet/IP and went with the "TCP/IP Non-procedural Communication". Its more work but then you get to control every little detail, so it was ok for me.