Forums

Sending email with embedded device

Started by rush February 5, 2008
I am looking for some help with development of a consumer product. One
aspect of the project requires the embedded device to send and receive
an email using an internal dial-up modem.
Emails sent and received will contain jpeg images.

Can anyone recommend a good starting point for micro or chipset
tailored for such an application.

Thanks
On 6 feb, 02:36, rush <rushi...@gmail.com> wrote:
> I am looking for some help with development of a consumer product. One > aspect of the project requires the embedded device to send and receive > an email using an internal dial-up modem. > Emails sent and received will contain jpeg images. > > Can anyone recommend a good starting point for micro or chipset > tailored for such an application. > > Thanks
Yes, you can start with the WEB SERVER example using a PPC/Viertex 4... it's in xilinx web page /embedded examples... http://www.xilinx.com/ise/embedded/edk_examples.htm Salud...
Le Tue, 05 Feb 2008 17:36:17 -0800, rush a &eacute;crit:

> I am looking for some help with development of a consumer product. One > aspect of the project requires the embedded device to send and receive > an email using an internal dial-up modem. > Emails sent and received will contain jpeg images. > > Can anyone recommend a good starting point for micro or chipset > tailored for such an application. > > Thanks
Hi ! With any Linux embedded platform you can 1- telnet smtp.xxx.com 25 (for sending email) 2- telnet pop.xxx.com 110 (for email receiving) putting it together in a small shell script is quite easy. -- HBV
In article <e1a00d18-d707-4fb8-990f-b0710e3e689b@v67g2000hse.googlegroups.com>,
rush  <rushik77@gmail.com> wrote:
>I am looking for some help with development of a consumer product. One >aspect of the project requires the embedded device to send and receive >an email using an internal dial-up modem. >Emails sent and received will contain jpeg images.
Are you looking for suggestions for hardware as well as software? Have you decided on any specifics? Sending email is probably the least of your concerns - anything with a TCP/IP stack could do that. Depending on how embedded your device has to be, there are plenty of freely available OSes (Linux, FreeBSD, NetBSD) that support everything in the world. Do you have a target price for your consumer device? That's what will probably be the biggest factor in determining hardware, and thus software. If you're sending JPEGs, does that mean there will be a camera connected to this box? If so, what kind of interface does the camera need?
>Can anyone recommend a good starting point for micro or chipset >tailored for such an application. > >Thanks
Most chipsets that can support TCP/IP can support your needs. But you really need to look at your target costs first. There are plenty of nice embedded system hardware vendors that can offer you a platform to prototype your device on, if not build a shippable product on. We need more details to be more helpful. Patrick ========= For LAN/WAN Protocol Analysis, check out PacketView Pro! ========= Patrick Klos Email: patrick@klos.com Klos Technologies, Inc. Web: http://www.klos.com/ ============================================================================
On Feb 6, 5:26=A0am, pk...@osmium.mv.net (Patrick Klos) wrote:
> In article <e1a00d18-d707-4fb8-990f-b0710e3e6...@v67g2000hse.googlegroups.=
com>,
> > rush =A0<rushi...@gmail.com> wrote: > >I am looking for some help with development of a consumer product. One > >aspect of the project requires the embedded device to send and receive > >an email using an internal dial-up modem. > >Emails sent and received will contain jpeg images. > > Are you looking for suggestions for hardware as well as software? =A0Have =
you
> decided on any specifics? =A0Sending email is probably the least of your > concerns - anything with a TCP/IP stack could do that. > > Depending on how embedded your device has to be, there are plenty of freel=
y
> available OSes (Linux, FreeBSD, NetBSD) that support everything in the wor=
ld.
> > Do you have a target price for your consumer device? =A0That's what will > probably be the biggest factor in determining hardware, and thus software.=
> > If you're sending JPEGs, does that mean there will be a camera connected t=
o
> this box? =A0If so, what kind of interface does the camera need? > > >Can anyone recommend a good starting point for micro or chipset > >tailored for such an application. > > >Thanks > > Most chipsets that can support TCP/IP can support your needs. =A0But you > really need to look at your target costs first. =A0There are plenty of > nice embedded system hardware vendors that can offer you a platform to > prototype your device on, if not build a shippable product on. =A0We need > more details to be more helpful. > > Patrick > =3D=3D=3D=3D=3D=3D=3D=3D=3D For LAN/WAN Protocol Analysis, check out Packe=
tView Pro! =3D=3D=3D=3D=3D=3D=3D=3D=3D
> =A0 =A0 Patrick Klos =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 E=
mail: patr...@klos.com
> =A0 =A0 Klos Technologies, Inc. =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Web: =A0htt=
p://www.klos.com/
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=AD=3D thanks Patrick The target cost is going to be an issue. Hoping to find a suitable processor for ~$12 - $18 in volume of 1k pieces (including external RAM and Flash) Processor needs to capable of reading/writing JPEG to SD card, transmitting /receiving JPEG via email and preferably generate a video signal to output images to a monitor / TV I have found modem modules [Silicon Labs Si2457 + Si3008] that take care of the email portion leaving a basic dsp processor free for video but they cost around $25. Maybe a higher dollar processor and dumb modem would be a better way to go? Any thoughts or is this budget unfeasible? thanks
On Feb 6, 5:01=A0am, Habib Bouaziz-Viallet <ha...@rigel.systems> wrote:
> Le Tue, 05 Feb 2008 17:36:17 -0800, rush a =E9crit: > > > I am looking for some help with development of a consumer product. One > > aspect of the project requires the embedded device to send and receive > > an email using an internal dial-up modem. > > Emails sent and received will contain jpeg images. > > > Can anyone recommend a good starting point for micro or chipset > > tailored for such an application. > > > Thanks > > Hi ! > > With any Linux embedded platform you can > > 1- telnet smtp.xxx.com 25 (for sending email) > 2- telnet pop.xxx.com 110 (for email receiving) > > putting it together in a small shell script is quite easy.
While that works in theory, many mail servers drop connections from senders that appear to be sending the SMTP commands keystroke-by- keystroke (on the fairly valid assumption that it's not talking to a "real" email program or server, and there's little likely good to come from accepting mail from such a source). But once you have a TCP/IP stack and a connection, sending email is pretty trivial.
"rush" <rushik77@gmail.com> wrote in message 
news:fae29215-4754-450e-8a83-f8bb415c2f63@e4g2000hsg.googlegroups.com...
>>
The target cost is going to be an issue. Hoping to find a suitable processor for ~$12 - $18 in volume of 1k pieces (including external RAM and Flash) Processor needs to capable of reading/writing JPEG to SD card, transmitting /receiving JPEG via email and preferably generate a video signal to output images to a monitor / TV I have found modem modules [Silicon Labs Si2457 + Si3008] that take care of the email portion leaving a basic dsp processor free for video but they cost around $25. Maybe a higher dollar processor and dumb modem would be a better way to go? Any thoughts or is this budget unfeasible? << You said earlier:
>> One aspect of the project requires the embedded device to send and >> receive an email using an internal dial-up modem. <<
Therefore it doesn't *have* to talk TCP/IP. You could consider offloading the infrastructure aspect to a dedicated server on a given phone number (or numbers) which accepts fairly simple serial data, and generates an email. Your costs then would be centralised, rather than distributed on every unit. Otherwise, which phone number is your modem going to call? An ISP? Steve http://www.fivetrees.com
Le Thu, 07 Feb 2008 15:06:35 -0800, robertwessel2@yahoo.com a &eacute;crit:

