Project

General

Profile

Actions

Task #3243

open
TJ DP

Task #2941: Detailed Design

Task #2952: Embedded SW-Development

Task #3032: GW2.0 Codebase readiness(Release 1.0)

ConfigPacket (Split, Delay)

Task #3243: ConfigPacket (Split, Delay)

Added by Thomas Joseph about 1 month ago. Updated 26 days ago.

Status:
In Progress
Priority:
High
Assignee:
Start date:
26/01/2026
Due date:
06/02/2026 (33 days late)
% Done:

80%

Estimated time:
Spent time:

Description

This is a constraint observed with N720 module

TJ Updated by Thomas Joseph about 1 month ago Actions #1

  • Due date set to 06/02/2026

TJ Updated by Thomas Joseph about 1 month ago Actions #2

  • Subject changed from ConfigPacket (Spli, Delay) to ConfigPacket (Split, Delay)

TJ Updated by Thomas Joseph 30 days ago · Edited Actions #3

E-REMOS sending config packet of size approx. 1676bytes. Device(N720) is receiving in two packets of size 1318 byte and 358 byte respectively with a delay inserted between them of 500ms. The arrival TCP packet is not indicated by an event as the host interface is through UART. AT TCPREAD (3072) This reception is called synchronous. 115200 = 10uS for 1 Byte

@DEVI PRIYAA : Please describe issue and resolution here or in a document

TJ Updated by Thomas Joseph 30 days ago Actions #4

  • Status changed from Analysis Started to In Progress

DP Updated by DEVI PRIYAA 26 days ago · Edited Actions #5

  • % Done changed from 0 to 80

As discussed with venu sir, the Sw release will contain the receiving the config packet in the synchronous mode.

If packet received timeout expires, it request again, no halt will happen because of that delay. This has been tested.

Further in the future release, need to make it in asynchronous mode

Actions

Also available in: PDF Atom