Request a firmware build - 2.7.1

[pfeerick]

Ask here if you want/need specific options that are not included in the stock builds. Builds will be uploaded to here (same link as 'By request' below), so check it out before making a request just in case there is already a custom build with your chosen options...

Please remember to specify your transmitter when requesting a build ;)

• Multilingual builds - zip file per transmitter containing all languages built
• Multilingual builds - NOHELI - zip file per transmitter containing all languages built
• By request

[chewi1472]

Hello pfeerick
May i have a built FR for TX16S with no Heli and bluetooth.
Thank you, and have a good day

[ArdSchell]

That would be very nice indeed.
TX16S with bluetooth enabled.
¡ǝɔuɐʌpɐ uı sʞuɐɥʇ

TX16S_EN_BLUETOOTH

[Xanthuz168]

hi, TX16S_En_Bluetooth please... thank you so much..

[pfeerick]

@chewi1472 Apologies for the delay. Available in the specials link in the first post.

cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DBLUETOOTH=Y -DHELI=N -DTRANSLATIONS=FR ..

[pfeerick]

@ArdSchell @Xanthuz168 Apologies for the delay. Available in the specials link in the first post, both with and without heli tab.

cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DBLUETOOTH=Y ..
cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DBLUETOOTH=Y -DHELI=N ..

[ArdSchell]

Hello Pfeerick,

Would be great if you could make a TX16S with bluetooth enabled.
TX16S_EN_BLUETOOTH

Thanks in advance!

Best regards,

Ard

[spiky1]

Hallo Pfeerick,

I tried that before I asked.
Today I tried again but I can only choose between off and XJT, no other choice available.

Firmware loaded is edge-tx x12s a55aff0 with DE.

Also tried 2.7.0 f79978b with the same result.

[spiky1]

@FreeRick With opentx 2.3.15 internal access I can select the ISRM option.

[pfeerick]

You need to go to Radio Settings -> Hardware -> Internal RF and change that to ISRM (per my earlier screenshot). Then your model settings page internal RF list will give OFF and ISRM as options ;)

[spiky1]

@pfeerick some people are slow learners🤷
I found the right place and it now works! 🥂

Thx for your help (and patience!)

[pfeerick]

I wouldn't go quite that far... it is a new option (was introduced in ETX 2.6)... and language barrier can lead to some interesting times also ;) Glad it is all working for you now. Enjoy! :)

[ETHOSWarrier]

Hello,I have a Frsky Horus x10 that i have installed the ISRM RF module in to allow it to run ACCESS firmware but there is no EdgeTx build for it...I found out the hard way when trying the "ACCESS" labelled download but got the wrong PCB error!...

My build would be a standard build like the ones downloadable already....Thanks in Advance...Chris.

[chewi1472]

Hello,
with a standard firmware,
switch on your radio
go to: SYS-->HARDWARE
at the end of the menu -->internal modul: select ISRM.
Go to your model ans select in internal modul what your want: ACCESS or D16.

[ETHOSWarrier]

Thats the issue,The standard firmware bricks the radio and you only get the "Wrong PCB Error"...you cannot start the radio to change anything.This has happened to others so a special build for the IRSM converted x10 is required.

[pfeerick]

So you are saying that if you load the standard firmware , it will brick the radio? As if your radio is a X10 with exchanged RF board, it's still a X10 mainboard, not an X10 Access one. You would then set the internal RF type to ISRM.

[alant101]

Following this with great interest as I have the same transmitter with the IRSM RF and would like to resolve this problem

[pfeerick]

So it's a X10/X10S ACCST mainboard with ISRM RF board? Try the X10 firmware (NOT the X10-ACCESS which is for the Express radios), and then Radio Settings -> Hardware -> Internal RF to set the internal RF to ISRM.

[arfpv]

Has anyone used the TBS Crossfire nano with the Radio master zorro?
I cant seem to run the Lua script. Updated openTX to 2.7.1, still get the same syntax error.

[MadMonkey87]

Hello Pfeerick

I would like a 2.7.1 build for the TX16s with noheli but with LUA_MIXER

Thank you in advance!

[gjhaynes]

