Dnia 08.04.2012 o 16:56 Patryk <p4tr...@o2.pl> Patryk <p4tr...@o2.pl> napisał(a):
There was a bug when using --i2c=ALL:ALL which Paul corrected. Now it works and enumerates all /dev/i2c in search for suitable 1-wire master. However the problem in my case was that I mistakenly used 60 Ohm resistors too pull up SDA and SCL lines. They are very small and I read the color code wrong. The resistors should be around 4.7K to 10K. On this page there is a good tutorial how to connect i2c to VGA. http://flipthatbit.net/2011/04/interfacing-i2c-the-easy-way/ This is the vga connector plug. So if connect wires directly do a VGA socket on a computer it's "reversed"(look at the schematic at the end it's for the socket in the PC) http://flipthatbit.net/wp-content/uploads/2011/04/vga2i2c.jpg I just used copper wires from a telephone cable sticked directly to the socket. First I attached +5V and GND and double checked the polarity with multimeter. The I secured it with sticky tape and connected SDA and SCL the same way. You can also cut an old monitor cable because those pins are connected. You must have in mind that the power supply of those +5V is limited It probably won't be enough to power more that the DS2482 and 1 DS18B20. So if you want to use it for bigger networks You have to get power from elsewhere(maybe from molex plugs directly from power supply unit). If we have all wires connected as in the vga2i2c.jpg we can connect DS2482-800. You can also use others i2c 1-wire masters. http://para.maxim-ic.com/en/search.mvp?fam=1wire&tree=master They all are in SMD packages You can buy TSOP to DIL converters and solder DS2482 to it and then you can use it on a solderless breadboard like I did. If everything is connected. You have to load the i2c-dev module modprobe i2c-dev If you run dmesg there should be a line like this "i2c /dev entries driver" and /dev/i2c-... devices should appear. In my case there are a dozen of them. We have to choose the right one or we can pass the parameter --i2c=ALL:ALL but the current(p14) version has some problems with it. The i2cdetect is in i2c-tools on Ubuntu. i2cdetect -l This should output smth like this i2c-0 unknown i915 gmbus disabled N/A i2c-1 unknown i915 gmbus ssc N/A i2c-2 unknown i915 GPIOB N/A i2c-3 unknown i915 gmbus vga N/A i2c-4 unknown i915 GPIOA N/A i2c-5 unknown i915 gmbus panel N/A i2c-6 unknown i915 GPIOC N/A i2c-7 unknown i915 gmbus dpc N/A i2c-8 unknown i915 GPIOD N/A i2c-9 unknown i915 gmbus dpb N/A i2c-10 unknown i915 GPIOE N/A i2c-11 unknown i915 gmbus reserved N/A i2c-12 unknown i915 gmbus dpd N/A i2c-13 unknown i915 GPIOF N/A i2c-14 unknown DPDDC-B N/A i2c-15 unknown DPDDC-C N/A i2c-16 unknown DPDDC-D N/A We are interested with i2c-X where is vga. In my case it's i2c-3. Then we simply run owfs /opt/owfs/bin/owfs --i2c=/dev/i2c-3 /mnt/owfs This is the schematic http://www.fotosik.pl/pokaz_obrazek/pelny/ce8286961892e6fc.html I have tested it on two laptops. One with Intel card and an old one with Radeon X600. -- p4trykx PS I also made some progress with I2c-usb converter which I plan to eventually use with DS2482-800. ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
