PappyJoe (Customer) asked a question.

September 22, 2023 at 11:48 AM
Nitra EIP Problem. Not Accessing Valves or Pal-S06

Using a BRX PLC with the Nitra EIP. I am using the Automation Direct quick setup software. I have ran the setup on the Nitra and have successfully written the setup to the Nitra, confirmed by making X1 on the PAL-SO9 NPN. I didn't change the IP address, made the BRX IP 192.168.192.130 with 255.255.255.0 subnet. I have set up a unit before which is up and running with no issues. I've tried three different EIP units, I've tried three different BRX PLCs. I have used the Ping in the PLC programming to ping the IP and have gotten successful return. It will not turn on the valves or show any inputs to the S06. I have also checked for anything else using the TCP port and it's showing nothing.

  • 34 answers
  • 2.08K views

  • ADC TechnologyGroup_05 (AutomationDirect)

    @tomm (Customer)​ @PappyJoe (Customer)​ ,

     

    This issue has sparked further investigations into the product.

     

    The vendor recently made a change to the Ethernet chip set. The old chip set would report a MAC OUI of 00:02:A2:xx:xx:xx. The new chip set reports a MAC OUI of 14:1A:AA:xx:xx:xx. When notified of the chip set change, we were of the understanding that the behavior of the PAL-EIP functionality was not affected. However, as a result of this investigation, we have found that the PAL-EIP modules with the MAC OUI of 14:1A:AA:xx:xx:xx are NOT behaving the same. Two issues have been found and reported to the vendor:

    1. When assigning the IP address to the new PAL-EIP modules using the EIPCT utility, the device will accept the change of the new network settings BEFORE responding to the request with a successful response. Because the device can no longer respond on the original established socket, the request 'appears' to have failed, even though the new settings have been applied to the PAL-EIP unit.
    2. The 'switch' in Assembly Instance 104 Attribute 3 that is the base of this entire thread was not enabled in the firmware of the new PAL-EIP units.

     

    So, the example code is correct. The process that you have attempted over and over again is also probably correct. This is a firmware issue that you have no control over. The behavior has been reported to the vendor, the vendor is actively working on a solution, and the current stock of PAL-EIP modules has been put on hold until the issue is resolved.

     

    Once new stock is available, please contact AutomationDirect and have these units replaced with updated units.

    Expand Post
    Selected as Best

  • Todd Dice (Customer)

    How did you setup the Ethernet client? I don't see these devices on the list in DMD 2.9

  • PappyJoe (Customer)

    You run an EIP program from the computer to establish that you can see the Nitra. Once it does, you can assign it's address. It defaults to 192.168.192.32, subnet 255.255.255.0 . I leave this alone and address the PLC accordingly. It's set at 192.168.192.130, subnet 255.255.255.0. I can see on the lights on both the PLC and the Nitra that it has traffic, but I can't operate a valve or see any inputs from the modules.

  • tomm (Customer)

    I have the same problem. Both EIPMSGS with the set and get attributes are getting Success with no errors. Everything seems normal. They are not returning anything to the BRX with a BX-P-ECOMEX module. This is on a separate network and different subnet from the rest of the program. There is something in the PAL module not being turned on and after weeks of trying and with tech support i am at a dead end.

     

  • ADC Community_02 (Automationdirect.com)

    @tomm (Customer)​ @PappyJoe (Customer)​ I have forwarded this over to the Pneumatics Product Management Team. We are going to do some testing here on our end to see if we can duplicate. Will keep you posted on any updates we find.

  • ADC TechnologyGroup_05 (AutomationDirect)

    Using the EIPMSG instruction, write a single byte with a value of 1 to the Data Attribute of Assembly Instance 104 using the following information:

    • Class: 0x04 (Assembly Object)
    • Instance: 0x68 (Vendor Specific Instance)
    • Attribute: 0x03 (Data Attribute)
    • Service: 0x10 (Set_Attribute_Single)

     

    Confirm the value by reading the Data Attribute of Assembly Instance 104 using the following information:

    • Class: 0x04 (Assembly Object)
    • Instance: 0x68 (Vendor Specific Instance)
    • Attribute: 0x03 (Data Attribute)
    • Service: 0x0E (Get_Attribute_Single)

     

    If the value in the Data Attribute of Assembly Instance 104 (0x68) is 1, return to reading the Data Attribute of Assembly Instance 101 (0x65) and see if the Input Data is now being updated.

     

    Please let us know the results.

    Expand Post

    • tomm (Customer)

      I ran the instructions and I got the 1 returned at instance 104. But it is still not working. I have something else wrong. I have included a screen print of the instructions. Perhaps that will show something.
      Tom

      • PappyJoe (Customer)

        Tomm, I'm not sure how to see instance 104? Any info would be greatly appreciated. Pappyjoe

      • tomm (Customer)

        What I did was at the bottom of that program I wrote these two instructions and turned off the other EIPMSG instructions. . Memory locations were what I had available. I attached a screen shot of the two EIPMSG instructions. They worked for me, but I am not working yet, but getting closer.

  • PappyJoe (Customer)

    I set up the EIPMSG instructions, The success bit was on when I ran them. I don't know how to look at Assembly Instance 104? Thanks

10 of 34

 

Did this information resolve your issue?