Skip to content
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

Under X9D-2.3.1 in companion, models with XJTD8 in .otx becomes XJTD16 #6912

Closed
dev-fred opened this issue Oct 8, 2019 · 6 comments · Fixed by #6919
Closed

Under X9D-2.3.1 in companion, models with XJTD8 in .otx becomes XJTD16 #6912

dev-fred opened this issue Oct 8, 2019 · 6 comments · Fixed by #6919

Comments

@dev-fred
Copy link

dev-fred commented Oct 8, 2019

Describe the bug
In 2.3.1 after a transfer of .otx file in a X9D, all models using a XJTD8 internal are converted to XJTD16

To Reproduce
1-From companion open a model with internal RF XJTD8
2. run the simu you will see D16

D8-D16

@dev-fred
Copy link
Author

dev-fred commented Oct 8, 2019

the problem is in companion

@dev-fred dev-fred closed this as completed Oct 8, 2019
@dev-fred
Copy link
Author

dev-fred commented Oct 8, 2019

In fact the problem can be reproduced directly in companion and it's not linked to the firmware or the simulator.
To reproduce:
1- create a model with XJT D8 internal
2- save it
3-close the otx windows
4- open the otx file
5- the HF internal is now in XJT D16

@dev-fred dev-fred reopened this Oct 8, 2019
@dev-fred
Copy link
Author

dev-fred commented Oct 8, 2019

It's really an issue, sorry

@dev-fred dev-fred changed the title Under X9D models with XJTD8 in .otx becomes XJTD16 in radio Under X9D-2.3.1 in companion, models with XJTD8 in .otx becomes XJTD16 Oct 8, 2019
@dev-fred
Copy link
Author

dev-fred commented Oct 8, 2019

Idem on X9D+, X10 so it's not only X9D

@notlebowski
Copy link

Indeed... when did that happen?
I don't think it was in the 2.3.0 nightlies...

@3djc
Copy link
Contributor

3djc commented Oct 9, 2019

At least 2 monthes ago, according to git blame

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants