compile RT EXE

[MrJackHamilton]

I agree with the "Localhost" being a problem. This typically, might try to resolve all of the Ethernet adapters on the SOM, and if one is not configured, you will get an error and the property node may return nothing.

I recommend setting one of the SOM ethernet adpaters to a hard IP, and then use this IP.

You should also consider dropping in a UDP broadcast as output of health and status of the SOM RT system to a remote laptop via ethernet. Just broadcast the RT time, the CPU usage, iteration counters, etc. to see if loops are running.

The UDP example can basically, drop in. But again; be ware to set the UDP output to the correct ethernat adapater by it's IP address.

Regards

Jack Hamilton

[KHartley]

Hey Spex and Jack,

All of our linux targets have a built in loopback ip address that is always enabled. So using localhost if nothing else should resolve with 127.0.0.1.

Let me grab a som.

[KHartley]

I just tested it on a SOM in 14.5 and a built executable appears to work just fine I have one led toggling on the devkit to show the app is running and one tied to the error line of the init vi. I don't see any errors and the app started so its not a broken feature. I've also disconnected all ethernet and the usb device port.

Nico,

Have you been able to get the init vi working in a built application?