• sysfs interfacing

    6
    0 Votes
    6 Posts
    3k Views
    Martijn HemeryckM
    'nother update: giving it some thought, I quickly wanted to see if I could do the same stuff again in go, so here goes another POC: https://github.com/mhemeryck/unipitt/blob/37b9a07bc570301c2a11836526df1a2be8b21647/main.go (Don't mind the project name though, I've sort of ran out of original names, I guess) Anyways, performance seems much better in this case. I figure I'll put my efforts into polishing this project as it seems to be the simplest, fastest, most robust. I did notice however when toggling one of the DI's, that another DI also got toggled somehow, still need to investigate that further. Thanks for continuous feedback, this actually adds a lot to me for the overall unipi experience!
  • EVOK and PIGPIO

    6
    0 Votes
    6 Posts
    3k Views
    L
    @tomasknot The wiegand is 0-5 Vdc (it's not even 5 its 3.8Vdc) Wiegand data pulses are 50ys width and come at 1ms wiegand protocol (while Neuron DI locial 1 must be higher then 4.5Vdc and min puls with is 20ys) Is there any possibility to connect this to Neuron M103 Are there raw PI inputs available?
  • Working with EVOK API for the first time

    25
    0 Votes
    25 Posts
    15k Views
    T
    Alright, thanks! I'll try the package installation on Raspbian and report back if I have any issues.
  • No inputs or outputs accessible

    2
    2
    0 Votes
    2 Posts
    2k Views
    T
    Hi @dominikmlkvy, This looks like a hardware problem. Are there any visible signs of damage on the board, or perhaps an interrupted connection somewhere? It might help if you can provide photos of the device in it's current state with a sufficient resolution to examine the hardware. If you are positive that you have not used the device in a way that is outside the intended operating parameters you can send the device for a replacement, but you may be charged some or all of the cost if the fault is due to improper use. Please contact [email protected] for further help. We keep test logs of our devices before sending them out - it would help if you could provide me with a serial number of your device so I can check it, but I don't expect that it failed testing as we perform a final check before sending each product. I hope this helps
  • Evok - Websocket bugs/problems

    3
    0 Votes
    3 Posts
    2k Views
    S
    Follow-up on this one: Bullet 1 and 2 are still a problem. Unipi people, can you please comment on this ? Bullet 3: When changing a relay state I get an array back with all relay states of that group. This was a problem because I wanted to propagate the state change to MQTT. I solved this by looping over the array and returning every state. Although this creates a little overhead, MQTT is fast enough to handle.
  • Analog Input - Evok Settings are not clear

    2
    0 Votes
    2 Posts
    1k Views
    T
    @seecosmea If you wish, you can set a lower bit resolution to get faster read of the AI. The correction is stored in the onboard memory (corr_rom and corr_addr), if you comment these out, you can set it manually using the correction parameter. Ignore the gain parameter.
  • JSON Bulk not working

    4
    0 Votes
    4 Posts
    2k Views
    Martin KudláčekM
    Hello @gradient, we can confirm, that the provided script doesn't turn off all relays, as it should. If a delay of at least 7.5ms is inserted between the commads, the result is as expected. We will look into this, but I cannot say when the fix will be released. Thank you for understanding, Martin
  • UniPian Neuron OS on UniPi 1.1

    3
    0 Votes
    3 Posts
    2k Views
    M
    Ok. When you write it like that it makes sence :). I have readed UniPi 1st generation -> This is the same image as for Neurons -> Click -> Choosed image only with Evok. Opensource images was not familiar for me as I was looking for prepared image. Maybe try to make it more obvious and place guide from git hub on the same page, to make it consistent. Anyway thank you for your reply.
  • Axon M505 bluetooth

    3
    0 Votes
    3 Posts
    2k Views
    Vesa KauppinenV
    @martin-kudláček said in Axon M505 bluetooth: Could you please share with us your intention, so I can point you to proper solution? Hi, We have developed our own software for Axon. We would now like to have Bluetooth enabled. With these instructions (http://wiki.friendlyarm.com/wiki/index.php/NanoPi_NEO_Plus2#Bluetooth), we have not been able to do it work. I would be very grateful if I could get specific instructions for starting Bluetooth. Also ping @TomasKnot /Vesa
  • Websocket connection dropping

    13
    0 Votes
    13 Posts
    7k Views
    T
    It should only disconnect if either a certain number of requests fails to reach the client; or no successful messages have been sent over >10 minutes, while there have been failures during that time. The actual implementation/behaviour is from the tornado.websocket library, albeit we use a slightly older version of Tornado. If you do have the time to investigate further we would quite welcome the feedback. We have put this on our list of things to improve in the future, but right now I can't give you any more specifics.
  • Wall switch - with Evok

    2
    0 Votes
    2 Posts
    1k Views
    Martin KudláčekM
    Hello @devmicha, The infrastructure looks like this: IOs -> (SPI) -> ModbusTCP server -> (ModbusTCP) -> Evok -> (REST, WebSockets,...) -> your code The ModbusTCP server (unipitcp service) is polling the complete status of underlying HW via SPI. This happens very quickly, in less than milisecond interval. The Evok aggregates data from the ModbusTCP server and from the owfs (for 1-Wire devices). Your application can poll data from the Evok in multiple ways (REST, WebSockets,...) As you can see, the Evok doesn't communicate with the HW directly. We discussed the possibility of custom software pulling the SPI in this thread: https://forum.unipi.technology/topic/711/reading-spidev I fully understand your concerns about infinite polling data over GET requests. This is generally slow and causes high load on the PLC. The WebSocket offers you a way to subscribe to updates of the IO. You can poll the complete status of the PLC at any time and yet you can listen to updates and act accordingly. Check the documentation and example: https://evok-9.api-docs.io/1.08/ubmjnyexu77wxwo4q/websocket. Martin
  • EVOK TCP-Modbus only responding to loopback address

    6
    0 Votes
    6 Posts
    3k Views
    T
    @martin-kudláček Already noted on the prepared knowledge base.
  • Can not install EVOK due to dependencies

    23
    0 Votes
    23 Posts
    14k Views
    Martin KudláčekM
    Hooray @alydersen! Thanks for the feedback, we will update the documentation. Martin
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • Node-RED flow -- EVOK to MQTT to EVOK

    1
    1
    1 Votes
    1 Posts
    2k Views
    No one has replied
  • This topic is deleted!

    4
    0 Votes
    4 Posts
    88 Views
  • Evok on Axon

    3
    0 Votes
    3 Posts
    2k Views
    M
    @tomasknot Thank you for quick reply. Sounds great - it's useful to have Evok software on Axon.
  • Cannot see 1wire sensor in EVOK

    2
    0 Votes
    2 Posts
    1k Views
    T
    Hi @bibabutzemann! No need to worry about doing something wrong, the setup process is not entirely intuitive. As far as I can see all the steps you've taken are correct. I have tested the device just now with the latest version, and can confirm that it does work correctly. Could you mention which sensor you are using - and, if it is not a premade RJ45 one, take a photo of your cabling? At this point an error in the physical layer appears the most likely.
  • Unipispi (neuron) kernel module on latest raspbian

    15
    0 Votes
    15 Posts
    6k Views
    T
    @majorcsa Unfortunately not, the updates have broken our driver three times within the past year, and so even if it is technically easy to do with a simple build script, it's not feasible for the process to be automated in such a way. The kernel updates by their nature change the entire API around which our driver is built, often changing things like includes, data structures, macros, function signatures etc. The process is somehow formalised by how the linking process for Linux drivers works, namely the use of a symbol table, but again the table itself changes quite a lot. Not all changes will break the module, but many have. This is the same reason why Raspbian itself only updates to one version in ~20, and is many updates behind the latest, as it always needs to be tested (and updated) for compatibility.
  • Reading spidev

    8
    0 Votes
    8 Posts
    5k Views
    Martijn HemeryckM
    Thanks for the reply. Since my last posts, I have been fiddling around with the setup and noticed that when I directly poll the modbus tcp server, the updated state is made available almost instantaneously. My issue is really on the polling side of the home assistant visualization I am using. I have now started a project to do the polling in a separate server, that then pushes out any changes in the form of an event via MQTT, see https://github.com/mhemeryck/unipusher . It currently works as a proof of concept for a single toggle switch, I am now looking into how I can make it more scalable to all kinds of inputs / outputs. I'll get back here if this ever works out :) EDIT: given it's not really unipi specific, I decided to rename it to modbridge, see https://github.com/mhemeryck/modbridge