Improved sensor usage

HomeForumsMonoBrick EV3 FirmwareImproved sensor usage

This topic contains 2 replies, has 2 voices, and was last updated by Author Image Lars Gardien 1 year, 2 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #5558
    Author Image
    Lars Gardien
    Participant

    Hi Anders,

    Last semester I had the assignment to participate in the First Lego League using your firmware. I noticed there was only little support for sensors. I’ve added the same polling features that were already present in the buttonevent classes to the sensor classes. I also added a possible implementation of these sensors to the vehicle class. A few more changes were made to the QueueThread to make it a little more thread-safe, i’m still not to sure though.

    These changes were only implemented for the EV3 sensors, because that’s all i had to use. The only thing currently not working is the EV3TouchSensor, because i had to cheapfix it, you’ll see…

    Just have a look if you’re interested, but don’t feel obligated.

    Thanks for your time,

    Lars Gardien

    Attachments:
    You must be logged in to view attached files.
    #5560
    Author Image
    Anders Søborg
    Key Master

    Hi Lars

    Sounds exciting – please use a pull request from Github. This makes it much easier… looking forward to ypur suggestions.

    /Anders

    #5565
    Author Image
    Lars Gardien
    Participant

    Hey Anders,

    I’d love to do a pull request, problem is I don’t think it’s ready for deployment. I can do a pull request for the improved QueueThread. But the sensorpolling and its propertyChanged events only work on all classes that derive from the UARTSensor Class, which isn’t exactly what I’d call proper.

    Furthermore, I haven’t got an EV3 at my disposal anymore, so I can’t test my code…

    Lars Gardien

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.

Posted in

Make a donation