Skip to content

Latest commit

 

History

History
42 lines (32 loc) · 1.84 KB

README.md

File metadata and controls

42 lines (32 loc) · 1.84 KB
Raw

pico-w-neopixel-server

Simple webserver aiming to be a thin remote controller for neopixel strips.

Developed to work with https://github.com/mrozycki/rustmas project.

If your host is capable of using mDNS, then you should be able to connect to the pico board using following hostname:

pico-w-neopixel-server.local

WARNING: There is no implemented conflict resolution - if you plan to use more than one neopixel server, consider changing the hostnames to different values for each server.

Dependencies:

  • CMake 3.19+
  • ARM GNU toolchain

If you don't have them set up, you can use these instructions

Usage

Just send a POST request to the /pixels endpoint with 3 bytes of data per each pixel!

To generate example data you can use:

NUM_PIXELS=500
temp=0; while [ $temp -lt $NUM_PIXELS ]; do byte=$(expr $temp % 100); printf "\x$byte\x$byte\x$byte" >> tmp.txt; temp=$(expr $temp + 1); done;

Then to send it to the device:

curl --data-binary @tmp.txt pico-w-neopixel-server.local/pixels

FS data

The my_fsdata.c file containing the response res.json file needs to be generated using makefsdata executable compiled for the host machine.
Create a folder named fs and a res.json file with the content of {} in it, and run makefsdata -11 -nossi in the directory that contains the fs directory.

There are issues in the template repository for automating this using Perl/Python scripts, however those lack some functionality that the C program has, and we need, like the keep-alive header.

Generated using https://github.com/krzmaz/pico-w-webserver-example