# MessageID & CAN Identifier

**URL:** <https://forum.opencyphal.org/t/messageid-can-identifier/2049>\
**Category:** Applications & Usage\
**Created:** [December 12, 2023, 8:46am UTC](https://forum.opencyphal.org/t/messageid-can-identifier/2049 "2023-12-12T08:46:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![circletrain](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/circletrain/32/1525_2.png) [@circletrain](https://forum.opencyphal.org/u/circletrain)\
**Post date:** [December 12, 2023, 8:46am UTC](https://forum.opencyphal.org/t/messageid-can-identifier/2049/1 "2023-12-12T08:46:48Z")

</div>

Hello, I’m a beginner to study about the Cyphal driver of PX4. I have a few questions, so I hope you can solve my questions.

1. Is it correct that the data can be received only when the CAN identifier (like 0x01) provided by BMS and the UVCAN message ID match? I don’t know if it’s accurate because it’s information obtained using only chatpt.
2. If you need to match, please let me know how you define the UAVCAN message ID. (Is 8165.NodeIDAllocationData.2.0.uavcan 8165 the message ID?)
3. If the content number 2 is correct, is there a way to handle the message ID separately for uavcan messages without a message ID written in the name?

I’m immature because I lack an accurate concept, so I think it would be helpful if you could give me a detailed answer.

---

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [December 12, 2023, 9:29am UTC](https://forum.opencyphal.org/t/messageid-can-identifier/2049/2 "2023-12-12T09:29:57Z")

</div>

1. No, the CAN ID cannot match because it is unique per node and may also change with priority. The subject-ID (aka topic-ID) has to match. CAN ID incorporates the subject-ID as follows:

 ![image](https://forum.opencyphal.org/uploads/default/original/2X/5/58d8993abcd53a061c8c49bd6917a23d63e5f924.png)

1. It is assigned when the system is configured via configuration registers. See the documentation for the data type named `uavcan.register.Access`.

2. Yes, by changing the configuration registers.

You may find the demos relevant: [GitHub - OpenCyphal-Garage/demos: Demo applications and reference implementations · GitHub](https://github.com/OpenCyphal-Garage/demos)

---

<div class="post-metadata">

**Author:** ![circletrain](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/circletrain/32/1525_2.png) [@circletrain](https://forum.opencyphal.org/u/circletrain)\
**Post date:** [January 5, 2024, 1:19am UTC](https://forum.opencyphal.org/t/messageid-can-identifier/2049/4 "2024-01-05T01:19:39Z")

</div>

So, according to you, the values of bits located in the Subject ID from the CAN ID of BMS are Subject-ID? (Here, CAN ID means a message in the existing “CAN” format, not a message in Cyphal format.)Then, when subscribing to the CAN ID, can I designate the bits located in the Subject-ID as the Port-ID?

---

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [January 5, 2024, 9:14am UTC](https://forum.opencyphal.org/t/messageid-can-identifier/2049/5 "2024-01-05T09:14:29Z")

</div>

yes
