Closed GoogleCodeExporter closed 8 years ago
I'm confused, is the problem with OneWire or I2C? I2C uses the TwoWire ( or
more commonly just called 'Wire' ) There is a library for Dallas OneWire as
well.
I2C/Wire operation requires a patch to the library if you want to use the
software pull ups, see here:
http://ryanmsutton.com/2011/11/updated-dev-enviroment/ You can also use
hardware pull up resistors on the I2C bus and not modify the library.
I would guess it is a similar issue with the OneWire protocol, though OneWire
has always worked best with hardware pullups.
Original comment by sutt...@gmail.com
on 4 Mar 2012 at 2:58
Well, let me put the simple way :)
I download OneWire 2.1 from http://www.pjrc.com/teensy/td_libs_OneWire.html
I compile on Arduino and I get the messages in the picture below.
Original comment by noseblee...@gmail.com
on 4 Mar 2012 at 9:55
Attachments:
Don't have any hardware to test with but all example code in above library
compiles on a clean install of arduino0023 and sanguino0023r3. The error
messages above likely indicate corrupted environment since any error on
pins_arduino.h:59 should also occur on pins_arduino.h:58 (with the exception of
duplicating globals MOSI,MISO,SCK)
Original comment by sutt...@gmail.com
on 5 Mar 2012 at 3:00
Attachments:
I started again with a clean install of arduino0023 and sanguino0023r3.
Problem insists. With OneWire 2.0 problem is resolved.
I believe my code somehow causes an error with OneWire 2.1.
Can you take a look and tell me what I'm doing wrong?
Original comment by noseblee...@gmail.com
on 5 Mar 2012 at 5:32
Attachments:
Cleaning up old comments, excuse the noise.
Original comment by sutt...@gmail.com
on 6 Sep 2012 at 12:20
Original issue reported on code.google.com by
noseblee...@gmail.com
on 26 Feb 2012 at 8:07