time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

Re: [time-nuts] Did my Tbolt die ?

AF
Adam Feigin
Sun, Jul 18, 2010 8:53 AM

Well, I wish it were all that simple. I was originally running  the
Tbolt with tboltd under Linux to provide data to one of my ntp servers,
on a real(tm) serial port. Sometime after a reboot (or maybe during ??)
it just stopped working, at least the serial portion. I've tried a bunch
of different machines, including attaching the thing to a Moxa Serial
device server, and i dont get anything out at all. I've let it sit
overnight, power cycling, tried  different machines, (VirtualBox, Wine
with USB serial and direct serial) all to no avail. It simply gives no
output at all.

Oh well, I suppose it was good while it lasted. I'm off over to the pond
for holiday, so maybe I'll get "lucky" and it will get happy after I get
back, otherwise I'll have to rip it apart and attempt to figure out
whats wrong -- probably just the serial chip blown somehow.....

Date: Sat, 17 Jul 2010 08:40:23 -0400
From: "Stan, W1LE" stanw1le@verizon.net
Subject: Re: [time-nuts] Did my Tbolt die ?

Hello Adam,  I suspect that:

Upon rebooting, the OS came up and did not recognize the (serial) COM
port assignment you had used before.

Check the COM port assignments in the control panel, and adjust
accordingly, to match the actual COM port you are using

Looks like the TB is good, I suspect the PC end.

Stan, W1LE

Well, I wish it were all that simple. I was originally running the Tbolt with tboltd under Linux to provide data to one of my ntp servers, on a real(tm) serial port. Sometime after a reboot (or maybe during ??) it just stopped working, at least the serial portion. I've tried a bunch of different machines, including attaching the thing to a Moxa Serial device server, and i dont get anything out at all. I've let it sit overnight, power cycling, tried different machines, (VirtualBox, Wine with USB serial and direct serial) all to no avail. It simply gives no output at all. Oh well, I suppose it was good while it lasted. I'm off over to the pond for holiday, so maybe I'll get "lucky" and it will get happy after I get back, otherwise I'll have to rip it apart and attempt to figure out whats wrong -- probably just the serial chip blown somehow..... > Date: Sat, 17 Jul 2010 08:40:23 -0400 > From: "Stan, W1LE" <stanw1le@verizon.net> > Subject: Re: [time-nuts] Did my Tbolt die ? > > Hello Adam, I suspect that: > > Upon rebooting, the OS came up and did not recognize the (serial) COM > port assignment you had used before. > > Check the COM port assignments in the control panel, and adjust > accordingly, to match the actual COM port you are using > > Looks like the TB is good, I suspect the PC end. > > Stan, W1LE > >
SR
Stanley Reynolds
Sun, Jul 18, 2010 11:33 AM

Adam,

Cold solder joints on the connector or chip would be my first guess after the
power supply was checked.

Stanley

----- Original Message ----
From: Adam Feigin awf@iis.ee.ethz.ch
To: time-nuts@febo.com
Sent: Sun, July 18, 2010 3:53:36 AM
Subject: Re: [time-nuts] Did my Tbolt die ?

Well, I wish it were all that simple. I was originally running  the
Tbolt with tboltd under Linux to provide data to one of my ntp servers,
on a real(tm) serial port. Sometime after a reboot (or maybe during ??)
it just stopped working, at least the serial portion. I've tried a bunch
of different machines, including attaching the thing to a Moxa Serial
device server, and i dont get anything out at all. I've let it sit
overnight, power cycling, tried  different machines, (VirtualBox, Wine
with USB serial and direct serial) all to no avail. It simply gives no
output at all.

Oh well, I suppose it was good while it lasted. I'm off over to the pond
for holiday, so maybe I'll get "lucky" and it will get happy after I get
back, otherwise I'll have to rip it apart and attempt to figure out
whats wrong -- probably just the serial chip blown somehow.....

Date: Sat, 17 Jul 2010 08:40:23 -0400
From: "Stan, W1LE" stanw1le@verizon.net
Subject: Re: [time-nuts] Did my Tbolt die ?

Hello Adam,  I suspect that:

Upon rebooting, the OS came up and did not recognize the (serial) COM 
port assignment you had used before.

Check the COM port assignments in the control panel, and adjust
accordingly, to match the actual COM port you are using

Looks like the TB is good, I suspect the PC end.

Stan, W1LE

 


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.

Adam, Cold solder joints on the connector or chip would be my first guess after the power supply was checked. Stanley ----- Original Message ---- From: Adam Feigin <awf@iis.ee.ethz.ch> To: time-nuts@febo.com Sent: Sun, July 18, 2010 3:53:36 AM Subject: Re: [time-nuts] Did my Tbolt die ? Well, I wish it were all that simple. I was originally running  the Tbolt with tboltd under Linux to provide data to one of my ntp servers, on a real(tm) serial port. Sometime after a reboot (or maybe during ??) it just stopped working, at least the serial portion. I've tried a bunch of different machines, including attaching the thing to a Moxa Serial device server, and i dont get anything out at all. I've let it sit overnight, power cycling, tried  different machines, (VirtualBox, Wine with USB serial and direct serial) all to no avail. It simply gives no output at all. Oh well, I suppose it was good while it lasted. I'm off over to the pond for holiday, so maybe I'll get "lucky" and it will get happy after I get back, otherwise I'll have to rip it apart and attempt to figure out whats wrong -- probably just the serial chip blown somehow..... > Date: Sat, 17 Jul 2010 08:40:23 -0400 > From: "Stan, W1LE" <stanw1le@verizon.net> > Subject: Re: [time-nuts] Did my Tbolt die ? > > Hello Adam,  I suspect that: > > Upon rebooting, the OS came up and did not recognize the (serial) COM  > port assignment you had used before. > > Check the COM port assignments in the control panel, and adjust > accordingly, to match the actual COM port you are using > > Looks like the TB is good, I suspect the PC end. > > Stan, W1LE > >  _______________________________________________ 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.
MD
Magnus Danielson
Sun, Jul 18, 2010 11:57 AM

