viRead of ENET resource truncating at 96 bytes

[RGTer]

Using niEthernet driver. The _put function works as planned. The _get function is truncating received data at 96 bytes. The VI_ATTR_TERMCHAR_EN and VI_ATTR_SUPPRESS_END_EN attributes are not applicable to this driver. This _get function just wraps the viRead function. Is there something special about the resource type that is affecting what we are reading?

[RGTer]

Just to add a little more info:
NI-VISA version is 2.6
LW/CVI version 6,
NI-488.2 version 1.70
NI-VXI version 3.2
niEthernet version 1.0.0

Thanks for any insight. This is becoming project critical.

Randy Gritton

[ScottieB]

Hello,

I believe you have also started a support request with Tori of our PXI group with which I am involved. Is there a specific reason that you are using this low-level driver for your PXI-8211? Does your application prevent you from using this card as though it were a regular ethernet card? It seems like you are writing low-level packets to the card rather than using the standard Windows API to write IP or other protocol packets out the interface.

I'm also not familiar with this niEthernet driver that apparently was designed to do this. Is it possible that this driver was written specifically for your company?

Thanks,
Scott B.
GPIB Group
National Instruments

[RGTer]

Hi Scott,
Yes, we are working with Tori. I am trying to get all of this coordinated through her.

The driver may have been created for the company we are supporting. We don't have a lot of details on from where this thing came. The driver basically just wraps the viRead/viWrite commands. This si why I am concerned about why the viRead is truncating at 96 bytes.

[ScottieB]

I'm not sure that the viRead should be returning more than 96 bytes. Perhaps what it is returning is not actually the data of the ethernet packet, but something else. I'm only speculating here.

However, more importantly, I'm still wondering why you are using this specific driver. Why not use the standard ethernet driver and let the card be recognized as a standard ethernet NIC in Windows?

Scott

[RGTer]

The data we are capturing is the first 96 bytes of what is expected and the 96th byte is not a termination character.

I forwarded a description of the application to Tori and asked her to get all of us into the email thread. I won't duplicate all of that here.