Software/2020TPC-SW
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

The 2020TPC is unable to receive the Dubuque Protocol with a 100ms holdoff #3

New issue
Closed
opened 2025-09-20 19:02:37 +00:00 by Joe · 2 comments
Joe commented 2025-09-20 19:02:37 +00:00
Owner
Copy link

When testing the Dubuque Protocol with a 100ms holdoff, we observed that the 2020TPC could not receive these tags until the last one was sent. This is because the Xxx_Tag_Sensor_Bit_Stream_Timers have timeouts that are too long, and the next packet gets included with the first.

To resolve this defect, make the timeout the same as it is on the 32ESPecial.

When testing the [Dubuque Protocol with a 100ms holdoff](https://git.ktag.clubk.club/Software/SystemK/pulls/6), we observed that the 2020TPC could not receive these tags until the last one was sent. This is because the [Xxx_Tag_Sensor_Bit_Stream_Timer](https://git.ktag.clubk.club/Software/SystemK/pulls/6)s have timeouts that are too long, and the next packet gets included with the first. To resolve this defect, make the timeout [the same as it is on the 32ESPecial](https://git.ktag.clubk.club/Software/2024A-SW/src/branch/main/components/IR/IR.c#L65).
Joe commented 2025-09-20 19:07:26 +00:00
Author
Owner
Copy link

Workaround

If you have a blaster with a newer versions of System K that uses the 100ms holdoff, and you are playing against an opponent with a 2020TPC that does not have the fix for this issue, simply don't pull the trigger so quickly.

**Workaround** If you have a blaster with a newer versions of System K that uses the 100ms holdoff, and you are playing against an opponent with a 2020TPC that does not have the fix for this issue, simply *don't pull the trigger so quickly*.
Joe commented 2025-09-20 21:04:05 +00:00
Author
Owner
Copy link

Here's the fix: I had to change the Period from 500000μs (!!?) to 20000μs for each Xxx_Tag_Sensor_Bit_Stream_Timer. Now the 2020TPC works just like the 32ESPecial.

Screenshot 2025-09-20 155845.png

Here's the fix: I had to change the `Period` from 500000μs (!!?) to 20000μs for each `Xxx_Tag_Sensor_Bit_Stream_Timer`. Now the 2020TPC works just like the 32ESPecial. ![Screenshot 2025-09-20 155845.png](/attachments/8208db61-bc21-4cbb-aa92-620a25457c89)
Screenshot 2025-09-20 155845.png
117 KiB
Joe closed this issue 2025-09-20 21:29:57 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Software/2020TPC-SW#3
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?