Other Parts Discussed in Thread: ISO3082
In an existing product the formerly used ISO3082 was replaced by the ISO 1500 as recommended.
The application and the used custom protocol uses the fact, that in case of two busmembers sending messages at the same time (collision is possible and allowed by the protocol) on the receiver-output (PIN R) the confused signal of the collision is visible for collision detection. It shows undefined messages due to undetermined voltage levels on the bus. The sended message is bitwise compared to the received one. when differences occur, a collision is presumed.
The ISO 1500 doesnt show this behavior. During transmission on the receiver output only the exact sended message can be seen unaffected of the collision going on on the bus. Not till transmitting stops an the rest of the colliding message may be received.
Looking at the datasheet i encountered differences in timing, voltage threshholds an driver-impedances. I assume, that due to the improved improved HW-drivers and high bus impedances due to quite long bus cabling the receiver doesn't see the foreign signal but only his own, when transmitting.
Looking at the standard there's no collision detection specified for the RS485 bus.
Looking at the datasheet a collision detection function is not mentioned in both transceiver-versions.
- Is the behavior of the ISO3082 an explicit function of the driver? (Or has it been used for detecting collisions although it's not intended for that explicidly?)
- Are there isolated RS485-transceivers with distinct collision detection (maybe actually with a distinct Pin) available? (If yes pls name them since i didn't find some)
- Is collision detection with the 485-bus usual in the applications, since it is not defined in the standard?