Creative Commons images are CC BY-NC-SA 3.0


added to your
shopping cart

In stock 271 in stock
11.95 1+ units
10.76 10+ units
9.56 100+ units

Description: As you know,  the Arduino micro controller only has a USB port and a TTL UART interface, so if you need an RS232 port directly connected to your Arduino, look no further than the RS232 Shield. 

The RS232 serial port used to be the standard connection for most peripheral ports on PCs, but now the port is primarily used on industrial equipment and automation prototyping, with the RS232 Shield and its DB9 connector, you can now easily access those elements straight from your Arduino.


Comments 11 comments

  • Will this board work with the Due?

  • Does this work with the Leonardo? If so, how does it interact with the virtual usb port?

    • It should work with Leonardo. Leonardo still has the TTL serial feature (and on the same pins, digital 0 and 1) - but unlike Uno the feature is separate from the USB communication with the PC. The sketch code would have to be written with this in mind (basically, use the “Serial1” class instead of the “Serial” class) - the upshot is that, on Leonardo, you’d be able to use this shield and the USB connection at the same time without conflict.

  • is there the Eagle files as usual? I’m confused with some boards having those files and some without? why’s that?

    • If it’s a board that we make in-house, we will post the Eagle files. For boards we source externally, the manufacturers do not always provide the full Eagle files, such as this.

  • I’m confuse about the schematic. They are using a P-Mosfet between the (resistor + Led) and Ground. With this configuration it seems to me the Mosfet will go to an undefined state:

    Gate=5V Source=5 V => Mosfet OFF Gate=0V Source=5V => Mosfet ON. But at this same moment the current will start flowing and so S->0V (The same as Drain) Gate=0V Source=0V => Mosfet OFF But if there is no current flowing, S->5V and so the Mosfet will switch to On again. While Gate=0V, the Mosfet will be switching between On and Off…

    Does somebody know what am I missing?

    From what I know of P and N channel Mosfets, this is a configuration for an N Channel Mosfet, not P (P-Mosfets Souce should be tight to VCC and Drain to the LED)

  • With the simple shields like this, I for one would prefer there to be a small section of protoboard available, possible tying to the other pins. That way, this would have a justified use rather than just making the arduino one shield taller.

  • I don’t see what there is to complain about with this shield. Engineering tells us to keep bypass caps close but real life tells me a MAX232 circuit works just fine built deadbug style with jumpers running all over. It’s just a simple level shifter and the way everything is laid out leads me to believe that the tracks and pin markings are done the way they are to help those just getting started to see how the circuit is built.

    • That’s what schematics are for. If they wanted beginners to see how the circuit was built just by looking at the board, they shouldn’t have silkscreened the entire thing. To me, it looks like they spaced everything out simply to justify needing an entire shield for something that can fit inside a DB-9 connector.

  • I don’t understand why the PCB layout is spaced out so wide. Basic EE literacy will tell you that a bypass capacitor should be as close to the IC’s power pin as is possible (and it wouldn’t hurt to put the MAX232’s charge pump capacitors closer either) but this is obviously not the case here. There seems to be a lot of unnecessary copper track length.

  • The amount of silkscreen on this board is to damn high!

Related Products