AN36 charcteristics clarification

RE: AN36 charcteristics clarification

michurin — Wed, 20 Nov 2013 15:35:51 GMT

"... it makes more sense to use a uint8_t directly" Disagree. If the characteristic is commonly known/used that it has been already defined/templated. If not than it is proprietary anyways and as you've said "For your own applications, you can define this in any way you want". Using customized type via shared .h file is as a good common practice.
I did also suggest a compromise:
typedef uint8_t led_state_t; which do not change anything but do indeed make code nicer and which is more important readable and understandable. Thank you.

RE: AN36 charcteristics clarification

Ole Morten — Wed, 20 Nov 2013 14:30:49 GMT

This would most definitely be possible, and I agree that it makes the code look nicer.

However, remember that the value actually used must be the same as the peer device uses. What you're actually defining here is what value the peer device have to send over the air to set the LED, and hence I'd say that it makes more sense to use a uint8_t directly instead of an enum or a bool, since that makes it explicit what size value you should send from the Central device to this characteristic.

For your own applications, you can define this in any way you want.