-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configuration not loading into JMRI properly #5
Comments
Do you have the same versions on both?
Le mer. 12 août 2020 à 06:39, ggee <notifications@github.com> a écrit :
… Update 1: Interesting find. This problem only occurs if I open JMRI on the
RPi. If I open JMRI on my Windows PC and connect to the gateway, all looks
fine.
[image: image]
<https://user-images.githubusercontent.com/4544293/89975182-1ad79400-dc33-11ea-8d9a-dd81f564f01a.png>
Update 2: Well, I crashed the gateway and when I restarted and refreshed
the node list, both JMRI show garbled content.
[image: image]
<https://user-images.githubusercontent.com/4544293/89975601-28d9e480-dc34-11ea-811d-c7ad404c91d3.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3PEQKIBHO6IUROXTNOYOLSAIMGZANCNFSM4P37XT2Q>
.
|
Yes, both have 4.20. |
This doesn't seem to be specific to RR-duino. I tried the cmri_net_serial and see the same problem. When I look at the stdout of the openlcb_gateway.py, it shows this. I don't know the protocol, so I can't tell if it is correct or not.
|
Hmm it looks like the last string is always missing the terminal null character. |
I commited a fix for that, hopefully. |
I can still reproduce.
NOTES:
So not sure if this is a JMRI issue or a sync phase issue. |
I have a fix for the write that causes a crash but I need some input from the openlcb guys. Stay tuned. |
OK can you test the latest git, it should be fixed! |
I think this is fixed now. |
Node information in JMRI is invalid.
When trying to 'Open Configuration dialog', nothing appears.
The text was updated successfully, but these errors were encountered: