poppy logs

To get logs of (real only) robot .i.e.:

curl -X POST -d "id=0" http://poppy.local/api/raw_logs

Provide a release that does not require node.js installed.

Once the robot is turned on, the first request to the http server always failed (see this thread).

As the config command is dedicated to "early" check the settings about connection, it could throw user off.

-S --Save flag does not work at all.

Use the 'poppy.local/reset' URL

Next to replace the use of json files with live discovering as default way to get robot structure, some features are not really usefull or must evolve:

• The json <-> live robot robot validation i.e. the 'v' flag
• -a option (could be performed with the query command),
• The discover flag...
• -M option should be dedicated to display and check connection to motors.
• -S will be kept for advanced use.

Append a new flag -d/--details in order to display detailed info about motors:

• Type,
• Id,
• Range for angle.

As example, typing:

poppy exec position 0 -w

does not wait the end of the movement as expected.

Mention these points in documentation:

• This module requires the v3.x.x release (aka it is based on pypot REST API v3.x.x),
• It has been only tested with dynamixel XL-320 (aka Ergo Jr).

aka poppy exec config -M without any user's settings for connection

aka integrate the v10 release of the module poppy robot core.

Various minor issues about the poppyrc file

• User's descriptor locator is never saved,
• Do not save empty settings (i.e use of default settings for both locator and connection),
• Do not save empty connection settings.

poppy-core: 9.0.0
yargs: v16

poppy shutdown

To turn the raspberry off.

Generic task for code improvement/ misc. update

By replacing the following command:

poppy exec compliant true|false ...

with

poppy exec compliant ...

and

poppy exec stiff ...

Use:

• Latest wix-msi release,
• Png icon instead of ico.

Apdat code to use the live discovering feature introduced in poppy-robot-core v4.0.0.

Use live discovering as default method instead of reading flat robot descriptor.

Using of Json descriptor will be still available but not anymore spotlighted i.e. reserved for advanced users.

The reboot command is querying the target robot to get its structure that is useless.

• Remove david badges (almost always down),
• Add lgtm/codeclimate badges.

poppy exec compliant // handly drivable
// will be same as
poppy exec compliant on

// instead of the inverse value as default:
poppy exec compliant off // i.e. programmatically drivable

That sounds more logical

Add this info in the config command dedicated to display "detailed" robot structure (aka with -M flag).

see #7: fixed with poppy v3.0.0

Fixing issue 6 of poppy-robot-core will almost solve it.

Excepted for the config command which use lower object (the PoppyRequestHandler) instead of the Poppy factory which is in charge to perform resolving of the .local addresses.

The notion of locator for file descriptor will not be anymore relevant with poppy robot core v9 and higher.

Next to poppy v3.0.0 change url from '/reset' to '/reboot'.

Update to clearer description => Reboot raspberry instead of robot

Add a new option in order to display the querying results in accordance with the robot structure aka group results per alias/motor.

=> Add a -t/--tree flag to the query command.

• Remove any references/configuration/use of the snap REST API
• Simplify CLI port settings: --http-port => --port

Do not 'pre'query robot when -h is used with cli entry point (aka typing poppy -h).

'pre'requirying is only needed to get robot configuration/the list of motors for sub commands in order to fill dynamic options values such as the list of motors.

Using --ip does not set the ip of target robot (but the flag -i works).
Idem with http and snap port aliases.

This property is not the robot descriptor but its locator.

poppy exec [compliant|speed|position|rotate|led] [value] ...

will be replaced by

poppy [compliant|speed|position|rotate|led] [value] ...

Use the "files" property in package.json on order to ensure to not pack unwanted/extra files.

The dependency to wix-msi introduced with release 7.1.0 is blocking installation under other os than windows.

In some particular cases, (commands using a positional argument abd the ip or port flags) the parsing of the arguments could return an invalid options message.

In the 'exec' command, replace the -v option with positional argument.

That will simplify the use of this command.

That will allow:

• Avoiding to overload poppy rest server with requests and then decrease failure on requesting robot,
• Better error management (failure are treated per request, not globally).