AnsweredAssumed Answered

Triggering Problem between TLS and Powermeter with 8164B

Question asked by gregm on Apr 8, 2011
Latest reply on May 27, 2011 by gregm
Hello everyone,

I actually meet what I expect to be sync problems between a TLS and a PWM during a serie of sweeps in continuous mode.
So far, I've been using an Agilent 8164A Mainframe with a TLS 81680A (slot 0) and a PWM 81635A (slot 1).
The code I wrote to handle triggering between the two modules looks like the following:

Sent once before the sweeps' sequence begins:
SOURCE0:WAVELENGTH:SWEEP:MODE CONTINUOUS
SOURCE0:WAVELENGTH:SWEEP:SPEED 4E-8     // 40nm/s
SOURCE0:WAVELENGTH:SWEEP:CYCLES 1
SOURCE0:WAVELENGTH:SWEEP:START 1.505E-06  // start: 1505nm
SOURCE0:WAVELENGTH:SWEEP:STOP 1.58E-06   // end: 1580nm
SOURCE0:WAVELENGTH:SWEEP:STEP 1E-11      // step: 0.01nm
SOURCE0:WAVELENGTH:SWEEP:EXP?            // get nb expected triggers (-> 7501)
INITIATE1:CONTINUOUS 1
TRIGGER:CONFIGURATION LOOP

Sent before every continuous sweep:
SENSE1:FUNCTION:PARAMETER:LOGGING 7501, 0.00025
TRIGGER1:OUTPUT DISABLED
TRIGGER1:INPUT CMEASURE
TRIGGER0:OUTPUT SWSTARTED
TRIGGER0:INPUT IGNORE
SENSE1:FUNCTION:STATE LOGGING,START
SOURCE0:WAVELENGTH:SWEEP START

this code worked successfully with the equipment mentionned above.
More recently, we've purchased a new Mainframe (Agilent 8164B) with a different TLS (81600B, slot0) and an identical PWM (81635A, slot 1).
However, the code I mentioned above doesn't work as well with the new equipment. From time to time, results given by the PWM seems to be "shifted", as if there was a bad sync between the TLS and the PWM, probably due to the triggering commands sent.

Is this code correct?  Have I omitted any command in my configuration?

Thanks in advance
Greg

Edited by: mkelly on Mar 15, 2012 9:47 AM  

Outcomes