Searching \ for 'Email from a pic' 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: 'Email from a pic'.

Truncated match.
PICList Thread
'Email from a pic'
1998\10\07@212329 by Robert & Susan Hoar

flavicon
face
I have just made it so that I can send E-mail from a pic.
I can read PORTB and send it in an email message.
This can be done at any interval, or just stay on-line and keep sending.

It can also generate web pages.

Just think, put one of these in a vending machine and get the status of the
machine
without getting wet. Put one in your home and see if you left the TV on.

I can make it interactive to read mail also.

This is very exciting and so easy even beginners will be able to implement
this.

Will post more.

Red
Robert Hoar

spam_OUTrwhoarTakeThisOuTspamtecnet1.jcte.jcs.mil
.....srhoarKILLspamspam@spam@global2000.net

With Interest in Astronomy, Celestrial Navigation,
Embedded Controls, Nuclear Power.

Available for information, contact me at:
ICQ #10764173

For info on
:How to make your own PCB's
:Drive stepper motors

try
<http://www.members.global2000.net/~srhoar/>

1998\10\07@223135 by Stephen Holland

flavicon
face
I'd love to see more about this...


-----Original Message-----
From: Robert & Susan Hoar <srhoarspamKILLspamGLOBAL2000.NET>
To: .....PICLISTKILLspamspam.....MITVMA.MIT.EDU <EraseMEPICLISTspam_OUTspamTakeThisOuTMITVMA.MIT.EDU>
Date: Wednesday, October 07, 1998 6:24 PM
Subject: Email from a pic


{Quote hidden}

1998\10\08@120351 by blacet

flavicon
face
That's pretty cool!

When I was at HP a couple years ago, they came out with a Spectrum
Analyzer that had it's own web site. That is EACH instrument had a
unique web site and data from the instrument was posted to the site in
real time.

Regards.
-------------------------
John Blacet
Blacet Research Music Electronics
-------------------------
KILLspamblacetKILLspamspammetro.net
http://metro.net/blacet/music.html

1998\10\08@221129 by Robert & Susan Hoar

flavicon
face
I have now added a page to my web site which was created by a pic.
I can send email and files with it.
It does not connect through a PC.

xtal -->PIC-->MODEM-->Internet

there are only 6 parts :

3 resistors
1 pic
1 crystal
1 MODEM (some old 2400 I had)

The Pic calls up the server and sends the mail or what ever.

I will post all on my web page by next weekend.


Red
Robert Hoar

RemoveMErwhoarTakeThisOuTspamtecnet1.jcte.jcs.mil
spamBeGonesrhoarspamBeGonespamglobal2000.net

With Interest in Astronomy, Celestrial Navigation,
Embedded Controls, Nuclear Power.

Available for information, contact me at:
ICQ #10764173

For info on
:How to make your own PCB's
:Drive stepper motors

try
<http://www.members.global2000.net/~srhoar/>

1998\10\29@064851 by Chris Mayhew

flavicon
face
Robert & Susan Hoar wrote:
>
> I have now added a page to my web site which was created by a pic.
> I can send email and files with it.
> It does not connect through a PC.
>


If Robert & Susan hapen to see this would you post your web site url
again......i seem to have missed it.......the one below points to a
broken link or old site.   OK, so i'm a few weeks behind !!!!  but it is
a cool idea !

Thanks
Chris

> <http://www.members.global2000.net/~srhoar/>


'Email from a pic'
1998\12\31@152439 by chuck
flavicon
face
Robert,
I can't seem to get to your web page.
Do you still have this PIC -> Email
posted there?
I would like to see how you did it.




---Robert & Susan Hoar <TakeThisOuTsrhoarEraseMEspamspam_OUTGLOBAL2000.NET> wrote:
{Quote hidden}

==
Chuck Hellebuyck
Electronic Products
EraseMEchuckspamelproducts.com
*****Program PICs in BASIC Special!*********
Complete 16F84 package for only $99.95
Includes: Compiler, Programmer and PIC part
http://www.elproducts.com
_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com


'EMAIL from a PIC'
2000\04\21@214205 by Peter
flavicon
face
Hi there folks,

Just had to stick my nose into this subject. As a Unix professional I
know a bit of what is involved in sending/recieving EMAIL both from a
client side and the server side as I have been responsible for the care
and feeding of this facility from time to time.

To send EMAIL from a PIC assumes a couple of things:

1) You have a working TCP/IP stack and related hardware on the PIC.

2) You have a gateway willing to relay for the PIC unless you want to
get into the complexities of setting up a full blown implementation of
sendmail,smail, qmail or other mail transport agent (MTA).

The procedure is pretty simple, well at least in concept.

A) Open a connection to the system with the MTA running on it on TCP
port 25.

B) Establish who you are with the server using the HELO syntax

example:

The PIC sends--
HELO picbox1
The MTA replies with--
250 mailrelay.mydomain.tld Hello picbox1.mydomain.tld Pleased to meet
you

C) Establish who you are sending mail from

The PIC sends --
mail from: RemoveMEpicboxEraseMEspamEraseMEmydomain.tld
The MTA replies with --
250 RemoveMEpicboxspam_OUTspamKILLspammydomain.tld... sender ok

D) Establish who is to get the mail

The PIC sends --
rcpt to: RemoveMEsomeoneTakeThisOuTspamspamdomain.tld
The MTA replies with --
250 EraseMEsomeonespamspamspamBeGonedomain.tld... Recipient ok

E) Now you want to send a message body.

The PIC sends ---
data
The MTA replies with --
354 Enter mail, end with "." on a line by itself

F) Now you can actually compose the mail.  If you want the sender, and a
subject to appear on the recipient's mail program's display you need to
have your first two lines be:
From: Pic Program
Subject: Overtemp in the engine room. Warp drive meltdown imminent.

(I couldn't resist the StarTrek reference! <VBG>)

G) You want a blank line between the subject line and the body of the
text so the recipient's mail program will properly parse out the
headers.  Another thing is if you are going to generate HTML mail you
want to  have right after the Subject: line a line reading
"Content-Type: text/html"  There are other MIME types that you can
specify, but I'm not going into the complicated subject of MIME encoding
standards, headers, parsing and all that.

H) Once the body of your message is done you terminate the message with
a line with a "." all by its lonesome just as the reply above tells you
to. When you do you will get a reply back from the MTA

250 UAA01680 Message accepted.

The portion UAA01580 is a queue ID that you can possibly use later on
for auditing purposes, but I leave that up to other imaginations.



--
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Peter L. Berghold                      http://www.berghold.net
RemoveMEPeterKILLspamspamBerghold.Net               Linux Bigot at Large
"Linux renders ships... Windows NT renders ships useless..."

2000\04\22@023658 by Sebastian Garcia

flavicon
face
Hi Peter,

Just wanna know where I can get more info on TCP/IP basic understanding, the
minimal for trying to do one of these uC-based email boxes. Can You point me
to some URL's?

Did You made anything in this field of uC plugged to the net?

TIA,

S.-


-----Original Message-----
From: Peter L. Berghold <peterSTOPspamspamspam_OUTberghold.net>

|Hi there folks,
|
|Just had to stick my nose into this subject. As a Unix professional I
|know a bit of what is involved in sending/recieving EMAIL both from a
|client side and the server side as I have been responsible for the care
|and feeding of this facility from time to time.
|
|To send EMAIL from a PIC assumes a couple of things:
|
|1) You

<SNIP>

2000\04\22@104414 by Dale Botkin

flavicon
face
On Sat, 22 Apr 2000, Sebastian Garcia wrote:

> Just wanna know where I can get more info on TCP/IP basic understanding, the
> minimal for trying to do one of these uC-based email boxes. Can You point me
> to some URL's?

Everything you ever wanted to know about SMTP: RFC 0821
TCP/IP requirements for attaching a host to the Internet: RFC1122

Both can be found at http://www.ietf.org/.

O'Reilly (http://www.ora.com/) also has some good books on the subject,
including Internet Core Protocols.

If there is a mail relay you can connect to that will allow your device to
send mail, you would need to be able to establish a TCP connection to port
25 and exchange text.  Implementing a real TCP stack in a PIC would be a
challenge...  you might want to consider running a script on your UNIX
host that will listen for UDP packets from your PIC and send the mail
itself.  A fairly simple Perl script would do the job, and UDP doesn't
require anywhere near the work that TCP does.

Dale
---
The most exciting phrase to hear in science, the one that heralds new
discoveries, is not "Eureka!" (I found it!) but "That's funny ..."
               -- Isaac Asimov

2000\04\22@124245 by Byron A Jeff

face picon face
On Sat, Apr 22, 2000 at 03:33:25AM -0300, Sebastian Garcia wrote:
> Hi Peter,
>
> Just wanna know where I can get more info on TCP/IP basic understanding, the
> minimal for trying to do one of these uC-based email boxes. Can You point me
> to some URL's?
>
> Did You made anything in this field of uC plugged to the net?

I'd like to point out that there may be a simpler way. The real problem in
all of this is TCP. TCP is a robost protocol that guarantees reliable
stream based end to end communication. Unfortunately this requires buffering,
flow control, sliding windows, and other mechanisms to enforce the gurantees
that TCP makes.

Simply put the average PIC doesn't have the resources to effectively do TCP.
And since the E-mail protocol runs on top of TCP, it won't be easy to do.

But there is another way: UDP. UDP is a protocol at the same level as TCP
but makes no promises whatsoever about delivery, order, flow control or
anything else. The great thing is that it makes it extremely simple. The UDP
header consists on nothing more that a short header that defines the source
and destination ports, length and checksum for the data. That's it. So your
application can choose which features of TCP are required for the application
instead of having to implement all the features that TCP requires.

So how can you use it? Not difficult fortunately. UDP has exactly the same
routability as any other internet packet. Your machine can dial up and
fire off UDP packets to anywhere on the internet. So what you do is set up
a server machine on the net somewhere that accepts UDP packets from the remote
uC machines, formulates E-mail, then sends the E-mail to it's final
destination.

I have two students currently doing a design project on the concept. They're
using SLIP as the underlaying IP layer due to its simplicity, and will be
firing off UDP packets to a server. The three most excellent things about
using SLIP/UDP are 1) The time/headache savings of buying into proven
technology. 2) The worldwide routability described above and 3) The simplicity
of writing servers, which consist of little more than opening a socket and
sending an receiving.

As for information of course the Internet RFCs are the main source.

BAJ

2000\04\22@140419 by Craig Gardner

flavicon
face
I have found a number of sites on using a pic for a web server and they implement
TCP check out the following sites.
http://www-ccs.cs.umass.edu/%7Eshri/iPic.html
http://www.chat.ru/~zhengxi/wwwpic/source.htm
http://www.mycal.net/wsweb/

Byron A Jeff wrote:

{Quote hidden}

2000\04\22@142123 by James Michael Newton

picon face
techref.massmind.org/tcpip

James Newton
spamBeGonejamesnewtonSTOPspamspamEraseMEgeocities.com
1-619-652-0593 phone

----- Original Message -----
From: Sebastian Garcia <KILLspamsgarciaspamBeGonespamTRON.FI.UBA.AR>
To: <EraseMEPICLISTspamEraseMEMITVMA.MIT.EDU>
Sent: Friday, April 21, 2000 23:33
Subject: Re: EMAIL from a PIC


> Hi Peter,
>
> Just wanna know where I can get more info on TCP/IP basic understanding,
the
> minimal for trying to do one of these uC-based email boxes. Can You point
me
> to some URL's?
>
> Did You made anything in this field of uC plugged to the net?
>
> TIA,
>
> S.-
>
>
> {Original Message removed}

2000\04\22@161324 by William Chops Westfield

face picon face
   Simply put the average PIC doesn't have the resources to
   effectively do TCP.  And since the E-mail protocol runs on
   top of TCP, it won't be easy to do.

   But there is another way: UDP. UDP is a protocol at the same
   level as TCP but makes no promises whatsoever about delivery,
   order, flow control or anything else.

