Update p2000.py #46
Open
Update p2000.py #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With multiple capcodes, the additional info was not put in the send message. bug was triggered by only receiving 1 receiver, although there were multiple capcodes
Open
Dinges28
commented
Dec 14, 2022
|
and now it posts again 1 receivers.. not multiple messages... @cyberjunky What am I doing wrong?? |
|
I quess what i see is that it only sees the last capcode before the |ALN| in the flex message: FLEX|2022-12-16 14:32:37|1600/2/K/A|08.029|002029568 000806240 000806221 000612120 000610850 000610835 000610825 000610823 000605969 000605333 000605310 000603940|ALN|P 1 BON-12 (Middel HV) HV weg letsel N36 - N36 25,5 Beerze 041199 053531 042270 |
|
It repeats reading the value, till it reaches the last capcode, and that description is send in the message.. instead of adding all the descriptions to the parameter |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With multiple capcodes, the additional info was not put in the send message. bug was triggered by only receiving 1 receiver, although there were multiple capcodes