duplicate terminals

[labviewette]

Hello all,

I'm new to the LabVIEW Communication Design Suite but not to LabVIEW. I am having a look at sample communication projects (802.11) and noticed that there aren't any local variables anymore but rather duplicate terminals. Could you please explain to me what the difference is and why there are no local variables anymore? Why aren't the wire guidlines applied here in the sense that duplicate terminals are used rather than wiring through structures?

Thanks in advance

[National_Burritos]

Hi labviewette,

Duplicate terminals in LabVIEW Communications are functionaly the same thing as Local Variables in LabVIEW. I.e., you have the same considerations with race conditions, etc. and so you want to be careful when using them.

Can you provide more detail on what you mean by "duplicate terminals are used rather than wiring through structures"? Is this in a specific part of the 802.11 code?

Also, for your information, look for an update to the Application Frameworks in then next week. The 1.1 version will have some nice improvements.

Cheers,

Rahul

[tcap]

Hello labviewette,

I think that you are posting with regards to the Session, Station Active, and Coerced RX Gain [dB]. These are using Duplicate Terminals (Local Variables) to allow for the modification of the RX and TX configurations without stopping the VI.  If these were wired through, the structure would store the value these variables upon the start of the VI. The same behavior could be possible with shift registers and state machines, but this would be a much more complicated architecture. 

If you look through the code, all of the race conditions associated with the duplicate terminals (unless I missed one), have been removed.

In general, this was a design decision by the R&D team.

Regards,