Web page interface software

Hello
I’m looking for ideas and direction for available software.
I want a web page front end to control remote hardware.
I have no idea on what software or technology is available or where to start reading.
Anyone setup anyything similar?
All suggestions welcome.
Riscos based preferrably unless there is hmi/scada that could be ported from gcc.

Thanks
Ron

My central heating controller is on a Raspberry Pi, and has one main app, with two other apps that control the hardware (one does relays and a thermostat via GPIO, the other a communicates with a radio interface via Ethernet). I also run WebJames, which has several dynamic HTML pages, generated in BASIC in WebJames’s cgi-bin folder. When a web page needs to get any information or change any setting in the heating controller, the BASIC communicates wuth the controller’s main app via Wimp messages.

Does that sound like an appropriate architecture for what you want to do?

Hi Dave, yes, very much so.
It’s the web page passing info back to the controller that I’m unfamiliar and interested in.

Can you give me a basic crash course on the html and cgi operation?

Cheers
Ron

HTML is a big topic. My best suggestion is to take an existing text-only web site (mine at http://davehigton.me.uk is text-only), choose an HTML tutorial website, and edit your copy of the HTML in accordance with what you learn and what features you want. Keep using an HTML validator to check that the HTML you have written is correct.

CGI is really about generating HTML from BASIC. My best suggestion is to install WebJames on your computer and follow the tutorials that come with it.

At this early stage in your learning, trial and error is important. You will likely write wrong stuff far more often than right, but that’s just the nature of the beast, so don’t be disheartened, don’t give up, just keep learning!

Thanks, will do.
I remember vaguely playing with cgi stuff 10 years ago after reading last night.
I’ll have a play and get back.

Cheers
Ron

It could be easier to write it as an API server, which can grow with your needs. All it listens to are simple GET and maybe POST requests, with text output that isn’t even HTML. All the fancy stuff can be elsewhere, and it’s easier to use it in different applications.

Typical GET request looks like:
http://madeupname.com/api?command=time;zone=gmt

Typical output looks like:
{"time": {
“hour”: “14”,
“minutes”: “33”,
“seconds”: “20”
}}

Or you could drop the complex JSON output, and just have:
time=14:33:20