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

FRM301 support #1811

Closed
wants to merge 15 commits into from
Closed

FRM301 support #1811

wants to merge 15 commits into from

Conversation

gagarinlg
Copy link

@gagarinlg gagarinlg commented Sep 3, 2022

This PR is based the work being done for PR #1064.

  • module communication with EdgeTX on PL18
  • LUA script connection
  • binding receivers
  • telemetry
  • enabling the bootloader
  • flashing form the radio
  • make FRM301 available in ExpressLRS configurator
  • apply remaining review remarks from the last PR

If possible, I would like to get some help on the configurator integration.

@rotorman
Copy link
Contributor

rotorman commented Sep 3, 2022

I tested this PR with Paladin EV (with FRM301 RF-module) running EdgeTX v2.8.0-dev (see https://github.com/EdgeTX/edgetx/wiki/Flashing-EdgeTX-to-Flysky-PL18-or-Paladin-EV ) and DIY-PWM ELRS Rx flashed with ELRS v3.0.0-rc2. Built the fw with Visual Studio Code + PlatformIO and flashed FRM301 via SWD.
I could use ELRS v3 LUA and TBS Agent Lite v0.96 for configuration, had a successful link and could actuate the servos attached to the RX.

@porfiheli
Copy link

I have just tested the FRM301 firmware with the flysky FTr10 receiver and it is working as transmitter.

  • Sport pin of JR Bay connected to the receiver SENS Pin (UART1 of the STM32F030)
  • SWD connector of FTr10 receiver has the same order as the FRM301 tx module

Issues found: sometimes the lua script takes a long time to load all the data. Also changes with the lua script are sometimes not saved. Bind function from the lua script worked.
Tested with Radiomaster TX16S with Edge-TX
image

@gagarinlg
Copy link
Author

It is probably not to hard to create a receiver firmware based on that PR.

@gagarinlg
Copy link
Author

@porfiheli did you ever continue working on the boot loader?

@porfiheli
Copy link

@porfiheli did you ever continue working on the boot loader?

@gagarinlg i didnt work on the bootloader, i focused first on getting the firmware working.

@gagarinlg
Copy link
Author

OK thx.
I think I will try to get a bootloader working next.

@porfiheli
Copy link

@gagarinlg here is the pin mapping of the FTr10 receiver.

2022-09-09 FTr10 Pin Mapping

@gagarinlg
Copy link
Author

I am still on this, it just got pushed back by some other stuff.

@JyeSmith
Copy link
Member

JyeSmith commented Feb 9, 2023

@gagarinlg would you like me to leave this open for now? Doesnt look like there has been much action recently.

@gagarinlg
Copy link
Author

Please leave it open for now, I plan to continue the work on it soon.

@richardclli
Copy link

@gagarinlg So is this branch still works or not?

@gagarinlg
Copy link
Author

Currently not, I need to put some work I to it, it stopped working after the last rebase.

@BlueskyFR
Copy link

@gagarinlg is there any hope for development to continue on this PR? I am sooo interested by compatibility with the EL18! 😍

@richardclli
Copy link

@gagarinlg is there any hope for development to continue on this PR? I am sooo interested by compatibility with the EL18! 😍

I have worked out 2 branches for v3.0.1 and v3.2.0 and make it compilable. However, it is not working properly during testing. Need some time to figure out what the problem is.

https://github.com/richardclli/ExpressLRS/commits/frm301-v3.0.1
https://github.com/richardclli/ExpressLRS/commits/frm301-v3.2.0

However, the RAM resources is already quite critical for FRM301 to runt he ELRS, so......... may need to change the MCU to support future versions.

@BlueskyFR
Copy link

@gagarinlg is there any hope for development to continue on this PR? I am sooo interested by compatibility with the EL18! heart_eyes

I have worked out 2 branches for v3.0.1 and v3.2.0 and make it compilable. However, it is not working properly during testing. Need some time to figure out what the problem is.

richardclli/ExpressLRS@frm301-v3.0.1 (commits) richardclli/ExpressLRS@frm301-v3.2.0 (commits)

However, the RAM resources is already quite critical for FRM301 to runt he ELRS, so......... may need to change the MCU to support future versions.

Thanks for the answer! I'll try this when I can. Is work going to continue then?

Also, does something need to be done to make it compatible with an actual receiver?

@gagarinlg
Copy link
Author

due to the flash am RAM constrains on the FRM301 it is not feasible to do this. It would be better to just make an ELRS module that fits the PL18 module bay.

@gagarinlg gagarinlg closed this Feb 29, 2024
@BlueskyFR
Copy link

due to the flash am RAM constrains on the FRM301 it is not feasible to do this. It would be better to just make an ELRS module that fits the PL18 module bay.

What would you recommend to make the controller work with elrs then?

@gagarinlg
Copy link
Author

Either via the AUX uart or by making a module that fits into the slot of the PL18.
@richardclli would you share your stl files?

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 this pull request may close these issues.

6 participants