I had to install Venus on a brand new computer due to the previous computer repeatedly crashing. I am not able to get the new computer to connect to my Vantage.
I was wondering if anyone has seen this error before (ComLinkTcpConnectionFailedTimedOut) and has any insight? It pops up when I am trying to run a method. It seems to be from being unable to connect to my Vantage’s cabinet.
I am able to connect to the Vantage via the system config editor and via the Venus 6 software and I can initialize the instrument. It can also pass daily maintenance. I am able to run a method if I remove the cabinet from the system deck. The XRP Service software is able to connect to the instrument at the set IP 192.168.1.1 and I have also set manual IPv4 address and mask (192.168.1.10 // 255.255.255.0) within the computer’s Ethernet settings. The system config editor cannot find the cabinet - “unable to start the discovery server” - so I set it to a static IP of 192.168.1.2:2000.
Let me know if there’s anything else I could try to get it working!!
Unless the network configuration for your VANTAGEs powersocket (cabinet controller) was altered in firmware, then you have the correct static IP and port set in the CustomCabinet section of system configuration editor, as well as correct PC network adapter settings.
At this point I would confirm physical network and power connections are intact. If you remove the kickboard panel at the very bottom of the front of the cabinet, you’ll see what’s called a power socket drawer on one end of the system. Can you please take a photo and post the image here? It should look like this:
Thanks for your reply! This Vantage’s power and ethernet connection are on the side of the instrument. The network port through which the Vantage is connecting to the computer only has a green light, not a blinking orange. This is also true for the light of the corresponding network port on the computer itself.
The connections and ports in your image are for the gateway processor, which resides in an electronics compartment under the left most deck panels. This is the main entry point to the VANTAGE network, and is the primary processor which controls all pipettor components (arm, lights, loading tray, front cover lock, IDL etc).
For VANTAGE configurations extended to include additional components (custom cabinet with magnetic locks, track gripper, entry exit module, logistics cabinet), there is an additional separate processor unit tethered to the gateway called a power socket (shown in the original image from my first reply). This is a separate network endpoint within the VANTAGE system with its own IP:port address unique from the gateway but within the same subnet.
When you add a custom cabinet device to a method’s decklayout, during run analysis (onset of run when compiler checks and system device connections are made) run control will attempt to connect to a powersocket via the configured network settings (almost always 192.168.1.2:2000).
If the connections to the power socket are not intact, or the network settings are no longer correct, then you will experience the error you have reported here.
If you dont mind, check behind the little kickboard on the bottom front of the system, or please provide an image of the entire system and I can point you in the right direction.
Sorry for the confusion, I didn’t attach a picture from behind the kickboard because when I remove the board, nothing is there.
Our service engineer was last minute able to stop by and he pointed out that the cabinet we have with this instrument is literally just being used as a table, which I didn’t know was possible (or why it would even be desired…) and it is unlike the other Vantage/cabinet configurations we have onsite. So that would explain why there isn’t a power socket underneath the cabinet or anything for the system config to find to connect to. Thanks for taking the time to explain everything in detail, though, that was very helpful!
I am bringing this thread up again since it’s relevant to our problem We too had to move to another computer for our Vantage, but the new computer isn’t connecting to the Vantage, even though the cables weren’t rearranged at all. I installed Instinct V (which is what our Vantage runs on), but that program is not recognizing the instrument. The computer itself verifies that the instrument is connecting, but the software doesn’t seem to recognize it. Not even the XRP service software can connect to it.
Installation of Instinct V went fine as I followed the operator/programmer manuals, but perhaps I am missing something else? Any additional advice could be provided?
When you changed PCs, did you update the network settings of the adapter (ethernet port) the VANTAGE is now connected to? Unless your VANTAGE is running a non-default network communication configuration, then its network adapter will be set to a static IP of 192.168.1.1 (INSTINCT V manages port assignment).
You’ll need to identify the ethernet port on the PC connected to the VANTAGE and confirm that its IPv4 settings are configured for static IP on 192.168.1.### where ### is any number between 2 and 255 which not already used by the local network.
Just a word of caution - INSTINCT V ceased development and active maintenance a few years ago. The vast majority (~99%) of the VANTAGE installation base is running on either VoV or VENUS 6 and you’ll find much less collective INSTINCT knowledge and experience from other users on this site. If you opt to convert your installation to VENUS, you will have an easier time getting resources and support.
Thank you for the quick response, as we were able to get it recognized on Instinct V now Unfortunately, there is another unexpected problem we ran into now. As we try connecting to the instrument, it could not setup connection to Module A Controller (error during listening on network interface), which is weird cause this didn’t happen before… Is there another IP/Ethernet cable we have to manually configure for that as well?
Edit: I installed VoV, yet the software is not recognizing the instrument either. I fear it has to do with the Module A connection we are experiencing on Instinct V
We too had to move to another computer for our Vantage, but the new computer isn’t connecting to the Vantage, even though the cables weren’t rearranged at all. I installed Instinct V (which is what our Vantage runs on), but that program is not recognizing the instrument. The computer itself verifies that the instrument is connecting, but the software doesn’t seem to recognize it. Not even the XRP service software can connect to it.
Unfortunately, there is another unexpected problem we ran into now. As we try connecting to the instrument, it could not setup connection to Module A Controller (error during listening on network interface), which is weird cause this didn’t happen before… Is there another IP/Ethernet cable we have to manually configure for that as well?