EBME Forums Forums Maintenance Technical Assistance mp70 problem

I created a client that imports the data detected by a monitor MP70.
The data I need are heart rate, systolic pressure, diastolic pressure and temperature.
But when I send a Sinlge Poll Date Request requiring all numerical measurements (Partition = NOM_PART_OBJ, Code = NOM_MOC_VMO_METRIC_NU, polled_attr_grp = 0), the system responds me with a INVALID ARGUMENT ROER.

I note that if I ask the patient demographics, the system responds correctly.
I enclose the Single Poll Data Request and the Single Poll Data Result containing the error.
Can anyone tell me where I'm wrong?




Request:


--> From Wireshark Sniffer: the poll data request for PARTITION=NOM_PART_OBJ=1 CODE=NOM_MOC_VMO_METRIC_NU=6 POLLED_ATTR_GROUP=0 (all groups)

No. Time Source Destination Protocol Info
8 0.167832 192.168.2.225 192.168.2.10 UDP Source port: med-ci Destination port: 24105

Frame 8 (78 bytes on wire, 78 bytes captured)
Ethernet II, Src: Dell_a6:88:78 (00:21:70:a6:88:78), Dst: PhilipsP_70:22:02 (00:09:fb:70:22:02)
Internet Protocol, Src: 192.168.2.225 (192.168.2.225), Dst: 192.168.2.10 (192.168.2.10)
User Datagram Protocol, Src Port: med-ci (24005), Dst Port: 24105 (24105)
Data (36 bytes)

0000 e1 00 00 02 00 01 00 1c 00 01 00 07 00 16 00 21 ...............!
0010 00 00 00 00 00 00 00 00 0c 16 00 08 00 01 00 01 ................
0020 00 06 00 00 ....
Data: E10000020001001C00010007001600210000000000000000...
[Length: 36]

--> Data Comment
SPpdu session id = e1 00
SPpdu context id = 00 02
ROapdus ro_type = 00 01 ->ROIV PDU
ROapdus length = 00 1c
ROIVapdu invoke_id = 00 01
ROIVapdu command_type = 00 07 -> CMD_CONFIRMED_ACTION
ROIVapdu length = 00 16 = 22 bytes
Action Argument
Managed Object Id -> m_obj_class = 00 21 = 33 = NOM_MOC_VMS_MDS
Managed Object Id -> context_id = 00 00
Managed Object Id -> handle = 00 00
Scope = 00 00 00 00
Action Type -> 0c 16 = NOM_ACT_POLL_MDIB_DATA
length = 00 08
PollMdibDataRequest
poll_number -> 00 01
partition -> 00 01 = NOM_PART_OBJ
code -> 00 06 = NOM_MOC_VMO_METRIC_NU
attr_group = 0 (all groups) --> PAY ATTENTION: OTHER POLLS HAS BEEN SENT WITH ATTR_GROUP = <a specific group id> but result doesn't change.




Result:

--> From wireshark Sniffer: the INVALID ARGUMENT ROER reply (from the monitor)

No. Time Source Destination Protocol Info
9 1.009063 192.168.2.10 192.168.2.225 UDP Source port: 24105 Destination port: med-ci

Frame 9 (66 bytes on wire, 66 bytes captured)
Ethernet II, Src: PhilipsP_70:22:02 (00:09:fb:70:22:02), Dst: Dell_a6:88:78 (00:21:70:a6:88:78)
Internet Protocol, Src: 192.168.2.10 (192.168.2.10), Dst: 192.168.2.225 (192.168.2.225)
User Datagram Protocol, Src Port: 24105 (24105), Dst Port: med-ci (24005)
Data (24 bytes)

0000 e1 00 00 02 00 03 00 10 00 01 00 0f 00 0a 00 21 ...............!
0010 00 00 00 00 0c 16 00 00 ........
Data: E1000002000300100001000F000A0021000000000C160000
[Length: 24]

--> Data Comment
SPpdu session id = e1 00
SPpdu context id = 00 02
ROapdus ro_type = 00 03 ->ROER PDU
ROapdus length = 00 10 -> 16 bytes
ROIVapdu invoke_id = 00 01
ROIVapdu command_type = 00 0f -> INVALID ARGUMENT VALUE
ROIVapdu length = 00 0a = 10 bytes
Action Result
Managed Object Id -> m_obj_class = 00 21 = 33 = NOM_MOC_VMS_MDS
Managed Object Id -> context_id = 00 00
Managed Object Id -> handle = 00 00
action type = 0c 16 = NOM_ACT_POLL_MDIB_DATA
length = 00 00

Hi Alessandro,

Here is the feedback from our technical expert:

The poll message looks correct. Please check the association request message. You may have negotiated the use of extended polling in the Poll Profile Extensions, but you are using the regular single poll request. If that is the case, either do not request extended polling mode, or use the extended poll data request message.

Hope this helps. If this doesn't help you troubleshoot your code, please reply back with the exact poll request that you are sending.