Thanks Peter. that makes sense. I would be OK with the EdgeTx Team issuing a disclaimer about consequences of using Custom Scripts. It would be really cool to allow user editing of the Model menu tabs so they only see what is useful to them, e.g. hide Heli and Custom Scripts. Of course, this means a universal build that provides for every option and this may not be an efficient use of hardware resources. Maybe you could check user prefs during startup and load only the relevant optional modules. But I'm sure this is not a trivial task!

[pfeerick]

True. But this is exactly the direction we want to go... hence #1692 However I don't know if this will make 2.8 now as I haven't even started on it and no-one else has raised their hand to work on it yet. 😁 With colorlcd radios having enough space for the firmware to have pretty much all the options enabled, there's no reason not to go that way. For B&W radios, though, it will have to stay as it is as there is simply not enough space.

[gjhaynes]

I'm so impressed with your responsiveness! Even more impressive given the workload you guys must be currently handling.
Long Live EdgeTx !!

[gjhaynes]

Hi Peter. Is there a downloadable 2.8 Companion & Simulator to play with?
Is this something I can create myself with GitPod?

[pfeerick]

Check the github actions pages for the Windows/Mac/Linux builds for the latest companion builds for the main branch. You could build a linux version on GitPod, but that won't help you if on Windows. Basically each build needs to run on the OS it is targeted for - Windows on Windows, Mac on Mac, Linux on Linux.

https://github.com/EdgeTX/edgetx/actions/workflows/win_cpn-64.yml?query=branch%3Amain
https://github.com/EdgeTX/edgetx/actions/workflows/macosx_cpn.yml?query=branch%3Amain
https://github.com/EdgeTX/edgetx/actions/workflows/linux_cpn.yml?query=branch%3Amain

[WizzX-FPV]

Hallo,
I would like to ask for 2.7.1 build for TX16S with:
ppmus
noheli
bluetooth
lua

when can we expect user friendly options selection?
Thank you.

[pfeerick]

@WizzX-FPV Sorry for the delay. Available in the specials link in the first post.

Please let me know if the ppmus option is working properly... I don't know how much testing option has had in the new UI as this is the first build I remember doing for a colorlcd target.

I don't have any idea of the timeline atm, I've been out of the loop for last two weeks but there hadn't been any progress of late. RL getting in the way, etc. Wasn't sure if you wanted lua or the lua custom mixer scripts, so I did both. There has been a misconception (due to how the option was presented) for a long time the LUA checkbox meant support for Lua when it fact it meant enabling Lua custom mixer scripts.

cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DPPM_UNIT=US -DHELI=N -DBLUETOOTH=Y ..
cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DPPM_UNIT=US -DHELI=N -DBLUETOOTH=Y -DLUA_MIXER=Y ..

[ArdSchell]

Hello Pfeerick,

Is the TX16S_EN_BLUETOOTH already available? or am I missing something.
Thanks you for your great help.

Best regards,

Ard

[pfeerick]

No, you're not missing anything... more I've been missing for a while ;) It's up in the special link in first post.

[ArdSchell]

Thanks Pfeerick,

Hope you are oke and welcome back.
Thanks for sharing the files.
:O)

[ArdSchell]

I updated my TX16S to 2.7.1 and it works perfect.
Thanks again Pfeerick.
¡ʇsǝʇɐǝɹƃ ǝɥʇ ɹnoʎ

[Meldinov]

Hi, i habe a problem with the 2.7.1 t-pro HELI. both ES and EN wont boot, the noheli works great.

[pfeerick]

I just checked the HELI EN and ES firmwares from the tpro HELI zip on my own T-Pro (MPM variant) and had no issues with them booting when flashed from the bootloader. So not sure what it's going on there.

[tyxiaotx]

Hello pfeerick,
May I have a build for Jumper T16 with bluetooth enabled? Thank you!

[pfeerick]

Done... check the specials link in the first post.
cmake -Wno-dev -DPCB=X10 -DPCBREV=T16 -DINTERNAL_MODULE_MULTI=ON -DBLUETOOTH=ON ..
cmake -Wno-dev -DPCB=X10 -DPCBREV=T16 -DINTERNAL_MODULE_MULTI=ON -DBLUETOOTH=ON -DHELI=N ..

[koakumaping]

