# Cube ID serial **URL:** \ **Category:** ADS-B\ **Created:** [21 May 2023 03:10 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152 "2023-05-21T03:10:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hamishwillee](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/hamishwillee/32/6687_2.png) [@hamishwillee](https://discuss.cubepilot.org/u/hamishwillee)\ **Post date:** [21 May 2023 03:10 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152/1 "2023-05-21T03:10:02Z")
Not exactly “ADS-B”, but best of the options. I’m thinking of testing [Cube ID](https://docs.cubepilot.org/user-guides/cube-id/cube-id#updating) on PX4. Is this known to work? My assumption is that this is a serial MAVLink connection and the autopilot just needs to emit [OPEN\_DRONE\_ID\_BASIC\_ID](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_BASIC_ID) and [OPEN\_DRONE\_ID\_LOCATION](https://mavlink.io/en/messages/common.html#OPEN_DRONE_ID_LOCATION) on the channel. Does the Cube ID have a standard component ID or will it accept broadcast ID on the serial channel? What component id does it broadcast with? Can you set the system ID/component ID (this would be necessarily in some architectures). ---
**Author:** ![Michael\_Oborne](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/michael_oborne/32/13_2.png) [@Michael\_Oborne](https://discuss.cubepilot.org/u/Michael_Oborne)\ **Post date:** [22 May 2023 05:14 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152/2 "2023-05-22T05:14:17Z")
@sidbh ---
**Author:** ![sidbh](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/sidbh/32/7358_2.png) [@sidbh](https://discuss.cubepilot.org/u/sidbh)\ **Post date:** [24 May 2023 09:06 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152/3 "2023-05-24T09:06:40Z")
CubeID should accept OPEN DRONE ID messages originating from any system as long as they conform with definition @ [GitHub - ArduPilot/mavlink: MAVLink micro air vehicle marshalling / communication library](https://github.com/ardupilot/mavlink) . CubeID publishes its own messages with SYS ID 1 and Component ID MAV\_COMP\_ID\_ODID\_TXRX\_1 ---
**Author:** ![hamishwillee](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/hamishwillee/32/6687_2.png) [@hamishwillee](https://discuss.cubepilot.org/u/hamishwillee)\ **Post date:** [24 May 2023 23:49 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152/4 "2023-05-24T23:49:45Z")
Thanks @sidbh , so some more confirmations: - Is this your own proprietary firmware? - Can the system and component ID be modified/configured. - Does CubeID receive incoming data and forward to the GCS/autopilot, or is it one-way - publishing location and ID from the flight stack? - Does the CubeID take its id from the messages and update the value if the messages change. I ask because the arduremote firmware (or whatever it is called) can be configured with a value or will otherwise take the first value it gets. FYI @JulianOes tells me he plans to do some work with you on this, so I hope to get answers to some of these eventually from him. At this point just getting my head around what “most” implementations do. ---
**Author:** ![sidbh](https://discuss.cubepilot.org/user_avatar/discuss.cubepilot.org/sidbh/32/7358_2.png) [@sidbh](https://discuss.cubepilot.org/u/sidbh)\ **Post date:** [25 May 2023 10:01 UTC](https://discuss.cubepilot.org/t/cube-id-serial/11152/5 "2023-05-25T10:01:46Z")
CubeID only acts a transmitter of the data, it doesn’t directly communicate with GCS. Only with Autopilot. It takes in the ID coming from autopilot. I am adding mechanism to Ardupilot, to set a one time programmable Serial ID.