I have two different custom devices which use the system definition API, an embedded data logger and an alarm logger, which I built to meet my own needs and requirements
The data logger I had working in a previous project in VeriStand 2018 however I have since tried to update the logger for a new project in Veristand 2019 and it is causing the target to crash upon initialisation of the custom device and I get a network connection timeout error
I have had both custom devices working when deployed to a windows target and I am using an RT PC with a PharLap ETS OS, which I have updated with the VeriStand 2019 engine from 2018, I am also getting the same error deploying to a fresh 2019 install
I have 2012 installed on my PC and when choosing the system definition api I choose 7.0.0.0 over 2012.0.1.0, of note is that 2018's version of the api was 2018.0.0.0 so I gather that I am assuming correctly 7.0.0.0 is the version that ships with 2019 as it is installed with it. Between the 2018 and 2019 RT PC's there is no difference in the software installed on the target.
Im thinking this issue is indicative of another issue I am having with custom devices which involves getting vi libraries to work on my target, for example using the modbus library, I have seen use of packed libraries which I think is the way to get this working but I am having trouble with their implementation with custom devices. If someone could offer me some guidance with this and my above issue it would be very much appreciated, thanks