I suspect that your system is set up to go to sleep.
If that happens Heather won't see the response to the last message it sent. For SCPI receivers, Heather polls the device for a new piece of information every time it gets a response. The requests alternate between the time code message and some receiver status value. At xx:xx:33 Heather requests the syst:stat page which takes three seconds to come in.
No response to a request? No new request sent out... If a new response is not seen within a receiver-dependent timeout (5-20 seconds for the Z3801A), Heather attempts to restart communications, but a sleeping system borks that.
So pretty excited about LH running a Z3801. But what I am seeing is a
consitent stall roughly 45-50 minutes in.
Mark
I agree with the 3 seconds thats what I see with HP sastat, gpscontrol, and
z38XX which are all working fine. So your saying the z3801 is going to
sleep or is it Heather?
How might I change Heather to get around the issue please?
Thanks
Paul
On Tue, Dec 13, 2016 at 4:27 PM, Mark Sims holrum@hotmail.com wrote:
I suspect that your system is set up to go to sleep.
If that happens Heather won't see the response to the last message it
sent. For SCPI receivers, Heather polls the device for a new piece of
information every time it gets a response. The requests alternate between
the time code message and some receiver status value. At xx:xx:33 Heather
requests the syst:stat page which takes three seconds to come in.
No response to a request? No new request sent out... If a new response
is not seen within a receiver-dependent timeout (5-20 seconds for the
Z3801A), Heather attempts to restart communications, but a sleeping system
borks that.
So pretty excited about LH running a Z3801. But what I am seeing is a
consitent stall roughly 45-50 minutes in.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/
mailman/listinfo/time-nuts
and follow the instructions there.
Mark
Hope you have had a great Holiday so far.
Wanted to get back to you on LH with multiple Z3801s.
Have tried the following.
Win XP and Vista
2 X Z3801s
USB ports and real RS232 ports flow control and no flow control.
LH, HP Satstat and gpscontrol
LH stalls on both operating systems and both types of ports.
Satstat and gpscontrol run forever on both Z3801s.
LH and a TBolt work on usb and real serial ports without issue.
Have looked at all of the commands in LH and do not see anything that might
help.
Great program but doesn't help me much.
By the way now thatthe second Z3801 is working with a Piezo oscillator, I
am mapping a FRS C rubidium into the Z3801 to see how it does. I may guess
a 10X improvement from what I have seen.
Regards
Paul
WB8TSL
On Tue, Dec 13, 2016 at 8:21 PM, paul swed paulswedb@gmail.com wrote:
Mark
I agree with the 3 seconds thats what I see with HP sastat, gpscontrol,
and z38XX which are all working fine. So your saying the z3801 is going to
sleep or is it Heather?
How might I change Heather to get around the issue please?
Thanks
Paul
On Tue, Dec 13, 2016 at 4:27 PM, Mark Sims holrum@hotmail.com wrote:
I suspect that your system is set up to go to sleep.
If that happens Heather won't see the response to the last message it
sent. For SCPI receivers, Heather polls the device for a new piece of
information every time it gets a response. The requests alternate between
the time code message and some receiver status value. At xx:xx:33 Heather
requests the syst:stat page which takes three seconds to come in.
No response to a request? No new request sent out... If a new response
is not seen within a receiver-dependent timeout (5-20 seconds for the
Z3801A), Heather attempts to restart communications, but a sleeping system
borks that.
So pretty excited about LH running a Z3801. But what I am seeing is a
consitent stall roughly 45-50 minutes in.
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/m
ailman/listinfo/time-nuts
and follow the instructions there.