Documentaion for .... WIP_BOPT_DEBUG_PKT and

[awneil]

@Moderator

it was decided that the appropriate place to add the option would be WIP AT Command Guide.

I think that’s a very bad idea!

Surely, it’s the WIP library that is the basis of this, so the WIP Library Documentation should be the “root”

Also, would you expect someone just using AT commands to be looking at Traces

Again, what we need is a proper, complete API - not to have to keep messing about with AT commands!

New Features - Complete API

Worse than that, WIP has deprecated the wip_netInitOpts API and now recommends that we use AT+WIPS instead Come on, Sierra Wireless - what are you thinking??!

Anyhow, the documentation provided in the WIP AT Command Guide is next to useless:

@WIP AT Command Guide v5.42

WIP_BOPT_DEBUG_PKT - Enable the debug traces of NET level 10

That’s it! No description at all of what the debug traces mean!

Similarly,

@WIP AT Command Guide v5.42

WIP_NET_OPT_DEBUG_PORT
This option is used to specify the port on which the debug traces are to be sent.
range: 0-3 (default value: 0)

There is no descriptionof what the values 0-3 mean.

And what about the other stuff: Undocumented: WIP_NET_OPT_DEBUG_PORT - #4 by awneil