# Msgproto.py HEX support

**URL:** <https://klipper.discourse.group/t/msgproto-py-hex-support/25087>\
**Category:** Developers\
**Created:** [October 24, 2025, 8:51am UTC](https://klipper.discourse.group/t/msgproto-py-hex-support/25087 "2025-10-24T08:51:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Delsian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/delsian/32/20830_2.png) [@Delsian](https://klipper.discourse.group/u/Delsian)\
**Post date:** [October 24, 2025, 8:51am UTC](https://klipper.discourse.group/t/msgproto-py-hex-support/25087/1 "2025-10-24T08:51:30Z")

</div>

Actual formats for ‘output()’ values is:

```auto
MessageTypes = {
    '%u': PT_uint32(), '%i': PT_int32(),
    '%hu': PT_uint16(), '%hi': PT_int16(),
    '%c': PT_byte(),
    '%s': PT_string(), '%.*s': PT_progmem_buffer(), '%*s': PT_buffer(),
}

```

Sometimes, for easy readability better to have %x format.  
Is it ok to implement this improvement? Or is it not necessary?

---

<div class="post-metadata">

**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\
**Post date:** [October 24, 2025, 10:05pm UTC](https://klipper.discourse.group/t/msgproto-py-hex-support/25087/2 "2025-10-24T22:05:55Z")

</div>

It’s fine to implement that if you wish. However, it may require more changes than just altering `MessageTypes`.

Cheers,  
-Kevin