communication problem with the QQQ 6470

We have the 6470 spectrometer that was turned off to do electrical work in the building. When we turned it back on, the communication is not taking place between the QQQ and the software. we restarted the system but the problem still persists

  • We don't understand why it doesn't ping any of these addresses. We simply turned off the LCMSMS following the procedure

  • Check PC settings against the guide here. The beep and valve switch suggest the MS is on and firmware loaded.
    It sounds like PC cannot ping itself (assuming it is 192.168.254.10) 
    The guide will show how to check and set this IP address. 

    (+) PC system requirements for MassHunter Version 10 - Mass Spectrometry Software User Forum - Mass Spectrometry Software - Agilent Community

    T
    ry also by pass network switch connect direct to and ping only LC  same with MS.
    See also what LEDS are on on the switch.
    Try other LAN cables

  • Hi Ross,

    Thank you for your support

    We have carried out all the recommendations you have recommended but without results. Here are the results of the pinging as well as the state of the spectrometer

  • At least you now have PC capable of communicating so can focus on MS. This is getting close to needing to log a call with local Support team and getting engineer to investigate.
    If possible, connect PC to MS directly bypass switch. Try different LAN cables for this. They can go bad without warning although it is not common it happens.
    The rapidly flashing status indicator is not right.

    That there is LED on the6470 LAN port is some indication it is not dead and connected to network. The orange on the switch port 7 should be green.
    The beep on start up shows some power to the instrument smart card but does not guarantee it is fully functioning. There should be 2 valve switches one almost immediately or just seconds after power up one a little later. The Later one indicates the firmware has started.


    If you are happy to remove the front, top and side covers, You can check the LEDS on the Turbo power supplies. This is just a visual check, There is no other work you can do here yourself and I advise against opening any more than this to look at the LEDs mentioned below.

    They look like this (these are off all 3 on when green)

    On turbo 1 at the front all 3 should be green once the turbo is running (they can be dusty and appear off!).
    On the one on right hand side, if it is not on then it is likely the firm ware has not started. And the issue is on the smartcard.
    At this stage even if they are on issue is likely at smartcard if direct connection cannot ping too.

    At this stage log a call and provide all the troubleshooting you have done here.

  • Hi,

    Thank you for your support
    All the recommended steps mentioned have been carried out (cable change .....) but the QQQ does not respond.
    Following this incident, therefore, WE MUST never turn off the 6470?

    Regards

  • No pinging and switching valve is not working.

    No booting of smart card

  • Check the PC's ethernet port. Try different LAN port on PC. If it is not exist add a LAN board to PC and give this ip adress for new LAN. 192. 168.254.1 

    Also you can connect a VGA monitor to the side of the 6470. then restart the MS and see what happens in monitor. 

  • Hi,

    We changed the smart card for 6470 and communication was restored with the QQQ. Except that when we tried to turn it on, the source temperature does not reach 400°C, it stops at 99°C. What must we do ?

    Thanks

  • Hello,
    If the QQQ is recognizing the source correctly, and a Hard reset of the QQQ has been done. Then there is a good chance the Sheath Gas heater is open. You will need to log a Service Call thru the 1-800-227-9770 Option 3,2
    Best Regards,
    Rick McFadden
    Online Technical Support Team
     
     
  • Hi,

    We have an error message displayed as shown in the attached photo. What should be done to unlock the system. We turned off, restart the PC but the problem still persists

    Thanks

Was this helpful?