[time-nuts] Pendulum CNT91 with TimeLab

GandalfG8 at aol.com GandalfG8 at aol.com
Thu Oct 10 00:28:26 UTC 2013


Considering that I now know there is data coming through I'm wondering if  
I'm still misinterpreting that error message.
I was assuming that the ID string was what TimeLab was claiming to be an  
invalid frequency but it occurs to me that it might also mean "I'm getting  
invalid frequency data and this is where it's coming from..."
In which case perhaps a copy of a portion of  the monitor window  frequency 
data might also be useful just in case that's the root of the  problem......
 
+5.00000000034E+06
+5.00000000035E+06
+5.00000000058E+06
+5.00000000041E+06
+5.00000000031E+06
 
Regards
 
Nigel
GM8PZR
 
 
In a message dated 09/10/2013 22:49:24 GMT Daylight Time, john at miles.io  
writes:

TimeLab  will capture and display the *IDN? result as the instrument name,
but it  shouldn't reject the connection if it doesn't get what it expects.
How is  it behaving when it rejects the data?

You've got to wonder what was  going through the heads of the designers of
the various counters that  didn't implement talk-only mode.   Of all the
obvious useful  features to leave out... :(  

-- john, KE5FX
Miles Design  LLC


> -----Original Message-----
> From:  time-nuts-bounces at febo.com [mailto:time-nuts-
> bounces at febo.com] On  Behalf Of GandalfG8 at aol.com
> Sent: Wednesday, October 09, 2013 12:32  PM
> To: time-nuts at febo.com
> Subject: [time-nuts] Pendulum CNT91  with TimeLab
> 
> Has anybody had any success setting up the  Pendulum CNT91, or the
> Tektronix rebadged equivalent FCA3100, to run  with TimeLab?
> 
> It was suggested here some time ago that it  should be possible to achieve
> this by running the counter in talk only  mode but so far I've had no luck
> with the FCA3100 and am aware of  similar problems with the CNT91.
> 
> I suspect this is more  likely a counter issue, or perhaps in my  case 
that
> should read  "user issue":-) rather than anything to do with the  
software.
>  I'm using an NI USB GPIB adapter and can run the FCA3100 with the  cut
down
> Tektronix supplied version of NI's Signal Express, but  whilst I can  also
> talk to it using NI's Measurement and  Automation Explorer any attempts
> with
> that to switch it into  talk only mode either don't work or perhaps  it's
> reverting as  soon as I close the software to switch over to  TimeLab.
> 
>  I've also tried running the counter in GPIB "compatible" mode",   where
it's
> claimed to emulate the SCPI command set of the HP 5313x  series, but  as
far
> as I can tell TimeLab is rejecting the  data because it checks for a  
valid
> HP ID string whilst the  counters still respond as  either an FCA3100 or
> CNT91.
>  
> Regards
> 
> Nigel
> GM8PZR
>  _______________________________________________
> time-nuts mailing list  -- time-nuts at febo.com
> To unsubscribe, go to  https://www.febo.com/cgi-
> bin/mailman/listinfo/time-nuts
> and  follow the instructions  there.

_______________________________________________
time-nuts  mailing list -- time-nuts at febo.com
To unsubscribe, go to  
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the  instructions there.




More information about the Time-nuts_lists.febo.com mailing list