TenTec
[Top] [All Lists]

[TenTec] Why Ethernet?

To: <tentec@contesting.com>
Subject: [TenTec] Why Ethernet?
From: jdunbar28@mchsi.com (Jim Dunbar)
Date: Sat May 31 20:47:49 2003
Ethernet is really the only logical choice. The 802.3 standard for Ethernet
as well as the 803.11 standard for Wireless Ethernet are
pretty much the universal networking protocols for just about every company
in existence. These companies are running with TCP/IP as the protocol
running over their ethernet networks. It provides you the ability to
interconnect workstations , servers, and any other ethernet capable devices.
It doesn't matter what operating system is being used on the network either.

What you don't want is to have is some proprietary networking protocol being
used to interconnect devices. Ethernet provides the ability to set up FTP
servers and/or TFTP servers in order to upgrade your firmware on the radios,
or for any other kind of control
programs.

I currently have a home office that has both my work  computers as well as
my ham radio equipment. I use a LinkSys four port Ethernet Switch that also
functions as a wireless Access Point interconnected to my cable modem.
Therefore, I can have all of my computers in the office interconnected via
the Ethernet Lan over CAT 5  cable, and I can also take a laptop or a
desktop with a LinkSys Wireless Client PCMCIA card or a Wireless Client
device that interconnects to the PC via the USB port. With either
method, I can now reach the network from anywhere in the house.

Jim
K4PV


----- Original Message -----
From: "Mark Rauchfuss" <mark.rauchfuss@worldnet.att.net>
To: "Gary Hoffman" <ghoffman@spacetech.com>; <tentec@contesting.com>
Sent: Saturday, May 31, 2003 2:30 PM
Subject: Re: [TenTec] Why Ethernet?


> Like, for example the capabilkity toi support bandwidth!
>
>
> ----- Original Message -----
> From: "Gary Hoffman" <ghoffman@spacetech.com>
> To: <tentec@contesting.com>
> Sent: Saturday, May 31, 2003 3:22 PM
> Subject: Re: [TenTec] Why Ethernet?
>
>
> > Yes indeed...to all.... but Ethernet gives you better possibilities for
> > remote control of the rig.
> >
> >
> > ----- Original Message -----
> > From: <AC5E@aol.com>
> > To: <tentec@contesting.com>
> > Sent: Saturday, May 31, 2003 1:57 PM
> > Subject: Re: [TenTec] Why Ethernet?
> >
> >
> > >
> > > I certainly agree it's about time to change to something besides an
> RS232
> > > port  Including a serial port means the customer must shop carefully
to
> > make sure
> > > they can hook up their rig. Todays most common choices are Ethernet,
> USB,
> > and
> > > Firewire.  And then there's the other hundred "new and improved"
stars
> of
> > > tomorrow. If they catch on - which most probably will not.
> > >
> > > While there's nothing really wrong with the typical Ethernet port, I
> don't
> > > network my rigs all that often.  But between the rotor interfaces,
> > computer
> > > logging, keyer, amp interface, etc., etc., there are a whole bunch of
> > wires going
> > > to the back of the shack computer and ham gear.  Far too many for
either
> > > comfort or easy servicing.
> > >
> > > So I would prefer either a regular USB or Firewire port on a rig. At
the
> > rig
> > > end, there's very little difference in cost of implementation between
> any
> > of
> > > the common choices, and far  more confusors come with USB/Firewire
than
> > network
> > > ports these days.  A single strategically located hub with a couple of
> > more
> > > daisy chained to it would sure relieve a lot of the clutter around
here.
> > >
> > > 73  Pete Allen  AC5E
> > > _______________________________________________
> > > TenTec mailing list
> > > TenTec@contesting.com
> > > http://lists.contesting.com/mailman/listinfo/tentec
> > >
> >
> >
> > _______________________________________________
> > TenTec mailing list
> > TenTec@contesting.com
> > http://lists.contesting.com/mailman/listinfo/tentec
> >
>
> _______________________________________________
> TenTec mailing list
> TenTec@contesting.com
> http://lists.contesting.com/mailman/listinfo/tentec

<Prev in Thread] Current Thread [Next in Thread>