03-09-2010 10:48 AM
03-09-2010 11:07 AM - edited 03-09-2010 11:08 AM
This is a little outside my field of expertise, but i'll give it a shot.
After looking here, it looks like you can assign each ethernet port its own IP address through MAX.
Then in your code, you can use the IP address to discriminate between the ethernet ports.
Hope that helps a little bit.
03-09-2010 11:18 AM
03-10-2010 09:40 AM
As it turns out, we're essentially going to do what you suggested (Dennis) - "use a single NIC and just have a different IP on each UUT". Attached is a snippet (VI) that shows the widgets I referred to. I'm not sure if either of these ideas is any easier than the other, but the way I see it, I have two choices - (1) create multiple instances of my RCTx tool that has its dedicated local host TCP port (for messaging to the client) and a dedicated webBrowser for tied to a specific IP address to display the traffic between the radio and the RCTx, OR (2) I have one RCTx app that receives TCP messages (with an IP addr embedded) then I would route that message to the proper webBrowser. I'm thinking that option 2 would require me to maintain an array of webBrowsers, but then the other (50 or so controls/indicators) would have to get tied in somehow. I was thinking I could incorporate some level of LabVIEW Object-Oriented code such that for each radio, I would create a class instance (object) that would encapsulate all the controls and messaging capabilities. I'm just not sure which way to go.