Skip to main content
Andrei Chichak
Andrei Chichak
Lead
November 13, 2014
Question

SPWF01S cgi scripts

  • November 13, 2014
  • 2 replies
  • 453 views
Posted on November 13, 2014 at 21:46

Back in version 140128, the documentation for dynamic web pages for the output demo (sending messages to the micro over the serial port) used test.cgi to shoot values out the serial port.

Recently I updated to 140805 and test.cgi is gone, but output.cgi exists.

But when I use output.cgi in the way that test.cgi was used in the past, it paints a demo page that then has to be filled out (again) before the new submit button sends the data to the serial port.

So, what cgi scripts are under the hood and how do you use them?

thanks.
    This topic has been closed for replies.

    2 replies

    Andrei Chichak
    Andrei ChichakAuthor
    Lead
    November 13, 2014
    Posted on November 13, 2014 at 22:34

    Here is an example. This is a rework of the boiler version of the output demo page. It should submit the user's text to the serial port, instead it brings up output_demo.html.

    Andrei Chichak
    Andrei ChichakAuthor
    Lead
    November 14, 2014
    Posted on November 15, 2014 at 00:17

    Update: from a bunch of surgical testing, I figured out that only a widget with a name of ''text'' will have its value sent out of the serial port. All of the others are ignored by output.cgi.

    Is this true, or are there other widget names that trigger output.cgi to do something useful (what are the names and what do they do)?

    Also, after writing the text widget value to the serial port, output_demo.html is displayed instead of the page that was on the screen. Is there any way to override this behaviour so that I can go to the page of my choice rather than output_demo.html?
    Terms & ConditionsAccessibility statement