Did my Tbolt die ?
After rebooting one of my servers, I noticed that I was no longer
getting information from my Thunderbolt. Low and behold, it really seems
to be no longer supplying TSIP packets on the serial port. The PS is
okay, and the PPS and 10Mhz outputs also are working. Its just the
serial output which seems to be broken. Connected it directly to a PC,
and tried with both Heather and Tboltmon. Heather says No COM1 Serial
Port data seen, and Tboltmon shows data being sent, but nothing being
received. Even tried a factory reset via Tboltmon, to no avail.
Have no idea why it might have stopped working. Any suggestions ? TIA.
On 07/17/2010 09:02 AM, Adam Feigin wrote:
After rebooting one of my servers, I noticed that I was no longer
getting information from my Thunderbolt. Low and behold, it really seems
to be no longer supplying TSIP packets on the serial port. The PS is
okay, and the PPS and 10Mhz outputs also are working. Its just the
serial output which seems to be broken. Connected it directly to a PC,
and tried with both Heather and Tboltmon. Heather says No COM1 Serial
Port data seen, and Tboltmon shows data being sent, but nothing being
received. Even tried a factory reset via Tboltmon, to no avail.
Have no idea why it might have stopped working. Any suggestions ? TIA.
OK, this is on any suggestions...
Have you unhooked it completely, let it sit there for a while and then
hook it up again?
Sometimes it works... when it is mildly upset.
Cheers,
Magnus
Same thing happened to me. Lady Heather said no data was being received.
Disconnecting power to the TBolt for a few seconds and reconnecting did the trick.
OK, this is on any suggestions...
Have you unhooked it completely, let it sit there for a while and then hook it up again?
Sometimes it works... when it is mildly upset.
Cheers,
Magnus
--
Raj, VU2ZAP
Bangalore, India.
I have had problems with TBolts on PCs. The COM port assignments seem
to be a bit volatile,
plug in a different mouse or other user and you may find the COM port
has been assigned to it.
I have never been able to confidently cope with this problem, I just
keep hacking the
system and sooner or later I get the COM port right with the right
settings and all is well.
There seem to be up to 3 layers to get right.
This may be because I use USB to serial converters or just be
inherent to the later Windows OS.
cheers, Neville Michie
On 17/07/2010, at 5:02 PM, Adam Feigin wrote:
After rebooting one of my servers, I noticed that I was no longer
getting information from my Thunderbolt. Low and behold, it really
seems
to be no longer supplying TSIP packets on the serial port. The PS is
okay, and the PPS and 10Mhz outputs also are working. Its just the
serial output which seems to be broken. Connected it directly to a PC,
and tried with both Heather and Tboltmon. Heather says No COM1 Serial
Port data seen, and Tboltmon shows data being sent, but nothing being
received. Even tried a factory reset via Tboltmon, to no avail.
Have no idea why it might have stopped working. Any suggestions ?
TIA.
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.
How do you find the latency on a USB to Serial converter?
I think a physical port is a little better at not changing than a
'virtal' port :)
On Sat, 2010-07-17 at 19:17 +1000, Neville Michie wrote:
I have had problems with TBolts on PCs. The COM port assignments seem
to be a bit volatile,
plug in a different mouse or other user and you may find the COM port
has been assigned to it.
I have never been able to confidently cope with this problem, I just
keep hacking the
system and sooner or later I get the COM port right with the right
settings and all is well.
There seem to be up to 3 layers to get right.
This may be because I use USB to serial converters or just be
inherent to the later Windows OS.
cheers, Neville Michie
On 17/07/2010, at 5:02 PM, Adam Feigin wrote:
After rebooting one of my servers, I noticed that I was no longer
getting information from my Thunderbolt. Low and behold, it really
seems
to be no longer supplying TSIP packets on the serial port. The PS is
okay, and the PPS and 10Mhz outputs also are working. Its just the
serial output which seems to be broken. Connected it directly to a PC,
and tried with both Heather and Tboltmon. Heather says No COM1 Serial
Port data seen, and Tboltmon shows data being sent, but nothing being
received. Even tried a factory reset via Tboltmon, to no avail.
Have no idea why it might have stopped working. Any suggestions ?
TIA.
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.
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
On 7/17/2010 3:02 AM, Adam Feigin wrote:
After rebooting one of my servers, I noticed that I was no longer
getting information from my Thunderbolt. Low and behold, it really seems
to be no longer supplying TSIP packets on the serial port. The PS is
okay, and the PPS and 10Mhz outputs also are working. Its just the
serial output which seems to be broken. Connected it directly to a PC,
and tried with both Heather and Tboltmon. Heather says No COM1 Serial
Port data seen, and Tboltmon shows data being sent, but nothing being
received. Even tried a factory reset via Tboltmon, to no avail.
Have no idea why it might have stopped working. Any suggestions ? TIA.
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.
On Sat, Jul 17, 2010 at 5:17 AM, Neville Michie namichie@gmail.com wrote:
I have had problems with TBolts on PCs. The COM port assignments seem to be
a bit volatile,
plug in a different mouse or other user and you may find the COM port has
been assigned to it.
I have never been able to confidently cope with this problem, I just keep
hacking the
system and sooner or later I get the COM port right with the right settings
and all is well.
There seem to be up to 3 layers to get right.
This may be because I use USB to serial converters or just be inherent to
the later Windows OS.
cheers, Neville Michie
If you drill down under the Advanced button in the Serial Port Control panel
area you can reset the Windows COM port for a single port.
If you know the port is not in use, ignore the message that tells you that
it is in use, when you change the port number.
You can also search the Windows registry for the "COM Port
Arbitrator". It is a 256 binary bit map of the assigned, and the
next to be assigned, COM port. That is where you reset the ever
incrementing COM port number.
If you are using a USB converter and want it to stay put, do the
following.
This should work for non-FTDI devices, that have serial numbers, just match
the VID/PID.
From FTDI Support:
===========
Hello,
What you will need to do is uninstall the driver for the FTDI device. Now
you will need to create a binary value in the registry by doing the
following:
Go to START and select RUN
Type regedit in the filed and select ok to get into the registry
Add a REG_BINARY value called IgnoreHWSerNum to the registry and setting it
to 01.
This value is held in the registry key located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum
(Device VID, PID and interface}
For a default FTDI device ID (VID 0x0403, PID 0x6001), add the following
registry REG_BINARY value set to 01:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum0
4036001
Now install the driver again. After this the com port should not increment.
Regards
James Leary
Support Engineer
FTDI Ltd
If those don't help I can tell you the other darker places of the registry
to examine and poke at. I had to make one of my programs "Idiot Proof".
Customers kept calling me up and asking me "What COM port do I have?". I
always wanted to respond "How #$)*#)$ should I know? It is your computer."
[It happened a lot, this group of customers were not Computer People.].
Instead I wrote my programs to always find the correct COM port for the
customer. I need to turn that into a DLL so other people can use it.
"Programming is a race between making programs Idiot Proof, so that any
Idiot can use it, and the Universe building bigger and better idiots. The
Universe is winning."
--
http://blog.softwaresafety.net/
http://www.designer-iii.com/
http://www.wearablesmartsensors.com/
It is a windows thing
James thanks for the very helpful ways to cure it.
I need to do that on a couple of modern usb ports
On Sat, Jul 17, 2010 at 9:09 AM, Bob Paddock bob.paddock@gmail.com wrote:
On Sat, Jul 17, 2010 at 5:17 AM, Neville Michie namichie@gmail.com
wrote:
I have had problems with TBolts on PCs. The COM port assignments seem to
be
a bit volatile,
plug in a different mouse or other user and you may find the COM port has
been assigned to it.
I have never been able to confidently cope with this problem, I just keep
hacking the
system and sooner or later I get the COM port right with the right
settings
and all is well.
There seem to be up to 3 layers to get right.
This may be because I use USB to serial converters or just be inherent to
the later Windows OS.
cheers, Neville Michie
If you drill down under the Advanced button in the Serial Port Control
panel
area you can reset the Windows COM port for a single port.
If you know the port is not in use, ignore the message that tells you that
it is in use, when you change the port number.
You can also search the Windows registry for the "COM Port
Arbitrator". It is a 256 binary bit map of the assigned, and the
next to be assigned, COM port. That is where you reset the ever
incrementing COM port number.
If you are using a USB converter and want it to stay put, do the
following.
This should work for non-FTDI devices, that have serial numbers, just match
the VID/PID.
From FTDI Support:
Hello,
What you will need to do is uninstall the driver for the FTDI device. Now
you will need to create a binary value in the registry by doing the
following:
Go to START and select RUN
Type regedit in the filed and select ok to get into the registry
Add a REG_BINARY value called IgnoreHWSerNum to the registry and setting it
to 01.
This value is held in the registry key located at:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum
(Device VID, PID and interface}
For a default FTDI device ID (VID 0x0403, PID 0x6001), add the following
registry REG_BINARY value set to 01:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags\IgnoreHWSerNum0
4036001
Now install the driver again. After this the com port should not increment.
Regards
James Leary
Support Engineer
FTDI Ltd
If those don't help I can tell you the other darker places of the registry
to examine and poke at. I had to make one of my programs "Idiot Proof".
Customers kept calling me up and asking me "What COM port do I have?". I
always wanted to respond "How #$)*#)$ should I know? It is your computer."
[It happened a lot, this group of customers were not Computer People.].
Instead I wrote my programs to always find the correct COM port for the
customer. I need to turn that into a DLL so other people can use it.
"Programming is a race between making programs Idiot Proof, so that any
Idiot can use it, and the Universe building bigger and better idiots. The
Universe is winning."
--
http://blog.softwaresafety.net/
http://www.designer-iii.com/
http://www.wearablesmartsensors.com/
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.