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

Companion treating X12S ACCESS ISRM like XJT #2383

Closed
1 task done
rburrow87 opened this issue Sep 27, 2022 · 3 comments · Fixed by #3050
Closed
1 task done

Companion treating X12S ACCESS ISRM like XJT #2383

rburrow87 opened this issue Sep 27, 2022 · 3 comments · Fixed by #3050
Labels
bug 🪲 Something isn't working companion Related to the companion software

Comments

@rburrow87
Copy link

rburrow87 commented Sep 27, 2022

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

I just realized I never submitted this as a bug and was probably forgotten in a PR comment from a while back #2019 (comment)

Okay now that you made me look at my old post, maybe it's caused by something else 😛 Almost seems like it's treating the X12S like the internal module is set to XJT instead of ISRM even though it's set to ISRM.

This is what the X12S ISRM radio writes:

moduleData: 
  0:
     type: TYPE_ISRM_PXX2
     subType: ACCESS
     channelsStart: 0
     channelsCount: 16
     failsafeMode: NOPULSES
     mod: 
        pxx2: 
           receivers: 0
           racingMode: 0
           receiverName: 
              0:
                 val: "SR6"

This is how Companion 2.8 reads it in (notice it offers the Antenna option as if it's treating it like the internal module is set to XJT and not ISRM (and I made sure it's set to ISRM)):

image

So this is how Companion 2.8 writes it back out:

moduleData:
 0:
   type: TYPE_ISRM_PXX2
   subType: ACCESS
   channelsStart: 0
   channelsCount: 16
   failsafeMode: NOPULSES
   mod:
     pxx2:
       receivers: 0
       racingMode: 0

But Companion 2.8 still reads in and writes out fine with my X9D+2019:

image

Version

Nightly (Please give date/commit below)

Transmitter

FrSky X12 w/ISRM upgrade

@rburrow87 rburrow87 added bug 🪲 Something isn't working triage Bug report awaiting review / sorting labels Sep 27, 2022
@pfeerick pfeerick added companion Related to the companion software and removed triage Bug report awaiting review / sorting labels Sep 27, 2022
@elecpower
Copy link
Collaborator

elecpower commented Sep 30, 2022

There is also a reference to antenna in Radio Settings hardware tab that does not appear in the radio simulator

image

This is displayed based on

case HasAntennaChoice:
      return ((IS_FAMILY_HORUS_OR_T16(board) && board != Board::BOARD_X10_EXPRESS) || (IS_TARANIS_XLITE(board) && !IS_TARANIS_XLITES(board))) ? true : false;

The model setup antenna is displayed based on

        if (moduleIdx == 0 && HAS_EXTERNAL_ANTENNA(board) && generalSettings.antennaMode == GeneralSettings::ANTENNA_MODE_PER_MODEL)
          mask |= MASK_ANTENNA;
inline bool HAS_EXTERNAL_ANTENNA(Board::Type board)
{
  return (board == Board::BOARD_X10 || board == Board::BOARD_HORUS_X12S || (IS_TARANIS_XLITE(board) && !IS_TARANIS_XLITES(board)));
}

So I need some guidance here as to the rules to apply in Radio Settings and Model Setup Internal Module before tackling a fix.

@pfeerick
Copy link
Member

pfeerick commented Sep 30, 2022

Need to consider #1765 and associated issue #1185 for that latter point I think.

@elecpower
Copy link
Collaborator

Looks like best for me to wait until 1765 is merged and see what Companion tweaks are necessary to match the radios

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.

3 participants