Message Edited by Khalid on 12-19-2006 12:03 PM
Thanks David and Steven,
It does look like an issue with the VxWorks on cRIO-9012. While R&D looks into this, I was wondering if I can perhaps get the IP Address from the OS myself. I am new to VxWorks and don't know how to go about making some VxWorks API calls from my RT VI. I know VxWorks uses .OUT extensions (instead of the .DLL), but that's about it. Contrasting this with PharLap (from cFP and older cRIO controllers), I could still call a sub-set of Win32 API calls.
I found the VxWorks' API on the Net, but didn't find anything on how to go about making the calls themselves, as in what .OUT files have which functions, etc. I am sure NI's functions are doing some of this. Would appreciate _any_ input on this.
Thanks much in advance!
Message Edited by Bassett Hound on 12-27-2006 08:52 AM
Thanks for the response. I realize VxWorks doesn't support the Win32 API. I was actually wondering about the VxWorks' API itself. Being an OS, I am sure VxWorks exposes some system-level API for the apps running on it. And am pretty sure LVRT is calling this API for some of its functionality (and to get the IP address??). So I am looking for ways to call this VxWorks' system API from a real-time VI.