• 0 Votes
    3 Posts
    2k Views
    T
    @martin_triska Thanks a lot! I had to do some debugging due to incompatible base source deviceTree (which was ultimately resolved by patching the compatible directives and a bit of merging together), but your response helped a ton! It works like a charm, so again, thanks! We plan to open source parts of the project in the future as well (along with a stable release) ... so hopefully it will help someone else too :)
  • S103 rs485 modbus sensor

    Official API - Evok neuron evok modbus
    1
    0 Votes
    1 Posts
    1k Views
    No one has replied
  • Input State remains the same

    Official API - Evok neuron pi l203 evok api input
    2
    0 Votes
    2 Posts
    2k Views
    T
    @HarishKumar The evok itself is not designed to handle the logic of your application. That's why we call it API. It is using Tornado which means the server itself runs in one loop so you need to have all the program behavior ready before it is called mainLoop.start(). So if you run an infinite loop anywhere in evok, you stop everything else (reading, setting, all APIs, ...). So I suggest using that APIs, it is much more easier to implement and you have the same functionality. But if you would REALLY want to do it in evok, you would have to prepare your program in a function, all tasks that would take more time would have to be decorated as coroutines and the call has to be yielded in order not to stop the main loop. The logic behind this is a little bit complicated to describe in one post :)
  • 0 Votes
    2 Posts
    2k Views
    T
    @HarishKumar It's ok. That's why the forum is here. If you visit the web interface of evok, you will see the numbers of IO of the Neuron you are using. In general it is numbered as X_Y where X is the number of group (1-3 depending on S/M/L model) and Y is the number of the Di/Ro/... So for example you would address DI1.4 as a string 1_4 with device type di.