Searching \ for 'PicLan' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devices.htm?key=pic
Search entire site for: 'PicLan'.

Truncated match.
PICList Thread
'PicLan'
1998\05\11@104120 by Pedro Barrios

flavicon
face
Hi everyone,

I need to design a device that would allow access to a
specific machine and measures the time the machine was in use.
This is to be done via a keypad. Every user will have a different
password. It must be user expandable.

I think this can be easily done with a PIC. However, the device
must be able to communicate with a LAN server. All the users
passwords, as well as time-keeping will be done by the server. The
device will only "question" the server as of whether the password was right
or not,
and if right the server will send an authorization code, the machine will
activate, and the server will start measuring the time the machine
has been in use. When the user desires to stop using the machine,
the machine is turned off and the time of use is recorded by the server.

There will be many machines controlled by this device-server configuration.
Thus, the server must be able to execute parallel identification and time
keeping.

So, I guess my question is: Can this be done with PIC's? I have the
premonition that I need other chip capable of communicating with
the LAN, which one would that be? Any suggestions or recommendations
to any of this?

Regards,

Pedro

1998\05\11@122709 by andre

flavicon
face
Pedro:
Dispense which possessor you know better otherwise
you can use any possessor to get this job done. PIC
possessors are ready for any thing you name it cheap and reliable.
Excellent Technical support and more.

Andre Abelian



Pedro Barrios wrote:

{Quote hidden}

1998\05\11@145044 by White Horse Design

flavicon
face
At 09:39 11/05/98 -0500, you wrote:
>
>I need to design a device that would allow access to a
>specific machine and measures the time the machine was in use.
>This is to be done via a keypad. Every user will have a different
>password. It must be user expandable.

...

>So, I guess my question is: Can this be done with PIC's? I have the
>premonition that I need other chip capable of communicating with
>the LAN, which one would that be? Any suggestions or recommendations
>to any of this?

I sent someone a tiny tcp/ip stack written in C a short while ago (you know
who you are!). From what you state, I don't think a low end (mid-range?)
PIC like the 16C74A would be appropriate (or a little higher end - though
I'm not familiar with the most powerful PICs I'm afraid). I would suggest a
low-end Hitachi H8/300 series. It sounds as if this system may be subject
to "but let's just add this or that" and therefore a bit more power than
perhaps the specification suggests should be added. Sometimes I use, say,
70% of a CPU's power for a job (depending on how tight the spec is), on
this one, I'd (off the top of my head - you must know far more about it
than you were able to post - politics etc) say allow 50% and certainly make
adding changes or enhancements easy.

Just my two-pen'orth (not a mis-spelling) - a quaint old English saying -
the Ameicans would say "my 2 cents" I guess..!

Regards

Adrian

WWW    WWW   Adrian Gothard
WWW WW WWW   White Horse Design
WWWWWWWWWW   +44-385-970009 (Mobile/SMS), +44-118-962-8913/4 (voice/fax)
WWWW  WWWW   spam_OUTwhdTakeThisOuTspamzetnet.co.uk, http://www.users.zetnet.co.uk/whd
---
Developers of GPS satellite-based tracking systems

1998\05\12@031529 by William Chops Westfield

face picon face
   However, the device must be able to communicate with a LAN server. All
   the users passwords, as well as time-keeping will be done by the
   server. The device will only "question" the server as of whether the
   password was right or not, and if right the server will send an
   authorization code, the machine will activate, and the server will start
   measuring the time the machine has been in use. When the user desires to
   stop using the machine, the machine is turned off and the time of use is
   recorded by the server.

First, you must find out whether there is particular type of server and/or
"authorization" protocol that you are expected to use.  There are many
standards for this sort of thing ("The great thing about standards is that
there are so many to choose from"), and they vary quite a bit in
complexity.  For example "xtacacs", "xtacacs" and "radius" operate over
UDP/IP, making them somewhat simpler than "tacacs+", which requires TCP/IP,
and "kerberos" is considerably more complex in several dimensions.  Those
are just IP-based protocols that will work over an IP network through
multiple routers and over various media, which is swell and politically
correcct, but useless if the user had in mind using an existing Novell or
netbios network.

I would suspect that most network tasks of this sort are beyond all but
the largest PICs, and pointlessly challenging on that sort of "embedded"
architecture.  The obvious "cheap" platform is an old PC running DOS and
one of the free network stacks, and the obvious "cool" platform is one of
those embedded network platforms that people are starting to sell, based
on things like the Motorola QUICC, Power-QuICC, and so on.

BillW

More... (looser matching)
- Last day of these posts
- In 1998 , 1999 only
- Today
- New search...