Internal module not set to ISRM up upgrade of on X lite PRO

[timemaster5]

Is there an existing issue for this problem?

• I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

I've built the latest edgetx 2.7.0 f79978b with bluetooth,crossfire, ghost, noheli, internalmulti, internalaccess, multimodule and luac options, but I can't choose an ISRM module in the model settings.

Expected Behavior

As in the previous versions, I would also like to use the internal ISRM2 module on 2.7.0 :)

Steps To Reproduce

The only thing is to download the official firmware release and test it on X lite PRO. But to be on the same page, I use these options: cmake -Wno-dev -DPCB=XLITES -DHELI=NO -DLUA=YES -DGVARS=YES -DFONT=SQT5 -DMODULE_PROTOCOL_FLEX=YES -DAFHDS3=NO ../

Version

2.7.0

Transmitter

FrSky X-Lite / S / Pro

Anything else?

No response

[pfeerick]

So just to double check, when you go into SYS -> Hardware -> Internal RF ISRM isn't an option there? I don't have that hardware, so am relying on Simulator for initial analysis

companion_QvUOTyHdYA.mp4

[timemaster5]

All right, stupid me. I didn't come across this option before on this radio. So when I set the ISRM there, all is fine, except I still have to go into ISRM options to select an external antenna. Even though I don't have an XJT, I immediately fell in love with the option to ask whether I use an external or internal antenna at the beginning :)

I was upgrading and saw the updating EEPROM message. Maybe that's why I wasn't expecting that, and not being able to select ACCESS protocol in the model menu gave me the impression that the support is just not there.

So is it really a bug? I mean, is it supposed to migrate these settings? I know this was a huge update. Maybe it wasn't possible to migrate everything.

And thank you very much for it. It works great, and many options are now much more straightforward. For example, the Hardware menu is now more helpful. I really didn't need to do anything in there before.

[raphaelcoeffic]

@timemaster5 so what you’re basically saying is that the internal module setting was not correct after upgrade, right?

[raphaelcoeffic]

By the way, can you please provide the exact command you used with CMake? It might be related to the default module & CMake.

[timemaster5]

@timemaster5 so what you’re basically saying is that the internal module setting was not correct after upgrade, right?

yes, I've lost bound receivers also..
EDIT: I haven't lost my bindings actually, it seemed so at the first sight, but when I powered the model on, all was ok. I lost only failsafe settings.

By the way, can you please provide the exact command you used with CMake? It might be related to the default module & CMake.

$ cmake -LH ../ > cmake-options.txt
$ cmake -Wno-dev -DPCB=XLITES -DHELI=NO -DLUA=YES -DGVARS=YES -DFONT=SQT5 -DMODULE_PROTOCOL_FLEX=YES -DAFHDS3=NO ../
$ make -j`nproc` firmware