> On Feb 6, 5:01&nbsp;am, Habib Bouaziz-Viallet <ha...@rigel.systems> wrote: >> Le Tue, 05 Feb 2008 17:36:17 -0800, rush a &eacute;crit: >> >> > I am looking for some help with development of a consumer product. One >> > aspect of the project requires the embedded device to send and receive >> > an email using an internal dial-up modem. >> > Emails sent and received will contain jpeg images. >> >> > Can anyone recommend a good starting point for micro or chipset >> > tailored for such an application. >> >> > Thanks >> >> Hi ! >> >> With any Linux embedded platform you can >> >> 1- telnet smtp.xxx.com 25 (for sending email) >> 2- telnet pop.xxx.com 110 (for email receiving) >> >> putting it together in a small shell script is quite easy. >
Hi !
> > While that works in theory, many mail servers drop connections from > senders that appear to be sending the SMTP commands keystroke-by- > keystroke (on the fairly valid assumption that it's not talking to a > "real" email program or server, and there's little likely good to come > from accepting mail from such a source).
Last year we have been delivering many custom boards (35-45) based on ETRAX100LX and AT91RM9200 with an embedded app sending one mail every day (cron - ash shell script). AFAIK no problems have been reported with opening telnet session on a remote mail server. Abviously this is not an absolute proof of concept, the right way is to consider SMTP, POP and MIME RFC specs. May be these are already implemented in a GPL library.
> But once you have a TCP/IP stack and a connection, sending email is > pretty trivial.
-- HBV
In article <fae29215-4754-450e-8a83-f8bb415c2f63@e4g2000hsg.googlegroups.com>,
rush  <rushik77@gmail.com> wrote:
>> Most chipsets that can support TCP/IP can support your needs. =A0But you >> really need to look at your target costs first. =A0There are plenty of >> nice embedded system hardware vendors that can offer you a platform to >> prototype your device on, if not build a shippable product on. =A0We need >> more details to be more helpful. > >thanks Patrick > >The target cost is going to be an issue. >Hoping to find a suitable processor for ~$12 - $18 in volume of 1k >pieces (including external RAM and Flash) >Processor needs to capable of reading/writing JPEG to SD card, >transmitting /receiving JPEG via email and preferably generate a video >signal to output images to a monitor / TV > >I have found modem modules [Silicon Labs Si2457 + Si3008] that take >care of the email portion leaving a basic dsp processor free for video >but they cost around $25. Maybe a higher dollar processor and dumb >modem would be a better way to go? > >Any thoughts or is this budget unfeasible?
How are you making out with this project? Have you checked out the UBICOM (http://www.ubicom.com/) line of processors? They should be about $15 or less for your quantities. There's also Luminary Micro (http://www.luminarymicro.com/) which could be as low as $8 per. Each has their pros and cons. Let us know if you have any questions or want to know our experiences with these 2 processor families. Patrick ========= For LAN/WAN Protocol Analysis, check out PacketView Pro! ========= Patrick Klos Email: patrick@klos.com Klos Technologies, Inc. Web: http://www.klos.com/ ============================================================================
On Feb 5, 8:36 pm, rush <rushi...@gmail.com> wrote:
> I am looking for some help with development of a consumer product. One > aspect of the project requires the embedded device to send and receive > an email using an internal dial-up modem. > Emails sent and received will contain jpeg images.
Whose are you dialing in to? 1) A conventional 3rd party ISP? In that case you'll need to do it in a standard way (and you'll need an ISP that you send trafffic to port 25, most would block that). Still, you can really minimize the process by simplifying and pre-assembling most of the message, then just inserting the addresses and mime-encoded picture on the fly. 2) Modems connected to your own server? In that case you can send anything you want over the phone line, it doesn't necessarily have to be an 'email' but could be some setup data and then transfer the jpeg using xmodem or something. This has infrastructure cost, but you can move a lot off the software complexity to your server. 3) Dialing into a 3rd party ISP then getting at your own sever over the internet, and having your server turn innocent-looking tcp data into an email message - basically your own mini-webmail system only designed to be used by your embedded device rather than a human user. Gets around the problem of ISP's blocking smtp traffic on port 25. You still have to maintain servers but not modem pools.