The NCD5500 allows you to easily change from a simple TCP socket or UDP datagram communication architecture over to a web interface based control and monitoring system. This interface is usable out of the box or completely customizable using HTML, CSS, and JS.
Currently the Web Interface configuration of the NCD5500 Ethernet module is only compatible with ProXR Lite.
Follow these steps to set up the software. The diagram below the steps will correspond to a step number.
The NCD5500 module does not have on-board storage for variables so you must alter the HTML files saved into the module. First you will need to have the .HTML file for your board which can be obtained from: https://github.com/ncd-io/ncd_Ethernet.
The NCD5500 module does not have on-board storage for variables so you must alter the HTML files saved into the module. First you will need to have the .HTML file for your board which can be obtained from: https://github.com/ncd-io/ncd_Ethernet.
You can alter and customize the code of the web page itself if you want to. NCD has limited support for doing so and a working knowledge of HTML5 is recommended.
Many functions in the base code expect an argument called kwargs. This is short for keyword arguments and allows you to pass context and variables through our functions and access them through your own callbacks later on down the communications flow. You can find an example of doing this in our standard relay control code which passes the kwargs of ‘callbacks’ (array of function to pass GET request responses to) and ‘bank’ (specifies the target bank for UI updates after getting current relay status’). This argument is not required and will default itself to being empty if no kwargs are passed. We recommend if you design your own code for the NCD5500 web interface to implement this practice as well.
The list of callable commands is in development. Contact us for questions or peruse the code. All of the pertinent functions will be listed after the NCD_AJAX function.