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

CPN: LS and RS not set correctly after reading Model and settings from radio #3982

Closed
1 task done
ParkerEde opened this issue Aug 29, 2023 · 7 comments · Fixed by #4406
Closed
1 task done

CPN: LS and RS not set correctly after reading Model and settings from radio #3982

ParkerEde opened this issue Aug 29, 2023 · 7 comments · Fixed by #4406
Labels
bug 🪲 Something isn't working companion Related to the companion software

Comments

@ParkerEde
Copy link
Contributor

ParkerEde commented Aug 29, 2023

Is there an existing issue for this problem?

  • I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Companion

Current Behavior

in Companion in the hardware settings the sliders LS and RS not set correctly after reading Model and settings from radio

Radio:
image

Companion:
image

Expected Behavior

in the Comapnion the settings from the radio profile should be taken over correctly after reading the model and radio settings

Steps To Reproduce

  • build companion with RM TX16S with current main
  • make sure that in the radio under Hardware/Sliders LS and RS is assigned correctly and is no longer set to "none"
  • start companion
  • read modell and radio settings
  • observe Radio Settings/TAB Hardware
  • both Slider LS and RS are set to "none"

Version

Nightly (Please give date/commit below)

Transmitter

Radiomaster TX16S / TX16SMK2

Operating System (OS)

Windows

OS Version

Win11

Anything else?

current main

@ParkerEde ParkerEde added bug 🪲 Something isn't working triage Bug report awaiting review / sorting labels Aug 29, 2023
@pfeerick
Copy link
Member

pfeerick commented Aug 30, 2023 via email

@3djc
Copy link
Collaborator

3djc commented Aug 30, 2023

Sound like the return of the vengeance of adc refactor part II

@elecpower
Copy link
Collaborator

and #3870 will completely break it again

@3djc
Copy link
Collaborator

3djc commented Aug 30, 2023

Indeed, no point in fixing before 3870 gets in, and maybe try to see if we can ease companion task by parsing hardware definition data for it (until full yaml definitions get worked on)

@elecpower
Copy link
Collaborator

The Companion refactor will parse the hw json files for 2.10 onwards but as usual the biggest pain point is data mapping from the earlier hard coded definitions.

@3djc
Copy link
Collaborator

3djc commented Aug 30, 2023

We are currently generating json on the fly per radio, with much more info than you need. We probably should try to make one file for companion use that gives all the info for all radio at once

@elecpower
Copy link
Collaborator

It is my understanding that on the fly is only a temporary method.
I have some code that handles a permanent json file per radio and ignores the entries that Companion does not care about.
I'm not in favour of an all radios config file as differences will inevitably occur in maintenance.

@pfeerick pfeerick removed the triage Bug report awaiting review / sorting label Oct 9, 2023
@elecpower elecpower added the companion Related to the companion software label Jan 5, 2024
@elecpower elecpower linked a pull request Jan 5, 2024 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working companion Related to the companion software
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants