AnsweredAssumed Answered

N7610C API issue

Question asked by Diego on Aug 24, 2018
Latest reply on Dec 5, 2018 by thysell
  • Comment • 5

When using N7610C API to generate an 802.15.4 frame, the resulting Data Length is wrong. The MAC payload length is configured using:

 

api.WaveformSettings.PhyPayload.DataLength = X

api.WaveformSettings.ZBSettings.PhyPayload.DataLength = X

 

However the resulting frame has X + 2 bytes as MAC payload length. Two bytes (0x00 0x00) are always added at the end of the payload.

 

In the case the frame is generated using Signal Studio for IoT interface as indicated in 802.15.4 Setup the MAC payload length is correct.

 

Any idea on why this might be happening?

 

Thanks,

Diego

thysell
thysell Employee Dec 5, 2018 7:41 AM
Correct Answer

Hi Diego,

 

I'm not familiar with N7610C but I checked with the Signal Studio team and this was their response.

 

This can be solved by using below API to set the payload data, i.e. add “9 Byte(s)” at the beginning of MacHeader string.

 

api.WaveformSettings.ZBSettings.PhyPayload.MacHeader = "9 Byte(s) [8841,66,1AAA,FFFF,,3344,]";

 

We have updated the N7610 help file to add below description. The updated online help has gone live on Keysight.com, and the next N7610 software release will include the updated N7610.chm file as well.

 

Hope this helps.

 

Pete

See the reply in context
No one else had this question

Outcomes