Skip to main content
Thermo Fisher Scientific

Corona Veo SII Empower Connections Guide

Issue

Installation afor Corona Veo CADs using SII for Empower with 3rd Party LCs.

Environment

  • Waters Empower 3
  • SII for Empower 1.1 or Later
  • Corona Veo CAD
  • 3rd Party LC

Resolution

1.      Software Downloads:

These contain installer and release notes, if any links are blocked, please contact your Thermo support representative.

a.      SII 1.1:

https://knowledge1.thermofisher.com/Software_and_Downloads/Chromatography_and_Mass_Spectrometry_Software/Chromeleon/Chromeleon_7_Software%2C_Drivers_and_Release_Notes/SII_for_Empower_1.1_Software_and_Release_Notes

             i.     HF 111938 for SII 1.1 only:

https://knowledge1.thermofisher.com/Software_and_Downloads/Chromatography_and_Mass_Spectrometry_Software/Chromeleon/Chromeleon_7_Software%2C_Drivers_and_Release_Notes/SII_For_Empower_1.1_Hotfix_111938_and_Release_Notes

b.      SII 1.2:

https://knowledge1.thermofisher.com/Software_and_Downloads/Chromatography_and_Mass_Spectrometry_Software/Chromeleon/Chromeleon_7_Software%2C_Drivers_and_Release_Notes/SII_for_Empower_1.2_Software%2C_Operator_Guides_and_Release_Notes

c. SII 1.3 (latest):

SII for Empower 1.3 Software, List of Supported Instruments and Release Notes

d.      Cleanup procedure (recommended if there are previously installed versions):

Complete Uninstall when upgrading SII for Empower Software

 

2.      Firmware Considerations:

a.      SII 1.1 (Chromeleon 7.2.10 framework):

b.      SII 1.2 (Chromeleon 7.3 framework):

c.  SII 1.3 (Chromeleon 7.3.1 framework): Same as SII 1.2 above.

3.      Connection:

a.      3rd Party Connection Kit 4820.8122:

4820.8122 - Rev 1.0 - Corona Veo RS Third-Party LC Connection - Installation Guide.PDF

USB>COM trigger cable should install automatically by Windows, and will show up in the Device Manager as follows:

COM Port settings should be default, and port # can be changed through Advanced Properties. This COM# should match what is defined in the SII Link, and be set as "Clear to Send" on the SII side.

b.      Recommended USB Cables (with improved shielding):

c.      USB Settings (also recommended to disable Intel C-States in BIOS if applicable to PC):

https://www.dell.com/support/kbdoc/en-us/000060621/what-is-the-c-state

d.      Firewall Settings (for Chromeleon, may not all apply to SII, but worth checking):

4.      CAD troubleshooting

a.      Acquity Connection detailed (haven’t written an Agilent one yet, but the external connection kit details that, using an adapter to go to the Serial port of the Autosampler instead of a signal block):

SII for Empower - Corona CAD Setup for Injection with Waters Acquity LC

b.      Confirm the Firmware can be seen in the Instrument Configuration. If the dropdown is blank, you may need to rebuild the system or repair SII.

c.      Method Editor Deserialization Error (may see this .Net conflict with other Empower Drivers, so order of system build is important):

SII Detector - CAD Instrument Method Editor Deserialized Error

d.      CAD Considerations with 3rd Party Injectors:

                                                    i.     Cannot use any inject immediate… commands with the SII Detector set up, thus only inject… functions/commands.

                                                   ii.     CAD in that setup will not support multiple injections per line in SII 1.1 (1 per sequence line only, or it gets hung up after the 1st injection ).

                                                  iii.     You cannot mix method sets in the same sequence.

iv.    Make sure your Empower sequence Run Time, and SII Run Time (System Tab of Method Editor) match. Be careful as the CAD section of the Method Editor also has a timetable for acquisition, but this must work within the total Run Time. If your Empower and SII Run Times do not match you will have issues after your first injection as synchronization will be off.

e.     If you are getting communication errors with Empower proceed with the following to isolate the issue:

The Detector front panel should always be on the Main Menu before attempting to control it with software.

i.     Confirm there are no errors in the Chromeleon Instrument Configuration, or in the Instrument Panels in Empower that may note an issue with the installation. The CAD should have an Idle state in Empower. The CAD can be run simulated within the configuration if you think the problem might be hardware related.

ii.     If Citrix is being used, run off the local Empower LACe client to confirm the issue is not Citrix-related.

iii.    Check your instrument method is correct, and will properly set up.

iv.    Check your sequence is properly configured, and that it is not causing the communication failures.

v.    If failure occurs upon injection, confirm external autosampler cabling and assigned COM port is correct. The bare ends of the trigger cable can be touched together to simulate a scan start, and confirm the issue is not with the cable (and could be an issue with the autosampler connection or port). 

vi.    Clear and rebuild the system in Chromeleon. To do so, first take the Empower system offline, then delete it. Remove all old SII components from the LACe Node properties > instruments tab. In the Chromeleon Instrument Configuration, delete and rebuild the system anew. Reboot LACe and instruments, then reconfigure the system in Empower being sure to add the newly created SII_Detector object in the appropriate order as noted above. Bring the system online, and retry Instrument Panel Connection > Method Setup > Submit Sequence.

f.     It is still possible to trigger the CAD directly from the Autosampler (analog trigger). Is this case the USB adapter is not used, and the red (+), black (-), and green (GND)  trigger cable (on the PC side) is connected directly to ports 10/12/12 on the I/O Terminal B on the back of the CAD (see below for cable pin assignments). EmpowerLink will still require a COM port to be set, but this will be bypassed when injecting.

 

 

  • Was this article helpful?