If you're going to go unreliable, you might a well go all the way to
just running ascii, especially since you're probably talking about SLIP
or PPP (Internet over async) as the physical layer anyway.  As far as I
know, any "NAS" that supports SLIP also supports telnet.  So the
procedure for sending mail would look like:

1) login as ascii "user."
2) send "telnet mailserver 25" to have server establish a tcp connection
  to the mail server.
3) send plain text SMTP negotiations:
       helo smallpic
       mail from:<>
       rcpt to:<@spam@billwww@spam@spamspam_OUTcisco.com>
       data
       Date: 1-jun-2000 1500
       Subject: Meltdown imminent

       Temperature of 120F present at sensor 1
       Temperature of 100F present at sensor 2
       Temperature of 80F present at sensor 3
       .
       quit

The only reasons for using UDP with some sort of translating gateway
would be if your physical interface is datagram based (ie ethernet), or
if you really WANT the thing to have an IP address.  Otherwise, as soon
as you insert a tranlating gateway, you might as well have it translate
the data at the most convenient level possible.  SMTP uses an ascii
steam, PICs have no trouble generating an ASCII stream.  Poof.  Done.

BillW

2000\04\22@181716 by Brian Gracia

flavicon
face
Try this link

http://www.mycal.net/wsweb/design/

Your Welcome,
Brian
********************************************
Better Produce through Better Control
********************************************

2000\04\23@122756 by Byron A Jeff

face picon face
On Sat, Apr 22, 2000 at 10:51:43AM -0700, Craig Gardner wrote:
> I have found a number of sites on using a pic for a web server and they implement
> TCP check out the following sites.
> http://www-ccs.cs.umass.edu/%7Eshri/iPic.html

No source code. Operation has never been substantiated.

> http://www.chat.ru/~zhengxi/wwwpic/source.htm

Didn't give a detailed code review. Looks legit but with extremely limited
TCP functionality.

> http://www.mycal.net/wsweb/

Uses an external TCP stack.

Note I didn't say it couldn't be done. I said it would be difficult to do
as evidenced by the code in the second link you posted.

The question I'm asking is other than coolness value and the fact that
pre-existing clients and servers exists for WWW and SMTP protocols, exactly
what benefit does a PIC gain by implementing a limited TCP stack over a
fully functioning UDP stack? The downside is the complication of the software
required on the PIC.

The only upgrade I'd really consider is PPP over SLIP simply because PPP
is way more widely deployed over SLIP at most Internet POPs. But fortunately
uChip has an appnote describing such an implementation.

UDP is easy to implement, gives the same routability as TCP, and makes
the server side applications easy to implement and much more reliable
applications (not communications) because the majority of the stack is well
tested.

I'm just pointing out what I see as an overspecification of the problem.
Shoving all that functionality into a limited PIC complicates the solution.
It just seems that having a PIC communcation directly with an E-mail server
as opposed to it using an intermediate server that translates PIC UDP packets
into E-mail make development more difficult and less reliable. The first and
only oder of business is to get the PIC on the net. After that intermediate
servers with more capable tools and functionality can mediate between the
now connected PICs and the rest of the net world.

BillW had the ultimate expression of that by proposing to ditch IP completely
in favor of ASCII. But considering my next project is to attach a PIC to a
parallel to ethernet adapter, which I got from eBay for $12, the power of
using a standard communications stack presents itself. Simply by writing a
new hardware driver, all the UDP code which my application will use to
communicate instantly starts working on ethernet.

The possibilities are endless.

BAJ

2000\04\23@130948 by Richard Beales

flavicon
face
Hi all,

I've got a really basic 16F84-based web server project on my site at
http://www.rmbeales.fsnet.co.uk/, or just grab the zip package from
http://www.rmbeales.fsnet.co.uk/files/ie/picserv1.zip.

Just for fun and not much (any :-) ) practical use, but it does work and is
written in C so not too cryptic.

cheers,
Rich.

{Original Message removed}

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