-
Notifications
You must be signed in to change notification settings - Fork 41
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
Wrong ID read from softrf Fanet #32
Comments
You have a really old version of GXairCom. Try to upgrade to version +4
El lun., 22 de febrero de 2021 17:32, Tenz <notifications@github.com>
escribió:
… Don't know if it is a real issue or maybe a problem of softrf mark ii
firmware but I get the wrong ID from all my devices set to fanet while
receiving with GXAir.
Eg. device real ID 0D3724 read as 073724
[image: 20210221_234503]
<https://user-images.githubusercontent.com/12269827/108783720-3f131680-756e-11eb-9d22-f194bf7e6a90.jpg>
[image: Inked20210221_234522_LI]
<https://user-images.githubusercontent.com/12269827/108783817-6bc72e00-756e-11eb-948c-b9bd05494c92.jpg>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#32>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AQGJZSTXJ3Z3EP7CPWAXCB3TALSPXANCNFSM4YBOACOQ>
.
|
Yep sorry that was old test, now I updated but I'm having the same problem with v.4.5.1 installed. same ID one side: 3C003C and GxAirCom get 07003C ... thanks |
That is actually all OK and fully intended. Older versions of GXAircom used a FANET Id with 07... Since a while GXAircom has its own FANET manufacturer ID and now it begins with 08.... |
But my other two devices are softrf not gxaircom.. seems the first 3 values are not decoded properly.. maybe I’m missing some concepts.. thanks |
Don't know if it is a real issue or maybe a problem of softrf mark ii firmware but I get the wrong ID from all my devices set to fanet while receiving with GXAir.
Eg. device real ID 0D3724 read as 073724
The text was updated successfully, but these errors were encountered: