Skip to main content
tabekb
Associate III
May 11, 2017
Question

SPWF04S Server-side-includes

  • May 11, 2017
  • 2 replies
  • 966 views
Posted on May 11, 2017 at 15:04

Hi!

I am using the SPWF04SA module. I am trying to create dynamic pages. My webpage is done and it works. I'm having problems with updating the tokens buffer using the AT+S.INPUTSSI command as described in the AN4965 Application note and UM2114 User Manual.

The problem is, if I send more than 255 bytes with AT+S.INPUTSSI command, the module became unresponsive! No more AT commands are recognized, and after 20 seconds the Watchdog resets the module. I think this is a bug, and if the SSI tokens buffer is limited to 255 bytes, this should be mentioned in the manual and/or application note.

So, when I send this:

AT+S.INPUTSSI=256

|{1111;11/05/2017;16:00}|{1111;11/05/2017;16:00;0;1;11,00;116;0;0}|{1111;11/05/2017;16:00;116;0;0;0;6;0;0}|{1111;11/05/2017;16:00;7;1;0;2;1;0;12345;0.0.0.0;123456789012345;1234567890123456}|{1111;11/05/2017;16:00;22:32:43;33;3;8;19:42:43;32;2;65}|{012345}|

I get no answer from the module, and I have to wait 20 seconds for the watchdog to reset the module.

Instead if I send this:

AT+S.INPUTSSI=255

|{1111;11/05/2017;16:00}|{1111;11/05/2017;16:00;0;1;11,00;116;0;0}|{1111;11/05/2017;16:00;116;0;0;0;6;0;0}|{1111;11/05/2017;16:00;7;1;0;2;1;0;12345;0.0.0.0;123456789012345;1234567890123456}|{1111;11/05/2017;16:00;22:32:43;33;3;8;19:42:43;32;2;65}|{01234}|

I get answer and everything is ok.

So, the question: is this a bug, or the tokens buffer are limited to 255. Even if the tokens buffer are limited to 255, this is a bug, because the module is completely blocked until the watchdog reset...

I hope you have a solution for this, because we are migrating from SPWF01S to this new module, and I really need dynamic pages for more than 255 bytes.

Thank you

    This topic has been closed for replies.

    2 replies

    Gerardo GALLUCCI
    ST Employee
    May 12, 2017
    Posted on May 12, 2017 at 10:55

    Hi,

    thanks for feedback. There is a bug on tokenizer (mismatch on u8/u16 type) on FW1.0.0. Fixed, and available on near coming FW1.1.0 (a few weeks) currently under testing.

    No constraints about the number of tokens, or length.

    With fix:

    12-May-17 10:54:51 [TX] - AT+S.INPUTSSI=256<CR>

    |{1111;11/05/2017;16:00}|{1111;11/05/2017;16:00;0;1;11,00;116;0;0}|{1111;11/05/2017;16:00;116;0;0;0;6;0;0}|{1111;11/05/2017;16:00;7;1;0;2;1;0;12345;0.0.0.0;123456789012345;1234567890123456}|{1111;11/05/2017;16:00;22:32:43;33;3;8;19:42:43;32;2;65}|{012345}|

    12-May-17 10:54:51 [RX] - AT+S.INPUTSSI=256<CR><LF>

    AT-S.Managing Tokens:6<CR><LF>

    AT-S.OK<CR><LF>

    Thanks again

    Ciao

    jerry

    tabekb
    tabekbAuthor
    Associate III
    May 17, 2017
    Posted on May 17, 2017 at 10:56

    Thank you for the answer Gerardo. I would like to ask you if it is possible to give me FW with this bug fixed, so we can go on with our development.

    Anyway, I think I found another bug/limitation, now on the POST side...

    The POST request is limited to 64 bytes, so I cannot send more than 64 bytes with a POST...If I send 65 bytes, the last byte is truncated and only 64 bytes are delivered by the module. 64 bytes for a POST are not enough...

    I am looking forward for your answer.

    Thank you

    Gerardo GALLUCCI
    ST Employee
    May 17, 2017
    Posted on May 17, 2017 at 12:04

    Ciao Tibor,

    are you talking about the output demo (the 'opposite' of input SSI)?

    jerry