Systems of this type (4-wire, half-duplex) are often constructed to avoid "data collision" (bus contention) problems on a multi-drop network (more about solving this problem on a two-wire network in a moment). To solve the "data collision" problem often present in multi-drop networks hardware units (converters, repeaters, micro-processor controls) can be constructed to remain in a receive mode until they are ready to transmit data. While the standards bring uniformity to data communications, many areas are not specifically covered and remain as "gray areas" for the user to discover (usually during installation) on his own. In this project, we have only used a baud rate of 9600 which is well under the maximum transfer speed we can achieve with the MAX-485 Module but this speed is suitable for most of the sensor modules out there and we don’t really need all the maximum speeds while working with Arduino and other development boards unless you are using the cable as an ethernet connection and require all the bandwidth and transfer speed you can get. While a multi-drop "type" application has many desirable advantages, RS422 devices cannot be used to construct a truly multi-point network.

A true multi-point network consists of multiple drivers and receivers connected on a single bus, where any node can transmit or receive data. RS485 meets the requirements for a truly multi-point communications network, and the standard specifies up to 32 drivers and 32 receivers on a single (2-wire) bus. EIA-485 only specifies electrical characteristics of the driver and the receiver. The RS422 driver and receiver use separate differential conductor pairs on the serial cables, enabling full duplex communications. The value of each termination resistor should be equal to the cable impedance (typically, 120 ohms for twisted pairs). Ideally, the two ends of the cable will have a termination resistor connected across the two wires and two powered resistors to bias the lines apart when the lines are not being driven. If two bits are received incorrectly, the error will go unnoticed by parity checking. This allows for basic error detection, in that if noise on the transmission line causes one bit to be received incorrectly, either received as a '0' when transmitted as a '1' or vice-versa, the error would be detected due to the count of '1' bits in the byte being odd when it is expected to be even, or vice-versa depending on the parity checking settings.

So, for eight data bits with a parity bit, M would be set (equal to one) in order to add an extra bit to each byte transmitted, and PE would be set in order to make that extra bit be used as a parity bit. The QScreen Controller controls the RS485 transceiver with bit 5 of Port D of the processor. The Serial 1 port can be configured for either RS232 or RS485 communications at up to 19200 baud. The Serial2 channel is always configured for RS232 communications, and can sustain baud rates up to 4800 baud. In its simplest form, a pair of converters from RS232 to RS422 (and back again) can be used to form an "RS232 extension cord." Data rates of up to 100K bits / second and distances up to 4000 Ft. Once a character is sent the hardware reverts back into a receive mode in about 1-2 microseconds (at least with R.E. Any number of characters can be sent, and the transmitter will automatically re-trigger with each new character (or in many cases a "bit-oriented" timing scheme is used in conjunction with network biasing for fully automatic operation, including any Baud rate and/or any communications specification, eg.

Each UART (sometimes referred to as a "USART") controls the serial-to-parallel and parallel-to-serial conversion and performs all of the timing functions necessary for one asynchronous serial communications link. It is NOT necessary to introduce long delays in a network to avoid "data collisions." Because delays are NOT required, networks can be constructed, that will utilize the data communications bandwidth with up to 100% through put. We will pull the enable pin high to put the MAX485 module in transmitter mode. We will pull the enable pin high to put the MAX485 module in receiver mode. Pin 3 of PortA is the Serial2 input, and pin 4 of PortA is the Serial2 output. We start with including the standard library for driving the LCD and declare the D8 pin of the Arduino Nano as an output pin which we will later use to declare the MAX485 Module as a transmitter or Receiver. Here again, we start with including the standard library for driving the LCD and declare the D8 pin of the Arduino Nano as an output pin which we will later use to declare the MAX485 Module as a transmitter or Receiver. The connection between two or more elements (drivers and receivers) should be considered a transmission line if the rise and/or fall time is less than half the time for the signal to travel from the transmitter to the receiver.

Here is more info regarding rs485 cable check out the site.