# Omron NJ PLC using FINS/TCP Cant See Tags **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [November 28, 2023, 3:07am UTC](https://forum.inductiveautomation.com/t/omron-nj-plc-using-fins-tcp-cant-see-tags/82409 "2023-11-28T03:07:34Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Saad\_Ali\_Hassan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/saad_ali_hassan/32/52363_2.png) [@Saad\_Ali\_Hassan](https://forum.inductiveautomation.com/u/Saad_Ali_Hassan)\ **Post date:** [November 28, 2023, 3:07am UTC](https://forum.inductiveautomation.com/t/omron-nj-plc-using-fins-tcp-cant-see-tags/82409/1 "2023-11-28T03:07:35Z")
Hi all, I am using Omron NJ Driver for my Omron NJ101 PLC to read/write tags in Ignition. The response time is very slow (4-5 secs) e.g. any button for turn off/on. Could be a network-related issue. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/2/52902a4bb94aabbe1ad00fefa8c09296f741956b.png) On the side, I decided to test the response time using the FIN/TCP driver but I can't see tags from the Omron PLC. I already imported the config tag file from Omron in the 'address' of the device connection. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e0de7107e8abf701596bb0958022cc9655721b98.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/8/6821217be43ff4164a0a3d8ada0eb86311fa92f0.png) Am I missing something or it's not possible to do so? These are my setting in Ignition and Omron PLC for FINS/TCP: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/6/2696d2219046663b7ce497bcbcbc64b89c6262c9.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/f/4fe8640ae58b790498567026fe8c7a32dca7a214.png) ---
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [November 28, 2023, 3:20am UTC](https://forum.inductiveautomation.com/t/omron-nj-plc-using-fins-tcp-cant-see-tags/82409/2 "2023-11-28T03:20:00Z")
The import/export format for the FINS driver is just a simple CSV format. The file you import for the NJ driver will not work. First column is the name/path for the tag. Second column is the address, in the format described in the user manual. FINS does not allow you to address tags by their symbolic name that you see in the PLC. It's a name/path assigned to an area and absolute address. The entire mapping page is optional. You can also just manually create tags in the Ignition Designer, with an OPC Item Path that uses the addressing syntax. [https://docs.inductiveautomation.com/display/DOC81/Omron+FINS+Driver#OmronFINSDriver-Addressing](https://docs.inductiveautomation.com/display/DOC81/Omron+FINS+Driver#OmronFINSDriver-Addressing) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 28, 2023, 12:53pm UTC](https://forum.inductiveautomation.com/t/omron-nj-plc-using-fins-tcp-cant-see-tags/82409/3 "2023-11-28T12:53:59Z")
You might also find my alternate EtherNet/IP driver helpful: > [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190): > > Automation Professionals is pleased to announce its latest EtherNet/IP Communications Suite driver module, a major upgrade to its EtherNet/IP Class1 Communications module, as a Public Beta. As of April 15, 2023, this is now a Production Release. The primary new feature is its new Generic EtherNet/IP Client Driver, a drop-in replacement for IA's Logix V21+ driver and its Omron NJ/NX driver. It does work with older Logix processors, and also works with Rockwell's MicroLogix 8xx family (ethernet… Based on my lab results, and some user reports, it is blistering fast. And does not need to have any tag list imported--it browses the NJ processor's global tags (except non-published). ---
**Author:** ![Saad\_Ali\_Hassan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/saad_ali_hassan/32/52363_2.png) [@Saad\_Ali\_Hassan](https://forum.inductiveautomation.com/u/Saad_Ali_Hassan)\ **Post date:** [November 28, 2023, 10:09pm UTC](https://forum.inductiveautomation.com/t/omron-nj-plc-using-fins-tcp-cant-see-tags/82409/4 "2023-11-28T22:09:27Z")
Thanks guys. I am having a look into it. FINS/TCP works a bit faster for some reason but not ideal as I'd have to recreate all tags with addresses.