adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-10-30 22:41:57 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

TCP-connected radio, not seeing message ack checkmarks [meshcomod] #212

New Issue
Closed
opened 2026-10-05 02:03:50 +02:00 by adam · 6 comments
adam commented 2026-10-05 02:03:50 +02:00
Owner
Copy link
Copy source

debug_2026-06-20_193114.json

config: LAN TCP direct to Heltec V4, meshcomod v1.16.0.4.
(this was working w/ direct USB-serial connection to meshcore 1.16; but haven't built a custom meshcore 1.16 wifi firmware yet to see if this is a meshcomod-specifc problem)

Hopefully this log is helpful; I don't see how to correlate the outgoing message to the responses just from the logging.

  • 2026-06-20 23:31:03 outbound message to #dummy, "testing 123".
  • 2026-06-20 23:31:05 ack (or looks to be, from packet analyzer)
  • 2026-06-20 23:31:06 ack (or looks to be, from packet analyzer)
[debug_2026-06-20_193114.json](https://github.com/user-attachments/files/29168945/debug_2026-06-20_193114.json) config: LAN TCP direct to Heltec V4, meshcomod v1.16.0.4. (this was working w/ direct USB-serial connection to meshcore 1.16; but haven't built a custom meshcore 1.16 wifi firmware yet to see if this is a meshcomod-specifc problem) Hopefully this log is helpful; I don't see how to correlate the outgoing message to the responses just from the logging. * `2026-06-20 23:31:03` outbound message to `#dummy`, "testing 123". * `2026-06-20 23:31:05` ack (or looks to be, from packet analyzer) * `2026-06-20 23:31:06` ack (or looks to be, from packet analyzer) <!-- github-sync-id:4708793292 -->
adam closed this issue 2026-10-05 02:03:50 +02:00
adam commented 2026-10-05 02:03:51 +02:00
Author
Owner
Copy link
Copy source

Do you ever see ack checkmarks for any message at all?

Do you ever see ack checkmarks for any message at all? <!-- github-comment-id:4760446233 -->
adam commented 2026-10-05 02:03:52 +02:00
Author
Owner
Copy link
Copy source

Before switching to TCP/meshcomod, yes.
After, none for anything.

Image
Before switching to TCP/meshcomod, yes. After, none for anything. <img width="259" height="341" alt="Image" src="https://github.com/user-attachments/assets/9b2de5d7-44b5-4094-bdaf-468640a9c48e" /> <!-- github-comment-id:4760448483 -->
adam commented 2026-10-05 02:03:53 +02:00
Author
Owner
Copy link
Copy source

Hmmm that leads me to be far more suspicious of the firmware not implementing acks correctly than RemoteTerm. I'll take a look.

Hmmm that leads me to be far more suspicious of the firmware not implementing acks correctly than RemoteTerm. I'll take a look. <!-- github-comment-id:4760457140 -->
adam commented 2026-10-05 02:03:53 +02:00
Author
Owner
Copy link
Copy source

I'm also suspicious of meshcomod; will try building their latest HEAD, and then try building meshcore.

I'm also suspicious of meshcomod; will try building their latest HEAD, and then try building meshcore. <!-- github-comment-id:4760472009 -->
adam commented 2026-10-05 02:03:54 +02:00
Author
Owner
Copy link
Copy source

Looks like a false alarm. meshcomod HEAD (63e5c6) works. The HEAD commit is a garbage data fix, so that would track.

Looks like a false alarm. meshcomod HEAD (63e5c6) works. The HEAD commit is a garbage data fix, so that would track. <!-- github-comment-id:4760493118 -->
adam commented 2026-10-05 02:03:55 +02:00
Author
Owner
Copy link
Copy source

Woot!

Woot! <!-- github-comment-id:4760494971 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#212