Hello pfeerick,
May I have a build for xlite pro with ACCST D16 D8(i dont use ACCESS), no heli, EN, ver 2.7.1, thx

[pfeerick]

You should be able to use the standard EN_NOHELI build... just set your internal RF to XJT instead of ISRM.

companion_BBSCewXoZs.mp4

[koakumaping]

ok,i will try it later

[Billy60]

Hello all
The links to the Multilinguals are dead.
Could they be fixed ?
Thanks a lot !

[pfeerick]

Looks like the VPS had an outage yesterday and didn't come back up again properly... should be right now. Sorry about that! :)

[shihuntaotie]

Hello,
May i have a built FR for X9DP with chinese?
Thank you

[pfeerick]

Unfortunately, I don't think so - I don't think CN or TW are working on B&W radios at the moment. I'll double-check, but I'm pretty sure you get a whole lot of nothing where there should be Chinese characters... which isn't very useful! :-O

[Billy60]

My tx16s is indeed colour Too bad Thanks for trying ! Le dim. 11 sept. 2022, 07:22, Peter Feerick ***@***.***> a écrit :

…

Unfortunately, I don't think so - I don't think CN or TW are working on B&W radios at the moment. I'll double-check, but I'm pretty sure you get a whole lot of nothing where there should be Chinese characters... which isn't very useful! :-O — Reply to this email directly, view it on GitHub <#1951 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFOMGZFF3TQHPKUSER2PTHTV5VUAFANCNFSM5VTJ3SGA> . You are receiving this because you commented.Message ID: ***@***.***>

[pfeerick]

Um, you might want to look again - I wasn't replying to you - and I'm not sure how I'd know what radio you have since you never said! 😆 That was a reply to "X9DP with chinese" which is a B&W radio ;) I replied to you 2-3 days ago letting you know the links should be working again ;) "Looks like the VPS had an outage yesterday and didn't come back up again properly... should be right now. Sorry about that! :)"

[pfeerick]

Build for X7 with NOHELI and LUA_MIXER added
cmake -Wno-dev -DHELI=N -DLUA_MIXER=Y -DPCB=X7 ..

[2xWhiskey]

Hello, is there a specific build option to utilize CRSF (Crossfire Shot) internally with the radio's internal RF module? I've selected CRSF and 400k Baud rate under the radio's HARDWARE menu as well as powered the internal module via the model specific menu. I'm using a Taranis X-Lite Pro (EdgeTX 2.7.1) with a DIY ELRS TX module (2.5.1) and have been unable to get the module to communicate via the Lua script. I have verified the module is working by connecting it to the radio's external bay and successfully using the Lua script.

[pfeerick]

This is more a general or Q&A type question than a firmware build request one. Especially since you need to consider aspects such as "how is the RF module connected to the radio" - i.e. does it have a full duplex connection? #2337 Are you using that connection, as defined in the hal.h? From a quick look at that, that transmitter should work as is, but I've not heard of it actually done before, just talked about, so you could be entering uncharted waters, and settings may still need to be tweaked ;)

[2xWhiskey]

Thank you, I am using a copycat of the TX_SX1280_Minimal design. It utilizes one pin connection for communications, Pin 10 (SPORT), of the main 15 pin connector that goes from the main board to the internal RF board. Does that SPORT line count as full duplex? Or are you referring to something like a UART that has both an RX and TX line? I tried looking at the hal.h you linked, but honestly I don't understand how to interpret it. I did reconnect the module to the external bay connect and verified that it was communicating with the ELRS lua script.

[2xWhiskey]

I was just thinking, I don't know the official pinout orders, just what I wrote down from taking notes with a multimeter. The SPORT line could also be Pin 5.

[pfeerick]

Hm, that could be a problem... full duplex means two-way communication at the same time, which for digital basically necessitates separate TX and RX. Half-duplex means only one side can talk at a time, so one line can be used for both. I have to admit I don't fully know how these are configured, but I believe the S.PORT line has the UART TX and RX both connected in some fashion. Another thing you may need to play with is the UART_INVERTED setting - that may have some bearing now that you are not going though the external sport connection. @raphaelcoeffic will be able to give a more informed overview of what's needed. Maybe also ask over on the ELRS discord, the #handset channel is probably a good place to start.

[2xWhiskey]

