• HOST_franji1 (HOST Engineering)

    MQTT Broker latencies must be considered also. Latency times occur on both the publish and the subscribe sides independently, sometimes by design (i.e. by $ervice level).

  • Linuxdept (Customer)

    we were getting 500ms delays out of the Click much to slow for our application. we are trying to see Encoder pulses. The Click itself was Keeping up Just when it was Publishing to MQTT was the large latencies we need to be able to handle 2,000 Pulses a second. any idea's ?

    • Garry (Customer)

      MQTT protocol is not for remote IO or real-time (deterministic) applications.

      So your application requires a 2Khz update frequency over a network?

      Ethernet IP comes to mind for Remote IO.

      Regards,

      Garry

      • z28z34man (Customer)

        Even Ethernet IP isn't deterministic and at 2khz would calculate to a .25ms rpi time if you needed to see both on and off and that is most likely even faster than the clicks scan time.

         

        What are you trying to do that you need that fast of updates over the network? Could you offload some of that task to the click and just send an integer value of the pulse count at a more reasonable 5-20 ms rpi time over Ethernet ip

        Expand Post

 

Did this information resolve your issue?