Just finished I2C parts 1, 2, and 3. At the end of part 3 I heard a part 4 was coming soon. That was posted 2-1/2 years ago.
I did several key word searches but cannot find it. Please direct me.
@gsax Do you have a link, I have no idea what this is about.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
Thanks for the follow-up.
part 1 - https://dronebotworkshop.com/i2c-arduino-arduino/
part 2 - https://dronebotworkshop.com/i2c-part-2-build-i2c-sensor/
part 3 - https://dronebotworkshop.com/i2c-arduino-raspberry-pi/
Discussion on more videos, an implied part 4, starts around 27:58 of part 3.
I searched unsuccessfully on both the dronebotworkshop site and the YouTube site. Maybe it is there but the title does not register with me.
@gsax Here is the 4th
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
That's it.
Thanks.
@gsax 👍
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting