Andrew Madsen
Andrew Madsen
If you're interested in implementing this and submitting a pull request, feel free to ask questions. I think the basic approach is to "swap" the initializers in `InternalSerialPort` and `SerialPort`...
Nice! The request/response API is entirely built on top of "high level" ORSSerialPort send/receive functionality. The implementation of the request response API shouldn't depend on the specifics of the low...
Just a note to say that I still haven't had a chance to look at this, but haven't forgotten, and will get to it when I can.
Postponing this at least until after 3.0 for now.
Thanks for this! Give me a bit to review it, and I'll let you know if I have any feedback.
Yes. Most if not all USB to serial adapters have TTL output levels anyway, so what you’re describing is commonplace. > On Nov 18, 2019, at 11:22 PM, pwjpj52 wrote:...
I'm not sure what might be going on. I've never seen the cu path fail to open while tty works (it's usually the other way around...). For device discovery, ORSSerialPort...
I'm assuming that's received data you're logging. The nulls might be due to data being received that can't be converted to a printable string. I can't tell for sure without...
Sure, a PR would be most welcome. It needs to not break the existing API, though. > On Jul 27, 2022, at 1:03 PM, Alex Frankiv ***@***.***> wrote: > >...
Yeah, I think a completion handler is probably a good idea.