recommend as an alternative
Do you actually need a "very large" single I2C transaction? How big, exactly? Do you have a receiver in mind that can receive the data without NAKing? Or do you need a receiver implementation as well? It looks like you can prevent the "Stop" from being sent in endTransmission(), which should give you the same effect as one long packet even though you're calling beginTransmission() multiple times. How many more clues do you want, or do you just want someone to write the code for you so that you can focus on ?analyzing the bitstream on OtherDevice? or whatever?
Preface: I used (ie, cut and pasted) the sketch shown in the video previously linked into this thread. I did not write the sketch but in the process of using it I discovered that wire.write has a 32 Byte limitation that is perhaps not so well documented. I wrote a post asking for suggestions on how to get around the 32 Byte limitation. To be clear, I did not ask for any "clues". As explained multiple times, I don't have much experience with either I2C or Arduino code. And btw in case it's not clear yet, I don't want "clues".
Now to try to answer your questions: Yes, making a relatively large single transaction (transmission) is the objective (I get what an Ack and Nak are, but I have no idea how to get two Unos to manage Acks and Naks). If the code will run by preventing the "Stop", that's swell. I don't care - I'm just trying to make Bytes move via I2C from one Uno to another.
As previously mentioned in this this thread, the objective is to be able to transmit thousands of Bytes. So, let's say 40k Bytes plus or minus. (I can of course insert the 40k Bytes - I'm not that clueless
, so no need for anyone to do that.)
To be clear, the preference, if possible, would be to send the Bytes from one Uno as the master to the second Uno as the slave - so yes, that would take code for the slave Uno to go with code for the master Uno - perhaps along the lines of the sketch shown in the video posted earlier in this thread but without the 32 Byte limitation of wire.write.
Yes, I just want to use the code to make the I2C transmissions between the Unos so as to have a testbed which in turn will enable me to focus on better learning the operation and better understand the performance of an oscilloscope's logic analyzer functions. If anyone has ever seen an education demo board, that is sort of what I am looking to establish with this project. I don't really want to code the demo board, but if I had a sketch (or really clear clue-free instructions on how write the code) then I could load the code onto a couple Unos, and that would be great. If in the process, I learn some Uno coding that's A-OK, but it's not the number one objective for this project.
So yes, if someone wanted to write the code I would not be too proud too use it. (Although, if it took more than 5 or 10 minutes or about the time it takes to read and write these posts, I'd say forget it unless you enjoy doing such coding.)
I realize Arduino is not everyone's first choice but Unos happen to be something I have available and I'd like to use them if possible. So if you or someone knows of such a master/slave I2C sketch on the web and you can post a link to the sketch would be great, or if you or someone wanted to write such a sketch, cool. If not, no worries.