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.
Solved! Go to Solution.
I would make two independent events, the request with the string and the broadcast with the DBL. These two events wouldn't be 'officially' related in any way, so I don't see any benefit in having the Create Event dialog link them by letting you create two different arguments when making the round trip.
I've had this use case a few times, and it didn't feel weird to me to create two different events. In fact, now that I think about it, I can't remember the last time I created an official round trip event. I always use Request and Wait for Reply, or just unrelated request and broadcast events.
That is kind of what I thought, it is just nice to get feedback that I am on the correct path.