Skip to main content
10 events
when toggle format what by license comment
Nov 20, 2017 at 4:36 history edited dda CC BY-SA 3.0
added 47 characters in body
Nov 18, 2017 at 1:16 vote accept Marcello B.
Apr 13, 2017 at 12:33 history edited CommunityBot
replaced http://electronics.stackexchange.com/ with https://electronics.stackexchange.com/
Apr 1, 2015 at 15:45 comment added Edgar Bonet I agree knowing the physical layer can help, but for using I²C you only need to know that addresses and data are multiplexed on the same lines, which simplifies the cabling (only 2 wires). On the software side, it's really simple: see the Master Writer/Slave Receiver Arduino tutorial, which can be trivially expanded to many slaves just by using different slave addresses.
Apr 1, 2015 at 11:55 comment added aaa I also said that in the 3rd 'paragraph', though adressing isn't standard in the uart protocol? Or well you will have to handle it software. With SPI you simply have a slave select pin that selects which slave to talk to. I didn't know that 9-bit protocol is for adressing? Or well I don't believe it's defined so in the standard? But yes, an extra bit could help. You could also send one byte with the address/setting and then send (an)other byte(s) with the message. Then on each slave you should check the first byte, and only handle the second when neccesary.
Apr 1, 2015 at 11:25 comment added Ignacio Vazquez-Abrams UARTs don't need to be single P2P; AVRs do support a form of multiple slave using a 9-bit protocol.
Apr 1, 2015 at 6:16 comment added aaa Ah, I see, haven't yet used I²C with arduino, but for a beginner, but in general it's better to know the hardware before you start on the software. In this way you know what to do and how to debug it. But I can imagine that arduino has steady/easy libraries for this. But same is for setting up serial connection in arduino?
Apr 1, 2015 at 6:15 history edited aaa CC BY-SA 3.0
added 597 characters in body
Mar 31, 2015 at 20:23 comment added Edgar Bonet I²C is somewhat complicated at the physical level, but all that complication is handled by the hardware (the TWI interface of the AVR chips). At the user level, it may be the simplest to use: only two wires and no need to match port configurations (baudrate, parity, stop bit(s)...).
Mar 31, 2015 at 19:25 history answered aaa CC BY-SA 3.0