I’m currently experiencing a Key Error when trying to load a method on a VANTAGE system. The strange part is that the issue occurs even when the method is completely empty. The exact same method loads without any problems on a different VANTAGE unit.
Here’s what I’ve tried so far:
Different laptops (all with Venus installed)
Different USB cables
Confirmed that the VANTAGE system is visible and accessible via the System Configuration Editor
The Arm Configuration loads correctly
However, when I try to load the method, I get the following error in the log:
2025-07-02 11:23:25.604 Venus software version: 6.0.2.3426
2025-07-02 11:23:25.635 SYSTEM : Analyze method - start; Method file ...lidtest.hsl
2025-07-02 11:23:26.391 Microlab® STAR / VANTAGE : Communication - progress; Connection to instrument is created.
2025-07-02 11:23:28.007 Microlab® STAR / VANTAGE : Main - error; An error occurred while running Vector. The error description is: CHxPars::Item could not find a value for key -534183934. (0x4 - 0x2 - 0xa)
2025-07-02 11:23:28.011 SYSTEM : Analyze method - complete with error;
Has anyone encountered this error before or knows what might be causing it?
Any advice would be greatly appreciated.
That specific error indicates that during the initial connection between run control and the VANTAGE system, that run control either didn’t receive an expected response from a query sent to a component of the system either at all or within an expected amount of time, or received a response in an unexpected format.
Given that this is occurring during run startup, this may indicate a hardware/electronics issue that could require service. If you were able to upload communication traces from the same day the above run trace was generated, I may be able to provide more information regarding the nature of the issue.
VANTAGE communication traces: C:.…Hamilton\Logfiles\VStarTranslator20250702.log C:.…Hamilton\Logfiles\HxTcpIpBdzComm20250702.trc
You can upload the files to the following download URL (password: Hamilton25):
Thanks for providing the comm logs, they gave the necessary context for your system’s issue.
Channel 5 has an issue with a component of it’s Y drive, and is reporting an init failure when the arm’s controller is requesting it’s current position during run connection/onset. I suspect an issue with it’s encoder board, but could also be a cabling issue. In any case, this should be enough information to get a service engineer started.