SoftwareSerial guidance

First of all, please don't scream at me for using SoftwareSerial instead of the real thing. I did it because it has better documentation.

Here's what I need help with:

  1. Noise | Does the connection get noisy or bad with long wires?
  2. 32U4 > 328P | I'm communicating between a Micro and a Classic Nano and I'm wondering if one will kill the other or something because of differing processors. They shouldn't, right?
  3. Communication | Is this two way? I need to send data from a couple of I2C sensors but also need to receive inputs to activate some IR LEDs and stuff.
  1. yes
  2. right
  3. serial coms can be 2 way.

All I needed. Thanks.

what's wrong with Serial documentation ?

Google "arduino serial communication" and you'll see what I'm talking about.

I don't know if I want to spend hours reading moderately hard-to-understand documentation when I can use something much easier and not terribly worse.

ah, it's not the documentation then, you are just lazy :innocent:


but if you want to keep the Serial ports for uploading code and debug, sure Software Serial (with all its quirks and limitations) can do the job (but the API is very similar although won't be as robust)

1 Like

Software serial is often reliable. However there are circumstances whereby incoming characters are dropped, whic can be a problem reading a GPS for instance.

NeoSWSerial does not suffer from the same problem.

Read about it here;

It looks difficult to use but may be worth trying. I'll see if I can get it working between a pair of UNOs over Autumn Break.

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.