Navigation

    • Register
    • Login
    • OpenHardware.io
    • Categories
    • Recent
    • Tags
    • Popular
    1. Home
    2. DirkB19
    3. Topics
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by DirkB19

    • DirkB19

      How to program Itead Rboard ? ISP ? FOCA ?
      Troubleshooting • avrisp mkii rboard itead progr • • DirkB19  

      2
      0
      Votes
      2
      Posts
      1022
      Views

      JCLB

      @dirkb19 Use Arduino 1.6.13 and not 1.8, it's a problem related to fuses with clones... You need to program with another arduino nano (or other) as ISP Then use the following: Duemilanove > 328P arduino as ISP plug the 7-19v Vin on the rboard You may also have to burn the bootloader And maybe need to press manually reset button on rboard, personally i don't need to. I've been struggling for a while with this board.
    • DirkB19

      Exit status 1 Error compiling for board Arduino Nano ?????
      Troubleshooting • • DirkB19  

      2
      0
      Votes
      2
      Posts
      5539
      Views

      pansen

      The problem is avr-g++: error: CreateProcess: No such file or directory Without any code we won't be able to help. It looks like a header is missing.
    • DirkB19

      Nano doesn't want to sleep ?
      Troubleshooting • • DirkB19  

      3
      0
      Votes
      3
      Posts
      926
      Views

      DirkB19

      Hi and thanks for the tips. I didnt think of the PIR indeed. But anyways, the nano isn't sleeping because I get serial debug back from it after the sleep command.
    • DirkB19

      RelayWithButtonActuator problem after toggling with pushbutton
      Troubleshooting • • DirkB19  

      8
      0
      Votes
      8
      Posts
      2264
      Views

      DirkB19

      Hi, I still haven't found the cause of the problem. But I have found a workaround The problem is captured in the serial output of my previous post. As you can see the payload ? of the incomming message is for some reason messed up. I still suspect the mqtt-cllient-gateway to be responsible for this, but i can not prove this. So the workaround is to filter out only the good info from the messedup payload. The good info seems to be found in the first bytes of the payload, while the last part acts up randomly. I filtered using substring as follows String hexstring = message.getString(); String String3 = hexstring.substring(0,1); // Filter out unwanted additional characters = workaround bug