Sensors Only Version for NodeMCU #32
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Uses a WiFi connection only to talk to JMRI.
Also edited the description in contained within the DCCpp_NodeMCU.ino file.
Similar to the way it is implemented in DCC++32
GPIO pins can now be defined as outputs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Uses the WiFi connection only to talk to JMRI. The serial interface is only used for boot status and debugging.
Several files were deleted or renamed, so don't let the number of deletions scare you.
I eliminated everything but Sensor inputs. I might add the Outputs back in, if there is any interest. I am also considering the possibility of serving multiple clients (similar to the ESP32 version). Now only one client can be connected at a time.