issues with escape_seq

[infor]

Posted on January 06, 2017 at 12:37

Hello ST,

it seems that the escape_seq parameter does not work as expected in the IDW01M1.

There are some discrepancies between the user manual and the obtained results. Please have a look at my transcript:

12:16:15.761 [TX] - at+s.scfg=escape_seq,at+miao<CR>

12:16:26.101 [RX] - OK

+WIND:61:Incoming Socket Client:192.168.0.218

+WIND:60:Now in Data Mode

12:25:49.307 [TX] - at+miao

12:25:49.807 [RX] - +WIND:59:Back to Command Mode

12:26:05.899 [TX] - at+miao

12:26:10.363 [TX] - at+miao<CR>

12:26:10.595 [RX] - ERROR: Command not found

12:26:13.700 [TX] - AT+S.<CR>

12:26:13.703 [RX] - +WIND:60:Now in Data Mode

So, it seems that:

1) escape_seq only changes the data->command sequence, but not the command->data

2) when in command mode, you need to send a to activate the sequence, despite the fact that the manual states the opposite.

Some more information:

♯ nv_model = SPWF01SA1

♯ nv_serial = 3915D31697

♯ version = 160129-c5bf5ce-SPWF01S

Giuseppe

#x-nucleo-idw01m1 #spwf01sa1 #escape-sequence

[Gerardo GALLUCCI]

Posted on January 08, 2017 at 04:19

Ciao Giuseppe,

escape sequence is used to exit data mode. Once in command mode, you need to run 'at+s.' command to come back into data mode again. It's a command, not An escape.

j

[infor]

Posted on January 12, 2017 at 21:50

Ciao Gerardo,

after reading your comment, I checked carefully the manual. In facts it confirms what you say.

Perhaps I can suggest to give some more emphasis to the 'note' that describes escape sequence. Anyway, the description is correct.

Thanks

G.

[Gerardo GALLUCCI]

Posted on January 13, 2017 at 11:19

Please use 'Mark Correct' button to close the issue