G1888A Headspace Communication with MassHunter Acquisition

Hey Paul,

Everything is up and working great. Thanks again. We're just having one last issue that I'm not getting any replies on so I was wondering if you could help. We just added a G1888A Headspace sampler to the system but after connecting the LAN, configuring the IP address, and installing the integrated headspace software for Masshunter (g5350-60002), it doesn't seem to show up in the instrument configuration tool (headspace is greyed out). I've tried restarting everything, uninstalling the instrument and reinstalling it, ensuring all firmware is up to date, etc. but nothing seems to work. I can connect to the instrument fine using the firmware update utility, and the LEDs on the back are showing the correct two green one Amber, but it just doesn't seem to want to connect to masshunter configuration. What am I doing wrong here? I know masshunter wasn't recording any data from a run until we added a remote rs232 cable between the gc and ms and the manual talks about a splitter to connect all 3 together but it also says that it should be able to work using just LAN. Is it just a cabling issue?

Any help would be appreciated. Thanks!

Parents
  • Is green LED 1 - top right - blinking?  That says that the channel is connected over the network. Solid means channel 1 is idle.

    Config looks like this?  I do not have the HS add-on software loaded.

    Is there any way for you to try RS-232 from the computer to the G1888A?

    The remote start cables may be 9 pins, but they are not RS232.  The Remote splitter cable is G1530-61200 and you'll need the remote cable from the G1888 to that -- G1530-60930 Remote start/stop cable.  Those cables are required to get all three parts of the system to start a run at the same time....once they are all configured and talking properly.

    Y cable G1530-61200

    .

    .

    .

  • Okay, so the configuration looks identical to yours with the headspace greyed out. We have those cables and all 3 remote ports are connected together. I just changed the IP address for the headspace to 192.168.254.14 from .13 just for the heck of it and no change. The light on the top is solid unless I connect to the firmware update utility then I'm getting a blinking top green on the HS and all 4 lights on the router are blinking together but still no luck with the configuration. For reference the firmware is v1.10

    I misspoke about rs232 I meant remote but yes, I can try rs232 to usb anyway. Let me give that a shot now. 

  • Alright so I tried changing to RS232, activated it in the headspace advanced settings, got it connected to the pc and made sure the bit rate and other settings were correct but no change. Swapped back to LAN, reset and ran a firmware update just in case. Here's a picture of our config screen and the revision history log: And just to make things more confusing, in Chemstation configuration, the G1888 shows up and configures no problem and works fine in chemstation itself. However even after adding it and configuring it there, masshunter still refuses to recognize it. I've looked through the software bulletins but don't see anything that's helpful but according to the people in the lab with an identical setup, they said the Agilent tech had the same exact issue with there's and it took him several days to figure it out. So apparently it's not a one off

Reply
  • Alright so I tried changing to RS232, activated it in the headspace advanced settings, got it connected to the pc and made sure the bit rate and other settings were correct but no change. Swapped back to LAN, reset and ran a firmware update just in case. Here's a picture of our config screen and the revision history log: And just to make things more confusing, in Chemstation configuration, the G1888 shows up and configures no problem and works fine in chemstation itself. However even after adding it and configuring it there, masshunter still refuses to recognize it. I've looked through the software bulletins but don't see anything that's helpful but according to the people in the lab with an identical setup, they said the Agilent tech had the same exact issue with there's and it took him several days to figure it out. So apparently it's not a one off

Children
Was this helpful?