I am curious on how people use a round trip to get a response from a module versus a request and reply or if they create a separate request and broadcast. I have different solutions, just looking for some ideas.
EX. I want to have a request get me the value of X (a string) and the reply should be (X) is equal to value (float). Think querying a register.
So if I did a request and reply, the request is a String, and the reply payload would be a String and a Float.
However, I don't want to have the lockup so I am making a round trip. Variables: String and Float. But if I do this all the controls are "required" for the request, even though the one is really only valid for the reply.
So what is the suggested action at this point.
- Modify the scripted VI to not make the float required or even replace it with a constant.
- I am hesitant to change the scripted code
- Leave the request as is and the developer just needs to know they can put a constant there but it is un-used
- Not great
- Don't use the Round Trip and create 2 separate events.
- Fine, I just originally liked the round trip idea, it is the data that posed the issue.
- Potential feature request: Make a round trip with a reply "payload" that may be different than the request. Not sure how to expose this so it may just be best to require creating 2 events.