Project

General

Profile

Actions
Copy link

Task #3525

open

Communication Protocol Update

Task #3525: Communication Protocol Update

Added by Thomas Joseph 5 months ago. Updated 3 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Mohan Kashyap
Target version:
RHMS-ISTRAC
Start date:
30/03/2026
Due date:
26/06/2026 (about 2 months late)
% Done:

50%

Estimated time:
48:00 h
Spent time:
24:00 h

Updated by Mohan Kashyap 5 months ago Actions
Copy link
 #1

  • Due date set to 10/04/2026
  • Status changed from New to In Progress
  • Target version changed from Future to RHMS-ISTRAC
  • % Done changed from 0 to 50
  • Estimated time set to 48:00 h

Device side implementation done as per message formats

Need to integrate with desktop application

Updated by Mohan Kashyap 5 months ago Actions
Copy link
 #2

  • Due date changed from 10/04/2026 to 15/04/2026

Updated by Thomas Joseph 5 months ago Actions
Copy link
 #3

Please update the doc. in shared folder and add link here. Specify the revisions of s/w and VAS appliocation also

Updated by Thomas Joseph 3 months ago Actions
Copy link
 #4

  • Due date changed from 15/04/2026 to 26/06/2026

Issue : Sometimes, application software is unable to reconnect device

Observations
if the device get disconnected, application requires close and open
some times, the application is showing "connecting..." for a long time. this requires application close and open
with multiple devices, in application., one device dropped after some time (in ISTRAC after two days) again after some time, the second device also got dropped (after two days).
Observed that device was posting as LAN socket LEDs were blinking.
LEDs would be stable if AS is open but bot connected with device, or AS closed
To resolve (1,2,3)

  1. When both nodes have started , they should establish a connection immediately
  2. Either node should detect connection drop and restore immediately
    A permanent loss of connection should indicate in a message in AS, correspondingly an LED indication on device side(ERROR status LED)
    To implement 2 and 3
    nodes should check a "keep alive"
    Time out

Mohan Kashyap, Shiva Leela
Define a protocol , evaluate and implement. Please share a timeline

Actions
Copy link

Also available in: PDF Atom