I've not had an issue with performance of the I/O but here's a technique for squeezing a little more speed out of the ports without having significant code changes.
http://www.codeproject.com/Articles/732646/Fast-digital-I-O-for-Arduino
I've not had an issue with performance of the I/O but here's a technique for squeezing a little more speed out of the ports without having significant code changes.
http://www.codeproject.com/Articles/732646/Fast-digital-I-O-for-Arduino
This looks nice until you see things like recent changing from Raspberry Pi to a Pi 2 and the library breaks! Too many folks here would not know what to do, except for some of the hard core type. I have not checked, but would guess the Arduino has ports mapped differently depending on the chips also.
Pass,
Clem
I think I get what you mean. Being able to standardise code is important if you are working on lots of different platforms and changing "core" libraries does pass compatibility issues onto your responsibility. However there are already issues between the different Arduino versions and often the libraries you find for your project are very old so to get working on that platform you do need to be quite good at fixing those kind of things.
To be honest if you are needing to squeeze ms off digital I/O you must already be working at quite a low level and this provides an intermediate step before you get to raw AVR code.
I think I get what you mean. Being able to standardise code is important if you are working on lots of different platforms and changing "core" libraries does pass compatibility issues onto your responsibility. However there are already issues between the different Arduino versions and often the libraries you find for your project are very old so to get working on that platform you do need to be quite good at fixing those kind of things.
To be honest if you are needing to squeeze ms off digital I/O you must already be working at quite a low level and this provides an intermediate step before you get to raw AVR code.