Skip to content

NSTART Not Implemented #404

@janvinas

Description

@janvinas

Hello,

I've noticed that the NSTART parameter has no effect, and CON requests always wait for the previous request ACK to arrive before being transmitted. Setting Message.transport_tuning.NSTART to a different value than 1 does not change this behavior.

Are there plans to implement this feature in the library?

Thanks.

Metadata

Metadata

Assignees

Labels

bugSomething doesn't work as it should (even though code or docs indicate that)enhancementtransports

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions