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

    not all extension ports are recognized

    UniPi Extension Modules (Axon & Neuron)
    2
    3
    1351
    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.
    • T
      tja last edited by

      hi all again,

      my build with L203, 2x xS30, 1x xS40 communicates now without any trouble so far.
      today i started to wire all the rest of the buttons in the house and i noticed that the DIs of the xS30 go from 01 to 18 but 19 to 24 are missing from evoks webapp and are not reported via webservices either (output sorted for convenience):

      Device: input / Circuit: 1_01 / Value: 0
      Device: input / Circuit: 1_02 / Value: 0
      Device: input / Circuit: 1_03 / Value: 0
      Device: input / Circuit: 1_04 / Value: 0
      Device: input / Circuit: 2_01 / Value: 0
      Device: input / Circuit: 2_02 / Value: 0
      Device: input / Circuit: 2_03 / Value: 0
      Device: input / Circuit: 2_04 / Value: 0
      Device: input / Circuit: 2_05 / Value: 0
      Device: input / Circuit: 2_06 / Value: 0
      Device: input / Circuit: 2_07 / Value: 0
      Device: input / Circuit: 2_08 / Value: 0
      Device: input / Circuit: 2_09 / Value: 0
      Device: input / Circuit: 2_10 / Value: 0
      Device: input / Circuit: 2_11 / Value: 0
      Device: input / Circuit: 2_12 / Value: 0
      Device: input / Circuit: 2_13 / Value: 0
      Device: input / Circuit: 2_14 / Value: 0
      Device: input / Circuit: 2_15 / Value: 0
      Device: input / Circuit: 2_16 / Value: 0
      Device: input / Circuit: 3_01 / Value: 0
      Device: input / Circuit: 3_02 / Value: 0
      Device: input / Circuit: 3_03 / Value: 0
      Device: input / Circuit: 3_04 / Value: 0
      Device: input / Circuit: 3_05 / Value: 0
      Device: input / Circuit: 3_06 / Value: 0
      Device: input / Circuit: 3_07 / Value: 0
      Device: input / Circuit: 3_08 / Value: 0
      Device: input / Circuit: 3_09 / Value: 0
      Device: input / Circuit: 3_10 / Value: 0
      Device: input / Circuit: 3_11 / Value: 0
      Device: input / Circuit: 3_12 / Value: 0
      Device: input / Circuit: 3_13 / Value: 0
      Device: input / Circuit: 3_14 / Value: 0
      Device: input / Circuit: 3_15 / Value: 0
      Device: input / Circuit: 3_16 / Value: 0
      Device: input / Circuit: UART_1_2_01 / Value: 0
      Device: input / Circuit: UART_1_2_02 / Value: 0
      Device: input / Circuit: UART_1_2_03 / Value: 0
      Device: input / Circuit: UART_1_2_04 / Value: 0
      Device: input / Circuit: UART_1_2_05 / Value: 0
      Device: input / Circuit: UART_1_2_06 / Value: 0
      Device: input / Circuit: UART_1_2_07 / Value: 0
      Device: input / Circuit: UART_1_2_08 / Value: 0
      Device: input / Circuit: UART_1_2_09 / Value: 0
      Device: input / Circuit: UART_1_2_10 / Value: 0
      Device: input / Circuit: UART_1_2_11 / Value: 0
      Device: input / Circuit: UART_1_2_12 / Value: 0
      Device: input / Circuit: UART_1_2_13 / Value: 0
      Device: input / Circuit: UART_1_2_14 / Value: 0
      Device: input / Circuit: UART_1_2_15 / Value: 0
      Device: input / Circuit: UART_1_2_16 / Value: 0
      Device: input / Circuit: UART_1_2_17 / Value: 0
      Device: input / Circuit: UART_1_2_18 / Value: 0
      Device: input / Circuit: UART_2_3_01 / Value: 0
      Device: input / Circuit: UART_2_3_02 / Value: 0
      Device: input / Circuit: UART_2_3_03 / Value: 0
      Device: input / Circuit: UART_2_3_04 / Value: 0
      Device: input / Circuit: UART_2_3_05 / Value: 0
      Device: input / Circuit: UART_2_3_06 / Value: 0
      Device: input / Circuit: UART_2_3_07 / Value: 0
      Device: input / Circuit: UART_2_3_08 / Value: 0
      Device: input / Circuit: UART_2_3_09 / Value: 0
      Device: input / Circuit: UART_2_3_10 / Value: 0
      Device: input / Circuit: UART_2_3_11 / Value: 0
      Device: input / Circuit: UART_2_3_12 / Value: 0
      Device: input / Circuit: UART_2_3_13 / Value: 0
      Device: input / Circuit: UART_2_3_14 / Value: 0
      Device: input / Circuit: UART_2_3_15 / Value: 0
      Device: input / Circuit: UART_2_3_16 / Value: 0
      Device: input / Circuit: UART_2_3_17 / Value: 0
      Device: input / Circuit: UART_2_3_18 / Value: 0
      Device: input / Circuit: UART_3_4_01 / Value: 0
      Device: input / Circuit: UART_3_4_02 / Value: 0
      Device: input / Circuit: UART_3_4_03 / Value: 0
      Device: input / Circuit: UART_3_4_04 / Value: 0
      Device: input / Circuit: UART_3_4_05 / Value: 0
      Device: input / Circuit: UART_3_4_06 / Value: 0
      Device: input / Circuit: UART_3_4_07 / Value: 0
      Device: input / Circuit: UART_3_4_08 / Value: 0
      

      can someone enlighten me about this ?

      tia,tja...

      1 Reply Last reply Reply Quote 0
      • T
        TomasKnot last edited by

        This is a known recent issue which was fixed in a recent release. It was caused by the YAML parsing library we use being updated, which broke reading overlaid inputs/outputs in xS30 extension.

        See https://github.com/UniPiTechnology/evok/commit/3c32d569282a6238998bac3b4d226b514fcd283e, as per the tag fixed in 2.0.5.

        1 Reply Last reply Reply Quote 0
        • T
          tja last edited by

          hi tomas,

          2.05a seems to have fixed this error too - the extensions are fully populated and the send events now (the old version didnt send events too as i had to discover).

          thx for helping,
          wbr,tja...

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