hi
i am using the SN65HVD35 for RS422/RS485 interface.
is there any reference design i can compare to?
do i need to use a TVS at the output?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
hi
i am using the SN65HVD35 for RS422/RS485 interface.
is there any reference design i can compare to?
do i need to use a TVS at the output?
Hi Golan,
RS-485 applications can vary widely in their environment and implementation. If you can describe your application and its requirements (number of nodes, distances, data rates, cable, etc.) in more detail, it will be possible to provide more accurate and useful resources and feedback.
To get started, there are several resources you might find useful:
hi
i used the SN65HVD35 for both RS485 and RS422 connection, we intend to use usually the RS485 option.
distance - up to 25-30m
data rate can be of up to 57600
Golan,
30 meters and 57kbps are well within the capability of the SN65HVD35 (and, more generally, any other RS-485 compliant transceiver). By adhering to the guidelines laid out in the RS-485 Design Guide to which I linked previously for considerations such as cable characteristics, bus termination, etc., you can certainly meet these requirements.
hi
as i understand this component can support both RS485 and RS422.
what should be the pin output configuration schematics (using jumpers) that will support both options for this component?
Golan,
The RS-485 and RS-422 standards refer only to the electrical characteristics of the driver and receiver, of which the SN65HVD35 is compatible with both. There is no concept of switching between the two. Rather, RS-485 is a stronger standard than RS-422, so any RS-485 compliant transceiver is simultaneously compatible with the RS-422 electrical standard. As such, I recommend using a standard RS-485 full-duplex bus configuration.