Thanks for the warning. I'll stick some resistors in line with Tx and Rx lines.The IO on the 3.3V promini is NOT 5V tolerant.
I was pleasantly surprised to find a semi-local supplier of Arduino & Arduino clone hardware with cheap shipping. I ordered 5 mini pro's which arrived last night.
The supplier sells both 3.3V and 5V versions. I ordered the 3.3V ones, and then afterwards got wondering if there would be any compatibility problems using the FTDI USB/serial adapter to program it. The FTDI adapter supplies 3.3V to the controller, but I assume the serial signal logic levels are still 5V. I guess I can put some small value resistors between the adapter and the microcontroller just to be safe, but I was wondering if anyone has had any problems with voltage level differences in this situation.
No there's no problems at all with the FTDI, as far as I'm aware it actually puts out 3.3V levels?, and is fully compatible with 5V as well.
Just checked one, as there was one connected just to my right, and a meter just to my left- 3.3V on the I/O.
But you didn't check every board in existence, did you?
The point I made in post #22 is simple and is correct. The ProMini 3.3V is not 5V tolerant. One needs to look at the voltages on all of the lines that will be connected to the ProMini to make certain that they are not 5V. Not all FTDI USB to Serial boards are always 3.3V signals. Not all boards called FTDI have legitimate FTDI chips.
Here is a legitimate FTDI USB/Serial interface board.
SparkFun FTDI Basic Breakout - 5V - DEV-09716 - SparkFun Electronics
This is a basic breakout board for the FTDI FT232RL USB to serial IC. The pinout of this board matches the FTDI cable to work with 5V Arduino boards.www.sparkfun.com
As you can read in the description:
One of the nice features of this board is a jumper on the back of the board that allows the board to be configured to either 3.3V or 5V (both power output and IO level). This board ship default to 5V, but you can cut the default trace and add a solder jumper if you need to switch to 3.3V.
If you buy this board, don't cut the jumper, and use it with a 3.3V ProMini, you will likely damage the ProMini.
The 3.3V ProMini is not 5V tolerant. Check the voltage on whatever USB?Serial adapter that you use. <---period
Most FTDI boards are adjustable to either - usually by a moveable jumper. If you're going to assume every poster is too thick to read instructions, or labels on the prducts, perhaps you ought to warn them against connecting mains directly to the Arduino?.
The poster that asked about it clearly said "I ordered the 3.3V ones" in post #20, and was wondering if the 3.3V ones actually used 5V logic levels, and just altered the power out - which they don't. Perhaps you should try reading the posts you reply to?.
I have several 3.3v prominis, including the real one from sparkfun and a couple of different clones. They all work quite well, but they are slow (8MHz).
The IO on the 3.3V promini is NOT 5V tolerant. Vcc for the ATMega on the board is 3.3V and Vcc +.5 is the maximum input voltage level, if I recall the data sheet correctly.
I have settled on this serial-USB board https://www.microcenter.com/product/486570/FTDI_Adapter_USB_Controller and have several and they have never let me down. They are 3V-5V switch selectable and all the relevant signals get switched.
Every Arduino (and clones) board I've bought has had the USB part built in. Surely it's cheaper (and easier/safer) to just buy complete boards. Not a criticism, just an observation.
Mike.
Since I've already got the USB/serial adapter, it's not a big deal, and the Mini-pro appears to be cheaper than anything else I've been able to find.
Thanks for the warning. I'll stick some resistors in line with Tx and Rx lines.
I'm going to try the LED Blink demo tonight. I'll report back later.
On the first board that arduino developed that used an auto-reset feature the IDE used the RTS control signal to trigger the reset to the board. On later boards they changed to using the DTR signal to use that (I recall no reason given for the change) for the trigger signal. So to keep compatibility they had to issue both RTS and DTR pulses
Last night I did some programming. I'm a bit rusty, programming in C, and got tripped up with function calls that have no parameters. I was unaware or had forgotten that, unlike some other languages, even if your function call has no parameters, you still have to include an empty pair of parentheses. I'd left them out, and the compiler didn't flag it as an error. So, it took a while to track down.
The one that still occasionally gets me is if(var=3) instead of if(var==3). I've tried using if(3==var) so it throws an error at compile time but for some reason my fingers always type it the other way around.I'm a bit rusty, programming in C, and got tripped up with function calls that have no parameters.
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?