On 07/18/2010 10:53 AM, Adam Feigin wrote:

Well, I wish it were all that simple. I was originally running  the
Tbolt with tboltd under Linux to provide data to one of my ntp servers,
on a real(tm) serial port. Sometime after a reboot (or maybe during ??)
it just stopped working, at least the serial portion. I've tried a bunch
of different machines, including attaching the thing to a Moxa Serial
device server, and i dont get anything out at all. I've let it sit
overnight, power cycling, tried  different machines, (VirtualBox, Wine
with USB serial and direct serial) all to no avail. It simply gives no
output at all.

Just rebooting should not be the killer, but power-cycling may be.
Grounding of equipment may also be an issue, as you connect things around.

Cheers,
Magnus

On 07/18/2010 10:53 AM, Adam Feigin wrote: > Well, I wish it were all that simple. I was originally running the > Tbolt with tboltd under Linux to provide data to one of my ntp servers, > on a real(tm) serial port. Sometime after a reboot (or maybe during ??) > it just stopped working, at least the serial portion. I've tried a bunch > of different machines, including attaching the thing to a Moxa Serial > device server, and i dont get anything out at all. I've let it sit > overnight, power cycling, tried different machines, (VirtualBox, Wine > with USB serial and direct serial) all to no avail. It simply gives no > output at all. Just rebooting should not be the killer, but power-cycling may be. Grounding of equipment may also be an issue, as you connect things around. Cheers, Magnus
JL
J. L. Trantham
Sun, Jul 18, 2010 12:11 PM

I had one die while being monitored with TBoltMon.  There was no ability to
communicate but the 10 MHz continued (close but clearly not disciplined).  I
do not recall if the 1 PPS was still present or not.  I am on vacation right
now and can't get to it.  If you need that information, I can check it when
I get back.  I haven't gotten around to doing the 'autopsy' yet.

Joe

-----Original Message-----
From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On
Behalf Of Adam Feigin
Sent: Sunday, July 18, 2010 3:54 AM
To: time-nuts@febo.com
Subject: [Bulk] Re: [time-nuts] Did my Tbolt die ?

Well, I wish it were all that simple. I was originally running  the
Tbolt with tboltd under Linux to provide data to one of my ntp servers,
on a real(tm) serial port. Sometime after a reboot (or maybe during ??)
it just stopped working, at least the serial portion. I've tried a bunch
of different machines, including attaching the thing to a Moxa Serial
device server, and i dont get anything out at all. I've let it sit
overnight, power cycling, tried  different machines, (VirtualBox, Wine
with USB serial and direct serial) all to no avail. It simply gives no
output at all.

Oh well, I suppose it was good while it lasted. I'm off over to the pond
for holiday, so maybe I'll get "lucky" and it will get happy after I get
back, otherwise I'll have to rip it apart and attempt to figure out
whats wrong -- probably just the serial chip blown somehow.....

Date: Sat, 17 Jul 2010 08:40:23 -0400
From: "Stan, W1LE" stanw1le@verizon.net
Subject: Re: [time-nuts] Did my Tbolt die ?

Hello Adam,  I suspect that:

Upon rebooting, the OS came up and did not recognize the (serial) COM
port assignment you had used before.

Check the COM port assignments in the control panel, and adjust
accordingly, to match the actual COM port you are using

Looks like the TB is good, I suspect the PC end.

Stan, W1LE


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.

I had one die while being monitored with TBoltMon. There was no ability to communicate but the 10 MHz continued (close but clearly not disciplined). I do not recall if the 1 PPS was still present or not. I am on vacation right now and can't get to it. If you need that information, I can check it when I get back. I haven't gotten around to doing the 'autopsy' yet. Joe -----Original Message----- From: time-nuts-bounces@febo.com [mailto:time-nuts-bounces@febo.com] On Behalf Of Adam Feigin Sent: Sunday, July 18, 2010 3:54 AM To: time-nuts@febo.com Subject: [Bulk] Re: [time-nuts] Did my Tbolt die ? Well, I wish it were all that simple. I was originally running the Tbolt with tboltd under Linux to provide data to one of my ntp servers, on a real(tm) serial port. Sometime after a reboot (or maybe during ??) it just stopped working, at least the serial portion. I've tried a bunch of different machines, including attaching the thing to a Moxa Serial device server, and i dont get anything out at all. I've let it sit overnight, power cycling, tried different machines, (VirtualBox, Wine with USB serial and direct serial) all to no avail. It simply gives no output at all. Oh well, I suppose it was good while it lasted. I'm off over to the pond for holiday, so maybe I'll get "lucky" and it will get happy after I get back, otherwise I'll have to rip it apart and attempt to figure out whats wrong -- probably just the serial chip blown somehow..... > Date: Sat, 17 Jul 2010 08:40:23 -0400 > From: "Stan, W1LE" <stanw1le@verizon.net> > Subject: Re: [time-nuts] Did my Tbolt die ? > > Hello Adam, I suspect that: > > Upon rebooting, the OS came up and did not recognize the (serial) COM > port assignment you had used before. > > Check the COM port assignments in the control panel, and adjust > accordingly, to match the actual COM port you are using > > Looks like the TB is good, I suspect the PC end. > > Stan, W1LE > > _______________________________________________ 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.