Ed,
We are using NI Real-Time Phar Lap ETS 13.1
I wrote a handcrafted function in C that doesn't exist in LabVIEW and compiled it into a DLL using Visual Studios 2010 (execution was too slow when I attempted to write the function in LabVIEW). I ran the DLL through the 2015 checker for RT deployment, and there were no Bad functions indicated only several Stubbed functions. When I attempted to actually deploy and use the DLL, however, it still kept failing most probably due to said Stubbed functions. After spending several months trying to solve that, I decided to simply leave it on a Windows OS comp where I knew it did work and transmit the data back and forth. Not an ideal situation, perhaps, but it let me get on with my work at least. When this communication issue came up, I decided to revisit trying to put the DLL onto the RTOS to by-pass the problem altogether. However, even after upgrading to LabVIEW 2016, the DLL still failed.
I hadn't really considered attempting a direct connection mainly because we will need the router to connect the Host computer to our RT Target, and we do not currently posses an additional Ethernet card that we could add to the RT Target to allow for a second connection.
Regards
