From: tz <tz2026@gmail.com>
To: "Ron Frazier (NTP)" <timekeepingntplist@c3energy.com>
Cc: "thumbgps-devel@lists.bufferbloat.net"
<thumbgps-devel@lists.bufferbloat.net>,
questions@lists.ntp.org
Subject: Re: [Thumbgps-devel] YEA! My Sure Electronics GPS just arrived.
Date: Sat, 24 Mar 2012 11:22:35 -0400 [thread overview]
Message-ID: <CAFv7OiibAyfc+qbCvNHtdLOxoz40pxBTmtbGooe=QdXDEdzMmg@mail.gmail.com> (raw)
In-Reply-To: <4F6D3E94.4080902@c3energy.com>
[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]
The skytraq EVBs (direct from skytraq) all use the SiLabs chip - you cannot
plug more than one in at a time under XP. It won't enumerate the second as
a com port and it confuses everything.
On Mar 23, 2012 11:25 PM, "Ron Frazier (NTP)" <
timekeepingntplist@c3energy.com> wrote:
> Hi all,
>
> I just discovered an interesting thing about the Sure board's serial - USB
> converter. I went ahead and installed the driver. With this serial - USB
> converter, which is a Silicon Labs CP210x chipset, no matter which USB port
> I plug it into, it becomes COM6, which was the next one available. With
> the Prolific based devices, including the TU-S9 and the BU-353, each
> subsequent USB port I plug into becomes a new com port, so those devices
> became COM3, COM4, and COM5 respectively as I plugged them into succeeding
> USB ports. I can see pros and cons either way.
>
> With the Prolific way, if I move the device to a different port, I have to
> have a different setup in the ntp.conf file, although you could probably
> have multiple setups, and if nothing is attached to a given port, then it
> gets ignored.
>
> With the Silicon Labs way, I only have to have one set of configuration
> options in ntp.conf. However, what happens if I plug in another device
> with the same chipset? I'm assuming the next one will become COM7. But,
> now, if I unplug both and plug them back into the same ports, but in the
> opposite sequence, I'll bet the original 1st device will now be COM7 and
> the original 2nd device will be COM6. I can see how this would cause some
> problems.
>
> I have not tested yet whether this board's USB port has a built in driver
> in Linux.
>
> Sincerely,
>
> Ron
>
>
>
> --
>
> (PS - If you email me and don't get a quick response, don't be concerned.
> I get about 300 emails per day from alternate energy mailing lists and
> such. I don't always see new messages very quickly. If you need a
> reply and have not heard from me in 1 - 2 weeks, send your message again.)
>
> Ron Frazier
> timekeepingdude AT c3energy.com
>
> ______________________________**_________________
> Thumbgps-devel mailing list
> Thumbgps-devel@lists.**bufferbloat.net<Thumbgps-devel@lists.bufferbloat.net>
> https://lists.bufferbloat.net/**listinfo/thumbgps-devel<https://lists.bufferbloat.net/listinfo/thumbgps-devel>
>
[-- Attachment #2: Type: text/html, Size: 2821 bytes --]
prev parent reply other threads:[~2012-03-24 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 21:08 Ron Frazier (NTP)
[not found] ` <cJ7br.8104$dq4.6080@newsfe23.iad>
[not found] ` <4F6D285C.1070505@c3energy.com>
2012-03-24 3:25 ` Ron Frazier (NTP)
2012-03-24 6:38 ` Ron Frazier (NTP)
2012-03-24 8:21 ` Andrew McGregor
2012-03-24 14:14 ` Ron Frazier (NTP)
2012-03-24 15:06 ` Dave Taht
2012-03-24 15:22 ` tz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFv7OiibAyfc+qbCvNHtdLOxoz40pxBTmtbGooe=QdXDEdzMmg@mail.gmail.com' \
--to=tz2026@gmail.com \
--cc=questions@lists.ntp.org \
--cc=thumbgps-devel@lists.bufferbloat.net \
--cc=timekeepingntplist@c3energy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox