Re: [time-nuts] Lucent KS-24361 GPS Time vs. UTC
Thanks for the reply. I tried all the ports, the only port that allows me to communicate at all with the unit is the J8 Diagnostic port on Ref 0. I also noticed that when I send the command to change to UTC time, the units go into FAULT mode and it takes about 5 minutes to relock the GPS. Mitch. Message: 1 Date: Wed, 26 Nov 2014 21:13:16 -0600 From: Bob Camp kb...@n1k.org To: Discussion of precise time and frequency measurement time-nuts@febo.com Subject: Re: [time-nuts] Lucent KS-24361 GPS Time vs. UTC Message-ID: 50e05f9e-853a-4782-a41c-ea210ccea...@n1k.org Content-Type: text/plain; charset=us-ascii Hi Which port are you putting the commands into? The box *may* respond to some things on the Diag port that it does not respond to on the PPS port. I have not investigated this, but it is a possibility. Bob On Nov 26, 2014, at 12:52 PM, Mitchell Janoff majan...@verizon.net wrote: I now have my KS-24361 operating and I've successfully communicated via RS232 (using the hack described previously) with both SatStat and GPSCon using Win7. The time I'm getting out of the unit is the GPS time (+16 seconds). I've tried to convert the time to UTC by first changing the mode from continuous output to a manual time update(:PTIM:TCOD:CONT 0), and then changing the time to UTC from GPS using the :PTIM:UTC 1 command. Neither of these commands seem to work with this unit. Has anyone experienced this and did you come up with a solution? Thanks. Mitch. ___ 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.
Re: [time-nuts] Lucent KS-24361 GPS Time vs. UTC
Hi If it re-locks the GPS, that suggests they are changing the time at the module level rather than doing the math in the CPU. The 5 minute re-lock is pretty typical of the GPS rebooting. The cell phone guys never use UTC time at the hardware level. All the CDMA cell sites are synchronized to GPS time. Because of this, being able to switch the time base is likely to be considered a bug by people like Lucent. They may have the switch over locked out in multiple ways. Bob On Nov 27, 2014, at 11:33 AM, Mitchell Janoff majan...@verizon.net wrote: Thanks for the reply. I tried all the ports, the only port that allows me to communicate at all with the unit is the J8 Diagnostic port on Ref 0. I also noticed that when I send the command to change to UTC time, the units go into FAULT mode and it takes about 5 minutes to relock the GPS. Mitch. Message: 1 Date: Wed, 26 Nov 2014 21:13:16 -0600 From: Bob Camp kb...@n1k.org To: Discussion of precise time and frequency measurement time-nuts@febo.com Subject: Re: [time-nuts] Lucent KS-24361 GPS Time vs. UTC Message-ID: 50e05f9e-853a-4782-a41c-ea210ccea...@n1k.org Content-Type: text/plain; charset=us-ascii Hi Which port are you putting the commands into? The box *may* respond to some things on the Diag port that it does not respond to on the PPS port. I have not investigated this, but it is a possibility. Bob On Nov 26, 2014, at 12:52 PM, Mitchell Janoff majan...@verizon.net wrote: I now have my KS-24361 operating and I've successfully communicated via RS232 (using the hack described previously) with both SatStat and GPSCon using Win7. The time I'm getting out of the unit is the GPS time (+16 seconds). I've tried to convert the time to UTC by first changing the mode from continuous output to a manual time update(:PTIM:TCOD:CONT 0), and then changing the time to UTC from GPS using the :PTIM:UTC 1 command. Neither of these commands seem to work with this unit. Has anyone experienced this and did you come up with a solution? Thanks. Mitch. ___ 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. ___ 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.
[time-nuts] Lucent KS-24361 GPS Time vs. UTC
I now have my KS-24361 operating and I've successfully communicated via RS232 (using the hack described previously) with both SatStat and GPSCon using Win7. The time I'm getting out of the unit is the GPS time (+16 seconds). I've tried to convert the time to UTC by first changing the mode from continuous output to a manual time update(:PTIM:TCOD:CONT 0), and then changing the time to UTC from GPS using the :PTIM:UTC 1 command. Neither of these commands seem to work with this unit. Has anyone experienced this and did you come up with a solution? Thanks. Mitch. ___ 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.
Re: [time-nuts] Lucent KS-24361 GPS Time vs. UTC
Hi Which port are you putting the commands into? The box *may* respond to some things on the Diag port that it does not respond to on the PPS port. I have not investigated this, but it is a possibility. Bob On Nov 26, 2014, at 12:52 PM, Mitchell Janoff majan...@verizon.net wrote: I now have my KS-24361 operating and I've successfully communicated via RS232 (using the hack described previously) with both SatStat and GPSCon using Win7. The time I'm getting out of the unit is the GPS time (+16 seconds). I've tried to convert the time to UTC by first changing the mode from continuous output to a manual time update(:PTIM:TCOD:CONT 0), and then changing the time to UTC from GPS using the :PTIM:UTC 1 command. Neither of these commands seem to work with this unit. Has anyone experienced this and did you come up with a solution? Thanks. Mitch. ___ 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. ___ 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.