Thank you for your advice and time. I do appreciate it!

[federikk]

Hello @pfeerick ,
may i ask a 2.7.1 for RM tx16s with:
crossfire, ghost, flexr9m, afhds3, internalmulti, multimodule, lua, luac, externalaccessmod

multilingual (IT)
thanks a lot
F

[pfeerick]

Sorry for the delay... flexr9m is no longer needed as an option as flex is enabled by default now, so the only extra options needed are for the external access mod and language. Check the "By Request" link at the top of the page for the firmware.

cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DTRANSLATIONS=IT -DHARDWARE_EXTERNAL_ACCESS_MOD=Y ..

[azaz44]

Update: I was able to compile it on my own. Although I'm not sure if I got the flags right. Would it be true to say, that such setup:

cmake -Wno-dev -DPCB=sth -DPCBREV=sth

done on 2.7, would give output equal to official release Black Pearl?
I had troubles to find out how is actually official release compiled.

---

Hi. Could I request x10 (non-access) with:

• noheli
• LUA_MIXER=Y
• others like in official release of Black Pearl

BTW, is there any reason mixing scripts are not included in official builds? Is it not stable?

[Helipro]

I am looking to get 2 compiled version of 2.9 for my Bluetooth build T16s and Jumper Tx16. I was not able to compile my own as I was with previous versions.
cmake -Wno-dev -DPCB=X10 -DPCBREV=T16 -DDEFAULT_MODE=2 -DPPM_UNIT=US -DBLUETOOTH=YES -DLUA=ON -DOVERRIDE_CHANNEL_FUNCTION=OFF -DCMAKE_BUILD_TYPE=Release ../

cmake -Wno-dev -DPCB=X10 -DPCBREV=TX16S -DDEFAULT_MODE=2 -DPPM_UNIT=US -DBLUETOOTH=YES -DLUA=ON -DOVERRIDE_CHANNEL_FUNCTION=OFF -DCMAKE_BUILD_TYPE=Release ../

Thanks,
Craig

[pfeerick]

As in you don't have the facility to do so, or encountered issues in building them? Both those build options built fine for me.

firmwares.zip

[Helipro]

Thank you I really appreciate it. I encountered issues: I tried the same way with past versions. Error that I receive now:
CMake Error: The source directory "/workspace" does not appear to contain CMakeLists.txt.
Config error: make: *** No rule to make target 'configure'. Stop.

[pfeerick]

Ok, you're hitting a problem we've noticed with the v2.9.0 version tag and gitpod... it's not executing the initialisation task whereby it would run mkdir build && cd build, so since you're not in the build directory since cmake has been told to look in the next directory up (the .. at the end) it can't find it. It seems even it you do create that build directory that gitpod doesn't seem to be initialising properly as it doesn't seem to be able to find the compiler. However, if you instead checkout the 2.9 branch as it is it seems to be working properly... i..e. https://gitpod.io/#https://github.com/edgetx/edgetx/tree/2.9

[Helipro]

The 2 files you sent me for the T16 and Tx16s bricked both transmitters in the middle of the update.
I am also still not able to access the web link you sent me to build my own firmware. Could you try sending me the firmware again, Thanks Craig

[pfeerick]

By "bricked" do you mean the UI pdate via bootloader froze when it was nearly at the end? If so, that happens occasionally, and after a hard power cycle it usually updates successfully. We're not sure why that happens yet.

…

On Fri, 8 Sept 2023, 1:07 pm Helipro, ***@***.***> wrote: The 2 files you sent me for the T16 and Tx16s bricked both transmitters in the middle of the update. I am also still not able to access the web link you sent me to build my own firmware. Could you try sending me the firmware again, Thanks Craig [image: 2] <https://user-images.githubusercontent.com/119552818/266491423-f0c09b75-81aa-4a75-be83-51bed59e319a.jpg> — Reply to this email directly, view it on GitHub <#1951 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABJ66KPU76RWRAF343F5JIDXZKDWNANCNFSM5VTJ3SGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Helipro]

Yes that is what happened. after it bricked I programed the Tx with the stmcube programmer and with the files you sent me but it was 2.9-rc1. I just used stm32cube programmer and went back to 2.9-rc2 on both tx's.