ok.
Let me see if I understand you guys...
- If the specs says 5v, then it's pins may trigger HIGH if they receive both 3.3v or 5v.
If the specs of a device say 3.3v, then be careful how much tension you apply to the pin. here in the case of the Lidar it says max 3.5v (*)
On arduino at least, tt is not possible to change this 3.3v <-> 5v pin settting from software.
- now let's see each of those 3 arduino models one by one
Microcontroller ATmega32U4
Operating Voltage 5V
Microcontroller ATmega328P
Operating Voltage 5V
Microcontroller ATmega2560
Operating Voltage 5V
All 3 boards are 5v. None of them are 3.3v
- if the devices I want to communicate with are 3.3v (the example of rplidar), then if I just receive data it should be fine with all those 3 arduinos (uno/micro/mega). However, if I need to send them something, then i need voltage conversion (with a level shifter on high baudrates).
In this case, indeed i must first issue a startscan command so that the rplidar sends me data.
==> So far so good?
Assuming yes.. then what can possibly explain that everything worked out-of-the box with uno and mega BUT required a 5v <-> 3.3v conversion on micro ???
and for the (*) above ==> the rplidar specs says it's max 3.5v on its RX/TX pins.... does that mean that even if it seems to work now with my 5v pins from uno/mega => my rpildar could fry any second ?
I am so confused 