Skip to content
  • MySensors
  • OpenHardware.io
  • Categories
  • Recent
  • Tags
  • Popular
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
  1. Home
  2. Troubleshooting
  3. Controller to Sensor communication problem

Controller to Sensor communication problem

Scheduled Pinned Locked Moved Troubleshooting
serial protocolcontroller
3 Posts 2 Posters 1.8k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ? Offline
    ? Offline
    A Former User
    wrote on last edited by
    #1

    Hi,
    my setup has two Arduino UNO R3: one is connected with USB to my laptop running SerialGateway.ino, and the other is running ServoActuator.ino.

    I am about to write my own controller in Java by using the serial gateway looking at the code from https://github.com/mysensors/Vera/blob/master/L_Arduino.lua.

    My problem is that in ServoActuator.ino the callback void incomingMessage(const MyMessage &message) {...} is never called.

    For example the setup() of ServoActuator.ino sends a 0;10;2;0;3;1.4.1 message to the controller. My controller replies with 0;10;1;0;3;0 but that message does not reach the sensor.

    I did also the message exchange manually (with a terminal, no controller at all) but nothing works.

    By going looking at the MySensors code the call to boolean MySensor::sendRoute(MyMessage &message) just return false whatever I do. I think I miss something so that getChildRoute(dest) returns the correct routing to the sensor.

    Please let me know what I do wrong.

    Thanks,
    George G.

    1 Reply Last reply
    0
    • ? Offline
      ? Offline
      A Former User
      wrote on last edited by
      #2

      Hi,

      the problem is solved by sending 1 instead of 0 to the sensor during: 255;255;3;0;3; request. So, now I replay with 255:255:3;0;4;1 instead of 255;255;3;0;4;0 and when I get the request 1;10;2;0;3;1.4.1 I reply with 1;10;1;0;3;0 which goes back to the sensor.

      Kind Regards,
      George.

      1 Reply Last reply
      0
      • daulagariD Offline
        daulagariD Offline
        daulagari
        Hero Member
        wrote on last edited by
        #3

        So, now I replay with 255:255:3;0;4;1 instead of 255;255;3;0;4;0 and when I get the request 1;10;2;0;3;1.4.1

        Yes I think node-id 0 should not be used.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        28

        Online

        11.7k

        Users

        11.2k

        Topics

        113.1k

        Posts


        Copyright 2025 TBD   |   Forum Guidelines   |   Privacy Policy   |   Terms of Service
        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • MySensors
        • OpenHardware.io
        • Categories
        • Recent
        • Tags
        • Popular