Patrick Grawehr

@soundanalogous Yes, I am aware of the original intent of this proposal. I'm just trying to get a picture on whether that's really bringing us forward the way it's currently...

You mean because servo is abusing "top level" commands? I haven't worked with this component yet, so I wasn't aware of this indeed not optimal approach. So yes, I agree...

I'm not sure I understand your requirement. Do you need a higher resolution of the duty cycle (e.g 16 bits) or a way to set the frequency (for which there's...

> Yap, I need a high-resolution duty cycle and the current protocol does not directly support it. That's not exactly correct. To use more than 14 bits for the PWM...

`analogWrite()` takes an int (16 bit) as the second argument, so this should actually work. Have you created a test sketch that uses `analogWriteResolution` and `analogWrite` to test how this...

It really appears that this is not properly defined, and at least in ConfigurableFirmata I can't currently see that changing the reporting parameters forces sending out the current state. I...

Let's clarify this: Firmata always sends a `DIGITAL_MESSAGE` (0x90) as a reply to a `REPORT_DIGITAL_PIN` (0xD0) message. That means when you enable/disable reporting for a specific pin, you always get...

> > Any pin that is set to output is always reported as 0 in the `REPORT_DIGITAL_PIN` message. > > Do you mean `digital I/O message` (0x90) here? Where is...

You are right, this is a potential race condition. I can't think of a good solution for this problem either. You'll probably have to wait a short time whether there's...

> Perhaps you can define an extra message type for the response of the "enable report" request. I thought about this, but it's difficult, because these are very basic messages...