Tag Bit addressing for the EtherNet/IP driver

[Anonymous user]

As per the email exchange with Amy Anger, it would be ideal to have the ability to access bits in the EtherNet/IP analog point tag field as possible in an OPC - Advanced analog point. 

This would allow for clients who use DINTs to package information in their systems fully transition to Geo SCADA smoothly. 

[sbeadle]

Thank you.

[du5tin]

I wonder if this wasn't done because discretes are actually a BYTE coming across the protocol? 0=false, 255=true in the raw form? 

This was requested by several of our clients as well. Bit packing into DINTs is a super common practice. 

[BevanWeiss]

I'd say that this should be implemented more in accordance with Modbus than OPC.

Modbus has a fixed 16 bit register (for IR / HR), requesting any bit reference within such a register is automatically promoted to retrieving the entire 16 bit register.

For PCCC / CIP when such a subindex is referenced, then it should be promoted (in the protocol side) to a full Item access, and then the subindexs split out as configured in Geo SCADA Expert 🙂

It might even be possible to re-use parts of this Modbus code... although in RSLogix world it's possible to apply subindexes on many data types.. DINTs, INTs, SINTs [I think... it's been a little while since I've tried this]

[mohamedsheikhaleid]

GeoScada does not recognize the device's that deal with protocol ethernet/ip, I got files the extension(EDS) but I can't deal with them in geoscada.

field device abb circuit breaker e2.2n.

tanks you..

[sbeadle]

Note:

You can use calculated points (triggered on Tag Processed) to work around this.

These expressions will work out bit numbers:

Bit 0: (".analog" mod 2)

Bit 1: (".analog" mod 4) >= 2

Bit 2: (".analog" mod 8 ) >= 4

Bit 3: (".analog" mod 16) >= 8

Etc.

[BevanWeiss]

@sbeadle another one for your 'Delivered' status 🙂  Certainly Geo SCADA Expert 2025 has this.

[sbeadle]

Delivered in Geo SCADA 2025:

EtherNet/IP Driver

We have extended the digital point support on this driver to enable the individual bit of an integer to be specified in the Tag Name property of an EtherNet/IP Digital Point. For example, you can now specify:

MyPoint.MyDataItem.2

where 2 is the number of the individual bit in the integer.

With an EtherNet/IP Digital Point that is configured to operate as an output point (in order to control plant), you now have to specify the type of data that the point is being used to control. You do this using a new Type field on the Control tab of the point's configuration form.

The type that you specify has to match that of the data item on the controller

[aukevin71]

The issue I have with bits is that using a Rockwell ontroller and trying to extract a bit from an integer using OPC Advanced digital, my address is ESD_FO.ActCauses/0. This naming convention resolves with no issue. When attempting to access the exact same controller and bit of the array, EtherIP throws a config error. EtherIP is working for everything else except for extracting bits in an integer. I have actually tried a .  and [ ] instead of the / , with no sucess either.