• Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Neuron M303, My Digital Input is not working

    UniPi Neuron Series
    2
    2
    68
    Loading More Posts
    • 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.
    • A
      AllanL last edited by

      I bought a UniPi Neuron M303 a year ago.
      My plan was to connect all my door and window magnetic switches in houses to this device and use it as alarm points in my smart home from Logic Group.
      I have installed EVOK and updated it to the latest version.

      Unfortunately, I have not succeeded in getting the inputs to show a status other than Off.
      I have tried putting a wire directly from ground to an input.
      The M303 does not respond to it by turning on the corresponding LED.
      I can't see it in the web interface either.
      ![M303 Input.png](EACCES: permission denied, copyfile '/tmp/I7W3Wl1UMzfoP1ttndWXovlc.png' -> '/usr/src/app/public/uploads/files/1662540511522-m303-input.png')
      Is there something I'm doing wrong

      A little more info
      Watch gives no trace
      "watch -n 0.1 cat /run/unipi/io_group1/di_1_01/di_value"

      I have also tested the debounce time and that is 50ms
      "unipi@M303-sn28:~$ mbpoll 127.0.0.1 -a 0 -0 -1 -r 1136 mbpoll 1.4-25 - FieldTalk(tm) Modbus(R) Master Simulator
      Copyright © 2015-2019 Pascal JEAN, https://github.com/epsilonrt/mbpoll
      This program comes with ABSOLUTELY NO WARRANTY.
      This is free software, and you are welcome to redistribute it
      under certain conditions; type 'mbpoll -w' for details.

      Protocol configuration: Modbus TCP
      Slave configuration...: address = [0]
      start reference = 1136, count = 1
      Communication.........: 127.0.0.1, port 502, t/o 1.00 s, poll rate 1000 ms
      Data type.............: 16-bit register, output (holding) register table

      -- Polling slave 0...
      [1136]: 50

      unipi@M303-sn28:~$ mbpoll 127.0.0.1 -a 0 -0 -1 -r 1137
      mbpoll 1.4-25 - FieldTalk(tm) Modbus(R) Master Simulator
      Copyright © 2015-2019 Pascal JEAN, https://github.com/epsilonrt/mbpoll
      This program comes with ABSOLUTELY NO WARRANTY.
      This is free software, and you are welcome to redistribute it
      under certain conditions; type 'mbpoll -w' for details.

      Protocol configuration: Modbus TCP
      Slave configuration...: address = [0]
      start reference = 1137, count = 1
      Communication.........: 127.0.0.1, port 502, t/o 1.00 s, poll rate 1000 ms
      Data type.............: 16-bit register, output (holding) register table

      -- Polling slave 0...
      [1137]: 50

      unipi@M303-sn28:~$ mbpoll 127.0.0.1 -a 0 -0 -1 -r 1130
      mbpoll 1.4-25 - FieldTalk(tm) Modbus(R) Master Simulator
      Copyright © 2015-2019 Pascal JEAN, https://github.com/epsilonrt/mbpoll
      This program comes with ABSOLUTELY NO WARRANTY.
      This is free software, and you are welcome to redistribute it
      under certain conditions; type 'mbpoll -w' for details.

      Protocol configuration: Modbus TCP
      Slave configuration...: address = [0]
      start reference = 1130, count = 1
      Communication.........: 127.0.0.1, port 502, t/o 1.00 s, poll rate 1000 ms
      Data type.............: 16-bit register, output (holding) register table

      -- Polling slave 0...
      [1130]: 50
      "

      A 1 Reply Last reply Reply Quote 0
      • A
        AVsetula administrators @AllanL last edited by

        Hi @AllanL,

        From your description, I assume it's a wrong connection. The digital inputs on our units are not potential-free, but instead respond to voltages in the range of 7 to 35 VDC. At the same time, it is necessary that the negative pole of the voltage source is connected to DIGND.

        More information can be found in the article dedicated to digital inputs:
        https://kb.unipi.technology/en:hw:02-neuron:description-of-io:01-description-of-di

        Best regards,
        Antonin

        1 Reply Last reply Reply Quote 0
        • First post
          Last post