leka / moti Goto Github PK

Currently we are using Serial.print() for debugging.

We need a debug system that can be turned off when not in used to save space.

isShaken() and _isShaken are available but the detection is not yet implemented.

https://github.com/WeAreLeka/moti/blob/dev/lib/Moti/Moti.cpp#L56

We need to write tests for every lib/module, just the bare minimum, to keep track of API changes and to make sure stuff compiles.

drone.io is working but should try travis-ci to compare

Right now, depending on the module, the naming conventions differs.

We should have:

• Module::init() - to initialise the thread
• Module::start() - to start what the thread must do
• Module::stop() - to stop what the thread must do

When trying to fade(Blue, Black, 1000) from blue to black, it doesn't work.

By just calling the following over and over:

Light::fade(HEART, Color::Black, Color::BluePure, 500);
Light::fade(HEART, Color::Black, Color::Orange, 500);
waitMs(1000);

eventually the program crashes... Might have to do with the Queue thing.

Same as #47 but with angle for `spin()``

It would be great to do:

robot.spin(RIGHT, 180, 540); // the robot does a spin a 540° (1,5 rotation)

due to recent changes in the API, it doesn't work.

need to cleanup and make it work.

trying to integrate the 2 sensors threads 908b289 and the heart thread e811dcc

there may be some delay() issues due to the use of delayMicroseconds() and not chThdSleepMicroseconds().

add example module one can copy to start building his own.

It seems like Light::fade() doesn't do great when asked to go backward and forward.

I'll try to reimplement the last version to make some tests.

for testing we used Arduino delay() function which is not compatible with chibiOS

need to use the chibiOS chThdSleep() function.

for some strange reason, the gyroscope values are not as expected.

must investigate

if the the last fade is 2 second we need a waitMs(2000) to give it time to complete.

That should not happen. We need to fix this.

Same as the module example in #78, will be easier to get started

As the libs and API are currently changing a lot, compiling every behaviors/app is cumbersome and time consuming.

Using CI save us time and help us focus on what's not working.

Please note that compilation doesn't mean that it will work on the robot...

some irregularities
must investigate

heart should be beating like a real one

both should be working great with a led for each one

trying to make Moti snore while sleeping

must investigate.

maybe it would be better to create one ore two separates methods to accelerate or decelerate.

We are currently using wood, which is not ideal :)

GanttStart: 2020-01-02
GanttDue: 2020-03-03

For now, DriveSystem methods only set the direction and speed of the robot, but no duration.

I think it would be great to be able to do:

robot.go(FORTH, 180, 2000); // the robot goes forth for 2 seconds.

it seems to be working

Using the sensors class in a thread doesn't give any results, no output are serial printed.

the strange thing is that everything works fine with the motors.

must investigate

est-ce qu'on peut la supprimer ? :)

the types used need more consistency and casting.

we need to make sure the values are coherent.

this will also confirme #43

implement the sensor analyser to find pattern in the sensors' data