Hello, two days ago I was working on I2C communication between two Arduino. It was working fine. Then on the next day, suddenly it stopped working. The only thing that changed was I updated Windows 10 using Windows Update. Could this be the cause? Anybody has similar problem the past two days?
Which Arduinos?
Did you change anything; or even recompile the same code and upload? If you changed something, roll back to the version that worked.
Could you no longer compile? Or did the I2C communication fail? Or ...
It sounds unlikely; I'm forced to use Linux at this moment (not really a punishment 
) but I never had Windows 10 updates break anything Arduino related.
don't understand how that could have been affected..
had something strange on windows 11 last week..
i didn't manually do windows updates but they happen..
i was coding an esp32cam and found that day was getting an error when trying to open the port..
A device attached to the system is not functioning..
something like that, long story short..
had to downgrade the CH341 usb drivers which had been updated..
what exactly is not working??
good luck.. ~q
I have come across this before but it has mainly been the port driver which you indicate may have been solved.
-
Due and Mega 2560 R3
-
I have an Arduino IDE for the Master and another one for the Slave. I can see the outputs of both. I think for both, I pressed the upload button which seems to always re-compile even there is no change in the code
-
I2C communication suddenly failed. When it was working, I entered command from the Master and the Slave responded. Now the Slave behaves as if there is no command from the Master
The Due is a 3.3V board; the Mega is a 5V device. Did you use level converters on the bus between the Due and the Mega. If not, you might have damaged the Due's I2C bus (and maybe more).
I would start by adding level converters (if not done so yet) and running some simple I2C tests.
Is there any good way to test if I have damaged the Due's I2C bus (and maybe more)? Is there some kind of self-test?
I did not use level converters but I directly connected the Due's SCL and SDA ports to the respective ones on the Mega 2560 R3. I used them for 1-2 hours and they could communicate with each other without issue. If the 3.3V - 5V difference can damage the Due's I2C, shouldn't that be instantly rather than working fine for 1-2 hours on one day and got damaged on the second day?
I don't know for sure. Maybe write a test script for both the Due and the Mega. On the Due, run the I2C scanner example, make the Mega a simple slave.
Not necessarily. I had a computer with an embroidery machine connected to it. The computer was also connected to a phone line for internet access. Lightning hit the phone line, computer basically died and the embroidery machine took a hit but was still usable. Embroidery machine symptoms were intermittent connectivity issues with the (new) computer; after 6 months the embroidery machine was dead.
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.