CLI debug

[spacehuhntech]

CLI debug

[Bommlon]

Maybe you are missing a linebreak after "hello world"?
The write command doesn't add an appending linebreak by itself.

[spacehuhn]

I just tested it myself and

create test
write -f test -c "STRING something"
write -f test -c "STRING else"
cat test

prints
STRING somethingSTRING else

That means write is not appending linebreaks by it's own.
What you can do is either to include a linebreak yourself or use the stream <file>, close and read commands.
With those you can open a file stream and everything you send over serial will be added as is to the file, until you send the close command.

[ruspea]

Thanks for getting back to me. I did wish to try this but I had a problem closing the stream, sending the word close was also written to the scream from serial however I can use the close command in the web cli. Is there a way round this. Thanks

…

On 15 Jun 2020, at 1:33 pm, Stefan Kremser ***@***.***> wrote:  I just tested it myself and create test write -f test -c "STRING something" write -f test -c "STRING else" cat test prints STRING somethingSTRING else That means write is not appending linebreaks by it's own. What you can do is either to include a linebreak yourself or use the stream <file>, close and read commands. With those you can open a file stream and everything you send over serial will be added as is to the file, until you send the close command. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[spacehuhn]

Probably the same issue, you need to send close with and after a linebreak like:

stream somefile
.....your text.......
close

but if you send it without linebreaks, the device sees it as this:

stream somefile.....your text.......close

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.