Documentation on 'Wireless Device Type Codes'

[Breina]

The PowerTag Link documentation (DOCA0157EN-07.pdf) had a table mapping Device Code and Identifiers to Device Types;

The Panel Server documentation (DOCA0172EN-09.pdf and DOCA0241EN-06.xlsx) don't have such a table. Was wondering if there's one that's maintained more recently. I have a user with a product identifier of '17973', and I'm not sure what the device's capabilities are.

I'm sure I've missed it somewhere, please help me find it?

Thanks in advance! 🙂

[Romain_Polette · Accepted solution]

Hello @Breina , 

Why not using the Modbus function code 43-14 to read device identification ?

Table in your post is related to Modbus Registers 31025 and 31032 for any wireless device connected to the old PowerTag Link. 31025 not applicable to the Panel Server.

For Panel Server only register 31032 "Wireless product identifier" is available, but.... I cannot find any public documentation explaining returned values...

FYI 17973 = PowerTag Rope Sensor R200 for IEC Market. Codes in the PowerTag Link table are not all listed.

Regards, 

[Breina]

---

@Romain_Polette wrote:

Hello @Breina , 

Why not using the Modbus function code 43-14 to read device identification ?

Table in your post is related to Modbus Registers 31025 and 31032 for any wireless device connected to the old PowerTag Link. 31025 not applicable to the Panel Server.

For Panel Server only register 31032 "Wireless product identifier" is available, but.... I cannot find any public documentation explaining returned values...

FYI 17973 = PowerTag Rope Sensor R200 for IEC Market. Codes in the PowerTag Link table are not all listed.

Regards, 

---

Hi Romain,

Thanks for the suggestion! I can retrieve the Panel Server's identification this way (slave 0xFF), but when prompting wireless devices for this (slaves 100 and up) they respond with 'Illegal function'.

I'm fine with just retrieving commercial references for Panel Servers and PowerTag Links, but SmartLinks do not support this function; it seems to rely exclusively on the wireless device codes (DOCA0115EN-03.pdf).

I would love to keep my software compatible with all old devices, yet up-to-date with all future EcoStruxture developments. Is there any chance you could publicise an updated table for this?

Regards,

Brecht

[Romain_Polette]

Hello @Breina , 

You are right... PowerTag is not supporting Function code 43-14 through Panel Server...

But it works well through PowerTag Link (see below):

This is strange because Modbus Serial devices connected to Panel Server support the Function Code 43-14:

@Eric_HAVAS can you check if this is expected with 1.9 ?

• Function Code 43 not supported for Wireless devices -> Exception 1 (Illegal Function) returned
• Function Code 43 OK for wireless devices on PowerTag Link

Thanks !

[Eric_HAVAS · Accepted solution]

@Romain_Polette 

For modbus deviced, PaS is not maintaining any modbus data for a downstream modbus serial device.
In case of modbus serial devices, PaS will be transparent for all the queries from upstream SCADA and it will be routed to the end device and the response we are getting is from end device only. That s why you have noticed that  Function Code 43-14 requests are answered correctly.

For Zigbee devices it is not the same mecanism, as this time the PaS that maintains and manage data and PaS does not answer to modbus device identification requests with function code 43-14

[Guillaume_Evrard]

hello @Eric_HAVAS ,

Why do we have a difference between PAS and PTL as highlihgted by @Romain_Polette  ?

Thanking in advance

[Eric_HAVAS]

Hello @Guillaume_Evrard 
It's only a question of priority and (over)load of backlog.
Due to the list of features still to develop to give more and more value added to the Panel Server gateway,  the function 03 has been considered more priority to develop than the others function codes. (FC 43-14)

(Screenshot of this excel file extracted from the list of modbus functions supported by the Panel  Server  https://www.se.com/ww/en/download/document/DOCA0241EN/  )

[Guillaume_Evrard]

thanks a lot @Eric_HAVAS for your answer.

[Romain_Polette]

Hello !

According to the documentation, this seems possible with PowerTag sensors connected to child Panel Server, because child PTag will be considered as Modbus TCP devices.
Am I right ?

[Breina]

Alright thanks for the info all! For now, I'll use commercial reference to identify devices and I'll be looking forward to using FC 43-14 some time in the future. 🙂

[Romain_Polette]

Hello @Breina , 

FYI, I've sent a request to update Panel Server Modbus documentation to integrate more info about "Wireless Product Identifier" (to align with PowerTag Link documentation).

I have no release planning at this time. Stay tuned.

Regards,