You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently working on BACpypes3. I need the UDPCommunication module for socket communication, which uses the UDPDirector and UDPActor. Please guide me on which classes I need to refer to in BACpypes3.
The text was updated successfully, but these errors were encountered:
Start with the samples in the link layer folder. While UDP is a session-less peer-to-peer protocol, they are named things like "client" and "server" to make it easier to envision things like "initiate a service" and "respond to a request for a service". Note that UDPDirector and UDPActor are terms from "legacy" BACpypes because at the time I thought that both the UDP and TCP portions of a stack should have the same design, not just the same request/indication/response/confirmation API.
Those samples use the lowest kind of PDU, you can of course make your own for your protocol and inherit from the generic Client and Server.
Hi Sir @JoelBender ,
I am currently working on BACpypes3. I need the UDPCommunication module for socket communication, which uses the UDPDirector and UDPActor. Please guide me on which classes I need to refer to in BACpypes3.
The text was updated successfully, but these errors were encountered: