Wiserver and I2C conflict

Discussions related to the WiServer add-on code for WiShield. WiServer is a friendly, easy-to-use front end for webserver and webclient usages.

Moderator: shard7

Wiserver and I2C conflict

Postby kolment » Thu Mar 25, 2010 8:49 am

Hello everyone,

I would like to know if someone was able to get the Wiserver sketch and a I2C wire.h library to work together. When i call wire.begin() to interface my RTC DS 1307, the Wiserver doesnt work at all . I would like to know if Wiserver.h and wire.h are compatible libaries


Cheers !
kolment
 
Posts: 6
Joined: Mon Nov 23, 2009 1:27 am

Re: Wiserver and I2C conflict

Postby gordonendersby » Thu Mar 25, 2010 9:19 am

Yes I have the RTC and Wishield ver 1.0 working together.
But the DS1307 uses the 2 wire interface(wire.h) not I2C.
You should be able to cobble the 2 sets of example code together and get something working.
Why not post your code.

But as an aside Im also using the DS18S20 temperature sensors on I2C as well.

Gordon
gordonendersby
 
Posts: 40
Joined: Tue May 12, 2009 7:43 am

Re: Wiserver and I2C conflict

Postby kolment » Thu Mar 25, 2010 12:40 pm

Hmmm k, i dont have my code with me ( im at work ill post when i get to my comp)

basically i wana use the Wiserver library to make a website on nmy local network with the router, and when i click on some link it turns on and off some leds. Also i want to use the DS18S20 and DS1307 on the side. When i call Wire.begin() sa fourre le chien!
kolment
 
Posts: 6
Joined: Mon Nov 23, 2009 1:27 am

Re: Wiserver and I2C conflict

Postby nimbusgb » Tue Apr 06, 2010 2:49 pm

WiServer and 3 I2C devices working together on a Mega board. 2 I2C devices are on the same address so I am having to multiplex them but it all works fine.
nimbusgb
 
Posts: 25
Joined: Fri Mar 26, 2010 8:13 am

Re: Wiserver and I2C conflict

Postby tiagop20 » Mon May 31, 2010 3:59 pm

I have a similar problem. I'm trying to get Wiserver and RFIDuino to work in a Mega and i can't. RFIDuino uses I2C and Wishield interrupt is on digital pin 2. Any suggestions? Thanks for any kind of help.
tiagop20
 
Posts: 3
Joined: Wed Mar 31, 2010 8:21 am

Re: Wiserver and I2C conflict

Postby GregEigsti » Mon May 31, 2010 4:17 pm

The WiShield is switchable between interrupt pin 2 or 8. I think if you change to interrupt pin 8 (non default) you will have to tweak the WiShield driver code to let it know. Not sure, never done it myself.

Greg
Check out the wiki!
uIP Stack Docs
Compatible Access Point List
WiShield user contrib branch - DNS, DHCP, AP Scanning, bug fixes, etc.
SlackLab.org - My geek projects blog.
User avatar
GregEigsti
 
Posts: 1067
Joined: Sun Aug 02, 2009 5:23 pm
Location: Sammamish WA USA (near Seattle)
  • Website


Return to WiServer

Who is online

Users browsing this forum: Exabot [Bot] and 1 guest