Bob,
as by the Z3801 manual, the (RS422) port (of your PC) has to match the
following settings:
Pace: None
Baud Rate: 19200
Parity: Odd
Data Bits: 7/chr
Start Bits: 1
Stop Bits: 1
There is no auto interface configuration mode inside the 3801. If the
settings are wrong or the cable isn't correct, nuthing's gonna happen.
When you have installed SatStat on your PC, check if the default
settings are correct, and select the COM port of your PC that you have
connected the cable to.
If everything is right, select Comm Port -> Port Open. After a while,
communication with the 3801 should be established, and the main form
should begin to periodically update every few seconds.
Shoot me a PM if you don't have the manual.
Btw. I've now installed Ulrich's superb Z38XX that is much more
versatile than the basic SatStat.
Adrian
Robert Benward schrieb:
Adrian,
I thought that was for the Satstat, is the 3801 auto sensing? Don't
you need to send a command?
Bob
----- Original Message ----- From: "Adrian" <[email protected]>
To: "Discussion of precise time and frequency measurement"
<[email protected]>
Sent: Monday, June 14, 2010 5:29 AM
Subject: Re: [time-nuts] My stubborn Z3801A
It's in the same menu where you start / stop communication, just
below the 'Port Open' command.
CommPort > Settings > Baud Rate
Adrian
Robert Benward schrieb:
The minimum voltage is +/-3 volts, I'm getting about +/-6 right now.
How does one change the serial port speed, I don't see anything in
SatStat.
Bob
----- Original Message ----- From: "John Miles" <[email protected]>
To: "Discussion of precise time and frequency measurement"
<[email protected]>
Sent: Sunday, June 13, 2010 8:21 PM
Subject: Re: [time-nuts] My stubborn Z3801A
Still to go: The RS-232 signals look fine going into the cable,
+/-5V, any
ideas why the computer won't read it? Am I missing something? I
tried two
different ports in case I screwed one up one of the ports, but no
luck.
Haven't been following the thread so someone may have suggested
this before,
but: try another computer, a shorter cable, or perhaps a slower
baud rate.
5 volts is near the bottom of the range for RS232 (the signalling
levels are
supposed to be closer to +/- 15V, or at least +/- 12V).
Some RS-232 gear is happy with 5V but it isn't optimal in all
cases. The
problem you mention is more likely to be either a physical or
protocol-level
mismatch than a real hardware fault.
-- john, KE5FX
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- [email protected]
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
