Using the Arduino Ethernet shield with AMICUS18 (Joint forum project?)

[pedja089]

Hi,
Nice work. But i think that you have some mistake.
You wrote

W5100_Gateway[0] = 192
W5100_Gateway[0] = 168 
W5100_Gateway[0] = 1 
W5100_Gateway[0] = 254

If i understand it should be

W5100_Gateway[0] = 192
W5100_Gateway[1] = 168 
W5100_Gateway[2] = 1 
W5100_Gateway[3] = 254

[HenrikOlsson]

Ah, yes of course, thanks for spotting that. It should be OK in the example project attached to previous message.
I wish I could go back and fix it in the post but I can't :-(

/Henrik.

[pedja089]

Maybe you should be moderator on AMICUS18 section...

[mackrackit]

The code in post #24 is fixed.

[Demon]

Henrik, Bravo!

Robert

[Heckler]

Hey Henrik (and others),
I just received my Amicus18 and the Arduino Ethernet Shield...

I have not completed the modifications yet... but am starting that tonight.

I assume your example code is intended to overwrite the Amicus boot loader? (I did read the amicus with my PicKit2 and save the hex file, so I think I can go back to the boot loader if I want.)

How has your progress been?? Where are you hoping to go with your experiments?

I would like to end up with a device that...
I can log into and read or view values like temperature, voltage status bits etc.
That could possible email me or text me if a given value changes beyond a set point.
Be able to remotely change values and bits.
?? other things yet un thought up.

I do not have any experience programing ethernet values via a PIC.

I have plenty of experience Pinging... seting static IP... subnet mask... Telnet... etc. From a Windows XP machine.

Thanks for any help, direction and code examples you (and others) can give.

[Heckler]

Henrik,

My Amicus board came with a 18F25K20 NOT the 18F25K22 that you mention in your article. I see the difference is 3.3v vs 5v. Am I going to need to get the K22 chip?

Thanks

[HenrikOlsson]

Hi Dwight,
Wonderful, please join the fun!

No, I wrote 25K22 in error, it's meant to say 25K20 so you're fine - just use the AMICUS18 as it is. (You CAN definitely use the 25K22 if you want but I think you'd need to run it on 3.3V, I don't remember if the W5100 has 5V tolerant inputs). I'd like to stress, again, that you don't need an AMICUS18 at all, the routines will work with ANY PIC that has a MSSP module.

No, don't overwrite/replace the bootloader. Add DEFINE LOADER_USED 1 at the top and set MCSP (or whatever you use) up to use the AMICUS Loader. It'll be a lot faster than re-flashing with the PicKit2.

Progress is good but a bit slow. This is all new territory for me, researching protocols, reading RFC's, trying, failing, trying again.

The goal is basically a set of routines, lets call it a "framework", which you can use to build the application you need. It won't do everything but it'll provide the base functionallity upon which we can write the actual application. At the moment I have the basic routines used to communicate with the W5100 and a couple of support routines to make using sockets and moving data in and out of easier. This is allready presented and published in the thread.

I have DHCP (Dynamic Host Configuration Protocol) working - also presented in the thread.
I have SNTP (Simple Net Time Protocol) working, (derived from Charles really accurate clock code but without using LONGs)
I have SMTP (Simple Mail Transfer Protocol) (with authentication) basically working (it sends mails) but it needs more work to increase the robustness and improve the interface to the main application.

When I'm happy with the SMTP code I think I'll take on DNS and if/when that works I think I'll try to make some kind of HTTP server "building block" but I'm not sure it'll work since each and every application will be different. Perhaps it's just better to write that from scratch - I don't know. The biggest hurdle, as I see it, is how to handle a "filesystem" of some sort on the PIC. A single, very simple web-page is not a problem but it gets complicated when you want multiple pages, perhaps images etc. Actually storing them (SD-card, SPI-flash, I2C-EEPROM whatever) is one part, keeping track of them (ie. the filesystem) is another and how to get them INTO the memory device is a third.

The application you envision is pretty much what I had in mind when I started but I'm trying to write the code as generic as possible. That way you can included the functionallity you need and leave the rest out. With the code and examples already presented you should be able to get DHCP and a simple web-server going. Perhaps you'll get a general HTTP server building block going before I get to it.

Keep us posted on your progress!

/Henrik.