Stump
- 18th February 2005, 01:33
Greetings eh!
Firstly Thanks to all users of this forum.
All the issues I encountered over the past 6mo
were solved from postings on this forum.
A special thanks to Mel... MN1307.txt demonstrated
a lot more than just reading and setting an RTC.
(my own similar program was more than 2x in size)
Now to business..
A master control using 18F6720 is to send and receive data from up to 12 slave pics
(possibly 18F252) located up to 5 meters from the master using I2C.
Each slave is located in a seperate enclosure and will be opto isolated.
1) Can the master control have more than one I2C bus?
one for on board accessories RTC,eeprom,etc,
and a second buffered i2c bus to talk to the slave modules.
ref... i2cslave.bas & i2cmast.bas
2) What exactly does "DEFINE I2C_HOLD" do?
2a) does this affect the hardware i2c or the software i2c or both
2b) will this affect the use of RTC and eeprom on the software controlled bus
3) would RS485 or other be a better choice?
Thanks Kindly
Ron
Firstly Thanks to all users of this forum.
All the issues I encountered over the past 6mo
were solved from postings on this forum.
A special thanks to Mel... MN1307.txt demonstrated
a lot more than just reading and setting an RTC.
(my own similar program was more than 2x in size)
Now to business..
A master control using 18F6720 is to send and receive data from up to 12 slave pics
(possibly 18F252) located up to 5 meters from the master using I2C.
Each slave is located in a seperate enclosure and will be opto isolated.
1) Can the master control have more than one I2C bus?
one for on board accessories RTC,eeprom,etc,
and a second buffered i2c bus to talk to the slave modules.
ref... i2cslave.bas & i2cmast.bas
2) What exactly does "DEFINE I2C_HOLD" do?
2a) does this affect the hardware i2c or the software i2c or both
2b) will this affect the use of RTC and eeprom on the software controlled bus
3) would RS485 or other be a better choice?
Thanks Kindly
Ron