crio9074 second ethernet port not working in execute, but works in development

[plf]

I am using the 2nd Ethernet port on the cRIO-9074 for monitoring of the system and it works in development mode but when I create an executable and deploy it to run at startup I can not connect to the port.

1st port

ip address 169.254.66.100 subnet mask 255.255.0.0

2nd port 

ip address 169.253.66.1 subnet mask 255.255.0.0

I use the IP address 169.253.66.1 string to net address for the net address into the 'tcp listen.vi'

Anyone seen this before??? 

thanks in advance, i hope. 

pete

[ShishKeBobby]

Hi Pete,

I'd like to hash out what you're communicating with on each end first and describe the way I'd like to go about debugging this.

I imagine port 1 is communicating with some Host PC.  Have we verified that this port is properly sending data to the host?

Port 2 sounds like you're using for some 3rd party hardware monitoring/control.  You also mentioned that it worked properly when running in interactive mode.  What port did you specify for the Listener VI?

How do you verify operation when running in interactive mode?  Is this the same process for your built Real-Time Application?  Do you see any sort of proper behavior from Port 1?

When you don't wire in the Listen.VI net address, do you see different behavior?

Please let me know any other details which may be useful.

Thanks,

[plf]

Thanks for the reply. It turns out I had an un-initialized global variable in my Tx loop that was killing my TCP/IP connection. Once I corrected this I had no further issues. 

Pete

[jgaona]

Hi Pete,

How did you establish a connection between your cRIO-9074 and your third-party device? 

This is my setup:

1st port 

ip address 192.168.0.40 subnet mask 255.255.255.0

2nd port 

ip address 192.168.1.10 subnet mask 255.255.255.0

But I can't seem to establish a connection.

Thanks

[plf]

Yes I did...

Looking at your ip addresses you would need to change the 2nd address to a different subnet... It is documented in a tech doc but off hand I do not remember where but try this...

1st port leave as is
2nd port change to 192.167.1.10
The 167 changes the second port to a different subnet than the 1st which is a requirement for usage. Start by just trying to ping it from a windows command prompt
FYI... I was using subnet masks of 255.255.0.0 just make sure to keep these the same on both ports or it is very difficult to get ni max to connect... Some very odd behavior will occur if you make them different.
Pete