You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 30, 2021. It is now read-only.
I am far from an expert on the matter but I found 2 versions of terminating A and B.
The sample hardware in the readme does as in the top diagram, pull B to VCC and A to GND and then in the sdm630 sample ino, the serial port is initialized with the invert parameter true.
All cheapish prefabricated ttl-rs485 converters I found use the bottom diagram with A pulled to VCC and B to GND, with an 120ohm resistor between A and B, but then the invert parameter must be set to false.
I think it would be good if you spend a few words on the invert parameter in readme.MD to avoid confusion (and a failing setup) for new users.
nogmaals bedankt.
The text was updated successfully, but these errors were encountered:
You're right. I forgot about this after testing my initial setup (which didn't work because of counterfeit max3485 chips that couldn't handle the 3V3). It's mixed up right now. thanks for the pointer.
Offcourse, confusion comes from the rs485 standard itself where -as I understand- A should be negative to B whereas the real world implements the opposite.
Hi,
I am far from an expert on the matter but I found 2 versions of terminating A and B.

The sample hardware in the readme does as in the top diagram, pull B to VCC and A to GND and then in the sdm630 sample ino, the serial port is initialized with the invert parameter true.
All cheapish prefabricated ttl-rs485 converters I found use the bottom diagram with A pulled to VCC and B to GND, with an 120ohm resistor between A and B, but then the invert parameter must be set to false.
I think it would be good if you spend a few words on the invert parameter in readme.MD to avoid confusion (and a failing setup) for new users.
nogmaals bedankt.
The text was updated successfully, but these errors were encountered: