I think in summary of this, one action item I will go is specifying the wire to match the device rather than trying for a one size fits all. We have a standard, stick with the standard. Realistically, we have all low powered devices and the only device I see that doesn't meet our standard is a small controller that would result in a 4.58% VD if we used 20AWG. All other devices are fine. I could twist these together with 2 of the 20AWG conductors to make 17AWG, but, like you all said, just pick the right wire in the first place. If the scope of work is outlined initially, then construction shouldn't have an issue. Right now, it's looking like 3 different sets of wires tentatively. 1 for 485, 1 for controller, 1 for all other devices.
itsmoked mentioned the insulation thickness and I got some reading last night. From what I am interpreting, of all this, the capacitance of the wire experiences a charge that effect the voltage, similar to a basic RC circuit. The Voltage Source can goes HIGH/LOW when transmitting data, but the wire will experience a delay due to this capacitance charging effect. (IMG14) When I see this, I go back and say if we are experiencing issues on older installation, I could slow the data rate, which will allow for more time for the charging discharging of the wire so that receiver can detect the voltage levels. Is this a correct analogy?
Also, I never understood the drive voltage range on RS485. I don't see why the output high isn't always 12V but rather a 12V to -7V. What effects the drive output voltage and is there a constant current that it is sending?
Last, why is the max distance always 4000'? It seems that if you had a low impedance/capacitance wire and did a low data rate (if the above capacitance analogy is correct), you could go further. Is this just a recommended standards? Hence the RS of RS-485?