05-27-2020 03:51 AM - edited 05-27-2020 03:52 AM
Hi,
I'm a little bit in a pickle here. We started using Systemlink with teststand, everthing worked fine until today when a pop up showed up in the middle of a test.
I can't make head or tail of it, if someone can help me it will be great.
I am sorry for the screen shot quality, i'll try to edit the post if the problem occurs again.
Solved! Go to Solution.
05-27-2020 08:09 AM
We fixed several bugs in the SystemLink TestStand plugin in SystemLink 2020 R1 (20.0). I would highly suggest you upgrade your server and client to 2020 R1 if you haven't already.
05-28-2020 01:42 AM - edited 05-28-2020 01:48 AM
Is there a way to update the client remotly (knowing that the computer doesn't have acces to internet), since there's no way i can stop the production for that.
Is the server 2020 R1 compatible with the 19.6 client?
05-28-2020 07:57 AM
Yes, the server is backwards compatible and can support older clients. It is not forward compatible, so you need to upgrade the server before you can upgrade any of the clients.
In addition, you can update the targets remotely with SystemLink. After upgrade the server you can replicate the 20202 R1 client feed to your server using the Package Repository application.
Then using the SL Systems Manager application you can add the feed from your Package Repository to the targets and that should enable the SystemLink Client to show up in the list of available upgrades. Note, you may need to update the NI Package Manager first if it is out of date using similar steps.
06-03-2020 09:34 AM
By the way JoshuaP, do you know the behavior during the client's update? On some computers we have a test running each minute, so we cannot stop the production for updates, or at least it's complicated to manage.
If we're making a client's update, are the test results correctly saved during that time?
06-03-2020 09:36 AM
and for the problem explained by sklod, we were able to reproduce it just by disconnecting the ethernet cable. Seems it's coming from a tag request in TS, not from the SL api in TS.