Skip to content
This repository has been archived by the owner on Feb 13, 2024. It is now read-only.

Implement S88/S88-n Sensor support #2

Closed
atanisoft opened this issue Dec 11, 2017 · 8 comments
Closed

Implement S88/S88-n Sensor support #2

atanisoft opened this issue Dec 11, 2017 · 8 comments
Labels
enhancement New feature or request

Comments

@atanisoft
Copy link
Owner

atanisoft commented Dec 11, 2017

This will provide up to 512 sensors with only a few GPIO pins required to read state of the inputs.

@atanisoft atanisoft added the enhancement New feature or request label Dec 11, 2017
@atanisoft atanisoft changed the title Implement S88 Sensor support Implement S88/S88-n Sensor support Dec 12, 2017
@atanisoft
Copy link
Owner Author

@atanisoft
Copy link
Owner Author

Implemented in v1.1.0

atanisoft added a commit that referenced this issue Jun 4, 2019
atanisoft added a commit that referenced this issue Jun 27, 2019
@zubozrout
Copy link

Hi,
sorry to ask under this issue, but I was trying to find out more about the wiring needed for that and haven't been able to find a single resource for that.

All I have found is this page:
https://atanisoft.github.io/ESP32CommandStation/config-s88.html
plus that I will most certainly need a RJ45 connector to easily connect all S88/S88-N sensors.

Unfortunately I haven't found a single wiring scheme. Could you please share more details on that, perhaps add it to the documentation page?

Info like: what components should one buy, where should it get connected to on the ESP32 board and maybe some simple scheme would help a lot.

Thank you very much.

@atanisoft
Copy link
Owner Author

@zubozrout I've been meaning to add more documentation all around on the site. I'll add some details on the wiring. For S88 you would likely be best with an RJ45 breakout board for the connections to the esp32. Three pins are common across all S88 buses with one additional pi per bus for data. I've got a reference page for the S88 pinout for RJ45 and the inline pin connector and will add both to the webpage today.

@atanisoft
Copy link
Owner Author

@zubozrout I've updated the page to now include more details. It may take a short bit for it to replicate to the webservers.

@zubozrout
Copy link

Thank you very much for all the info and the updated wiki, really appreciate it :).

@zubozrout
Copy link

Hello,
I finally got around to wiring everything up (properly). I hope I got everything right - in regards to the default configuration at least. I've also uncommented #include "Config_S88.h" in Config.h. But I am unsure about the following:

NOTE: The S88 Bus will require a data pin in addition to the pins that are common to all S88 Buses. which I am sure I haven't done.

It might be related to this <S88 ID DATAPIN COUNT> : Creates an S88 Sensor Bus with the specified ID, DATA PIN, SENSOR COUNT. but how should I trigger that S88 command (where)?

All I have available is the DCCppESP32 Web interface and JMRI. And then a occupancy detector connected to the S88N bus.

Also, once the data pin is configured, what should I see? Will there be a new item for S88 sensors in the Web UI and/or where to look for that in JRMI?

Thank you very much and sorry to be bothering you with these for sure trivial things to solve.

@atanisoft
Copy link
Owner Author

If you enable the S88 support in the code, recompile and flash it to the esp32 you should see a S88 section available on the configuration tab of the web interface.

From the web interface you should be able to create the S88 Bus with the data pin and how many S88 inputs are expected. Sending the S88 command as written above is not directly supported from JMRI.

Once the S88 Bus has been defined, the inputs will show up as regular sensors in JMRI with a base ID of 512 (default) and count upwards from there for each input. Secondary buses will do the same but will start with the first sensor id as a multiple of 512.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants