Why xethru returns data without end byte?

Discussion in 'Module Connector (MC)' started by YuriiKulyk, Dec 3, 2019.

  1. YuriiKulyk

    YuriiKulyk New Member

    I have some questions about xetthru work
    1. Why some messages came without end byte?
    for example
    7d:50:6c:a1:75:23:2c:01:17:00:01:00:00:00:00:00:00:00:5d:4c:19:3f
    here message has start byte 7d but hasn't end byte, just 3f
    2. Is there any way to connect to device remotely (like to server)?
    3. Is there any way to identify device or set static IP for it?
    4. I have tried to decode byte code with end byte and got this result
    {'counter': 2268206, 'state_code': 1, 'RespirationsPerMinute': 0.0, 'distance': 0.4778558313846588, 'SignalQuality': 8, 'MovementSlow': 81.95458221435547, 'MovementFast': 29.5238094329834}
    does it look like correct data?
     
    Last edited: Dec 3, 2019
  2. Charlie Shao

    Charlie Shao Moderator Staff Member