If the transfer might sometimes be faster or earlier than the slave, Arduino 2, can use the data, then a buffer would be some RAM in the receiving (slave, Arduino 2) ATmega. It is the same number of pins as would be used by any synchronous shift-register based solution using external chips the ATmegas on-board SPI peripheral is designed to implement the same mechanism. This requires at least two pins, clock and MOSI, between Arduino 1 and Arduino 2. The simplest solution is to connect the Arduinos' ATmega SPI peripherals together, Arduino 1 as master, and Arduino 2 as slave. You're outline diagram suggests that there is only a small amount of data in each transfer, but even that is not clear. over what distance is the transfer going to happen, inches (cm),.Sender and receiver, is 20% available, or 10µs/byte, can either orīoth ends 'block' waiting for a transfer? how much CPU overhead is acceptable to achieve the data rate on.how many Arduino pins are available to implement the transfer.Possibility that it will be unavailable or could lose data, and so will the 'slave' always be ready to receive data, or is their a can either end initiate a transfer can Arduino 2 request data, is the transfer one way or are their some use-cases which require.is the data bit or byte orientated, and is it arbitrary binary?.latency - how long can the delay be between sending and receiving data?.
Data rate - how fast does the data need to be transferred?.
Some examples of the type of detail which may be important, in no particular order, to answer the question: However, outlining one of the options might help you understand the detail that an answer needs. As Andy Aka's comment says, there is very likely more to this than a single pin for sending and receiving data, and currently the question is missing important detail.
0 kommentar(er)
