Unable to connect to ECU using XCP on CAN with ECUMC Toolkit

[jrfarre]

I am getting error code -301021 when attempting to connect to my controller via XCP on CAN using "XCP or CCP Master" custom device. I have verified the .dll is named the same as the file referenced in the database. Both the database and the checksum are in the same directory on the windows PC that is running VeriStand. I have also compiled checksum as a shared object file and placed directly on the Linux target with an edited database that references a .so checksum instead of a .dll in usr/local/lib. I also set up a remote seed and key server using "Remote Seedkey.lvproj" in example finder and cannot seem to unlock my ecu using a tried and true checksum. 

Does anyone have screenshots of how they configured this custom device in VeriStand? It would be nice to compare to something that is working. I would like to avoid using remote seed and key and anything LabVIEW, is this possible?

I am using VeriStand 2023 Q2.

[ZYOng]

I am not sure if you can configure ECUMC to call an SO file directly. At least I have never seen anyone do that.

Please see the attached build exe for the remote seedkey server. I only have 64-bit LabVIEW so make sure your seedkey dll is built for 64-bit. You can use the ProcessCmd.exe to verify if the remote seedkey server can load your DLL.

Run the remote seedkey server before you deploy your VeriStand project. Don't forget to enable it in the custom device.

If it does not work, check Enable XCP/CCP Logging. Retrieve and upload the log file here. I can help to analyze the trace log.

You can refer to Troubleshooting XCP or CCP Master Custom Device in VeriStand for some helpful information.

[jrfarre]

I was unable to use the server you sent because the DLL I had ended up being 32-bit. I then explored the example provided in LabVIEW with a co-worker and found the example did not work because the default IP address that would populate for "Server IP Address" was not the network port the PXI is connected to. So we copied the example and edited the VI to add a Control to set the IP address, then routed that IP address into the TCP Port Listener. Once that was done, I am able to achieve a connection status of 1 without an error code.