Advanced Search

hexfet wrote: That's good news! Do you have a link to the new version. The file here hasn't been updated.

Here is the link. I do not have a module, so I can not check. I follow this because I want to buy a micro TX module for my t8sg v2 plus radio.

https://www.team-blacksheep.com/products/prod:agentxhttps://www.team-blacksheep.com/products/prod:agentx

That's good news! Do you have a link to the new version. The file here hasn't been updated.

Hi team,

Final feedback with my HITEC RED Transmitter, It works fine with the original Hitec RED transmitter, it means the receiver is ok.

I did another try to bind but without any success for this Ares-RC.

Claude

Hi team,

Thank you very much for all your suggestions, really appreciated.

I'll purchase a Hitec transmitter and update this post with the results.

Claude

Hi Wil and team

Thanks Wil this is great, really appreciated that you did this test for me.

I'm using a IR8M and Minima is correctly saved, however I did the procedure exactly like you described again without any success.
There is no Bind on the HITEC receiver and the procedure described in the plane user manual just says that the binding is automatic ..

My receiver LED always rapidly blinks red even if my transceiver is off.

I see multiple possible problem:

-My plane is new but does not bind with a transmitter
-Code is not working with IR8M


Claude

Hi team,

This is the status of my tests.

I tried once more with protocol=Hitec, Format=MINIMA because by now I found in the plane manual that HITEC minima is the protocol to select.

However it does not work !

I do not have any clue of how to debug my problem, I just did try and error test with different values.

I guess the following
Fixed_id should not be a problem
num_channels may create a problem so I tested with 3,4,5
Freq-Fine I tested with multiple as well, however I'm not sure if this parameter plays a role for the bind or only during servo movements.
tx_power should not be a problem for binding a model 30 cm far from the transmitter
Channel assignment, I'm not sure if this may cause a problem, I did several tests with on of the 4 channels either on 0 or 100, because I guess THR should be zero to sync.

Any suggestions are welcome.

Here is a copy of my last model.ini file

name=FOKKER
mixermode=Advanced
icon=PLANE.BMP
type=plane
[radio]
protocol=Hitec
num_channels=5
fixed_id=123456
tx_power=30mW

[protocol_opts]
Format=MINIMA
Freq-Fine=64

[channel1]
template=simple
[mixer]
src=AIL
dest=Ch1
curvetype=expo
points=0,0

[channel2]
template=simple
[mixer]
src=ELE
dest=Ch2
curvetype=expo
points=0,0

[channel3]
template=simple
[mixer]
src=THR
dest=Ch3

[channel4]
template=simple
[mixer]
src=RUD
dest=Ch4
curvetype=expo
points=0,0

Hi team

When I ordered this plane I did not realize that Deviation may not be compatible with it.
www.ares-rc.com/fokkerDVII/

I'm using a IR8M transmitter and I want to use it with a HITEC RED BNF micro airplane.
For so far as I can see with my IR8M module "4 IN 1" CYRF6936, CC2500, NRF2401, A7105, including CC2500. www.rcgroups.com/forums/showthread.php?2...Receiver-Free-Review

In the manuals, I see the protocol Hitec.
www.deviationtx.com/manuals/html-devo10-....html#protocol-hitec

I have seen that some people have have done some successful tests.


-Do I need to install additional HW (cc2500) in my IR8M in order to support AFHSS HITEC protocol, so far as I can see in my IR8M the CC2500 is already included ?
-So I have to use a Night Build, can I use the latest one ?
-Any specific recommendations or advise ?

Thanks

Claude

For the yaw issue, it could be that your original TX as an offset on the yaw and since it is learnt during calibration, the quad will compensate but since the Devo has no yaw offset it drifts.
Calibration is implemented in my latest code but we need to wait that someone from the deviation team includes it. It's really a few lines of code...

There are some pricewars ongoing in RC radio land......
In the end more choice and cheaper open hardware will be availble.

in terms of evolution and developmemts I think all credits are for OpenTX and Deviation teams. JUMPER does not revolutionize any radio......

Just buy radio of choice and run deviation or open Tx.

I hope there will be a good radio on the market for deviation, as Frsky radio’s are a class above Jumper.

Maybe the crossfire module doesn´t support CRSF on the PPM pin. I found an article for futaba. There is an instruction for a custom cable. They use a pin of the "extension port" for CRSF input. So probably the signal is already correct. I will try to stick this together tonight.

team-blacksheep.freshdesk.com/support/so...-futaba-crsf-support

I'll leave it up to your choice, as you do the work (which I'm already thankful for, as I know from my German work it takes quite some time), but personally prefer pt. I just think that if someone finds a ptBR translation, he won't see a necessity to make an additional ptPT translation, so we might as well put your work in pt right away, and if someone feels like there is to many English terms in it he's always free to make a pt PT or update your translation and decide specific terms or translations in the language team on transifex. But from experience in ANY other of the current translations this won't happen soon, as pretty much all are single persons work. Anyways, I'll open up pt for you as well and will close the one you are not working on in the next couple of days.

If any of the BG folks are monitoring the forum at all, could you please post the .ini files you are using for various models?

I've noticed in a lot of your promo and test flight videos for different models, you are using the Jumper radio (makes sense!)

Can you post those up?

(Or, any of the Dev's that worked with the Jumper team during prototypes, can any of you guys reach out and see if they will upload their model files?)

I'm particularly interested in the one for the EACHINE E500 VTOL.

vlad_vy wrote:

vlad_vy wrote: I have a problem with transifex. I can't scroll down "ch_model", it become frozen at half way down, nearby "Available curves".

The problem confirmed and routed to transifex development team.

Now the problem fixed by transifex development team.

vlad_vy wrote: I have a problem with transifex. I can't scroll down "ch_model", it become frozen at half way down, nearby "Available curves".

The problem confirmed and routed to transifex development team.

TherealjonnyD wrote:

fneuf wrote: Has anyone tried the T8SG with SmartPropoPlus ?

I haven't bothered, because it has USBhid mode that shows up as a joystick with no modifications. Far more reliable than the microphone input PPM signal.

Totally true, but it is still fun to try things and learn. And well, there is an available function on a product I purchased... so by nature I'm willing to test it

mwm wrote:

Iroquois wrote: I have a vision of the creaters of the T8SG laughing all the way to the bank while you gentlemen do their development work for them.

That's generally how open source works: people do development on it to improve the software they are running. Jumper gave the developers transmitters to make sure "software they were running" included the T8SG version. You see the same thing happening with the FrSky Taranis. The Hobbyking th9x open source versions on the other hand took the firmware but didn't involve the developers, so it stagnated or at best got upgrades from development for other hardware.

With proprietary systems, you can't improve the software so your unpaid work is limited to testing.

I tend to share the opinion of mwm. As far as I know (and please correct me if I'm wrong) hardware on the T8SG is not open source. BUT, designers & developers from Jumper are opened to suggestions and discussions.

And that's very important and welcome from a company. The will to seek, gather and learn from community/users comments is cool. Feedback driven design, made with discernment, brings focus to product dev team and clear value to customers.

Were it could be seen as becoming tricky here, and I think that's what Iroquois is implying, is that Jumper is the only one to make money out of this product (again if I'm initial statement is not proven wrong), whatever the hard work of their benevolent contributors. On one side, it's an uber great acknowledgement for all the participants to Deviation coding & testing to see such a recognition from a manufacturer. On the other side the company did get a quality firmware, clearly the killer feature, without too much efforts, I guess you could also see it as a company taking profit of a community. In a pure factual way, both statement could be defended as true. So I guess how you see it mainly depends from the mood on which you rise this morning

Personally I prefer the "great acknowledgment" POV of the story. And I really hope Jumper will find great ways to support back the community and show some love to the skilfull and helpfull talents here. The possibilities offered by a company choosing to build on top of open source firmware, in coherency and respect of the software development team is really motivating.

Hello there,

After lurking this thread for some weeks, I jumped in and bought the jumper (pun intended). Finally I did received mine today and so far I have noticed:

• the battery rack is installed (and I can confirm the Turnigy 1600 to be a nice fit)
  
• the USB port is the accessible one
  
• it beeps in addition to vibration,
  
• the installed firmware is the specific T8SG build dated from the 05/10 (special thanks to vlad_vy on that)

Should I update it first thing?

ltwvince wrote:

dc59 wrote: Jumper replied, both T8SG & DEVO hall gimbals are at molding stage now, beta version will be released soon.

If they can give good price for beta testing, please let us know. I have this T8SG, Devo 7E and Devo 12E. Thanks.

IMHO :

• Beta testing should not imply payment from the tester, but should be seen as a gracious opportunity for the brand to have dedicated and motivated ressources in their team.
• And should a payment be done to guarantee the "motivation" from the maker POV, it should be clear that the testers will be upgraded and receive the final product in the end as an acknowledgement of their efforts.

Those are the only win-win scenario I could think of and see as acceptable.

Anyone have a model.ini laying around for a Japalura 130mm frame with a Betaflight fc (FC3)?

Here are the specs:

Spektrum DSMX Quad Race RTX
Betaflight F3 Flight controller
DYS SX20A ESCs
Brother Hobby Tornado 1407-3600KV

The FPV Rig:
Team Black Sheep Unify Pro HV Race VTX
Runcam Owl+
TBS Whip Antenna

After posting this problem I did more searching and found that the problem is a documentation issue. I found the following explanation which then made the process clear:

Category: Feedback & Questions


The Deviation manuals suggest 2 methods for installing Deviation:
1. Use the Deviation Java Uploader.
2. Use the Walkera Dfuse installation software.

Method number 2 is for use with computers running the Windows operating system.
Method number 1, the Java Uploader, is cross-platform (Windows, MacOS, Unix, whatever can use Java), and is the simpler, more trouble-free method. The Updater was designed and built by the Deviation development team to ease installation of Deviation on a variety of Devo tramitters.. Using the Java Uploader, you can easily install any version of Deviation from version 4.01 or later, or return to the original Walkera firmware and file system if you wish. Installation uses the Firmware Zip file that you download without needing to unpack it. The Java Uploader takes care of unpacking and putting everything it the appropriate location on the radio. The application also includes other useful features you can explore.

goebish wrote: That sucks I suppose I'd need an H501S + an actual Hubsan Tx to actually understand what's happening ...

How can I help? I currently live in Zürich, so I'm not sure if I could somehow ship the quad + TX to you and back. Could I perhaps do some analysis on my own? What equipment do I need? I'm an informatician / computer scientist / hacker by education + occupation, but I have no experience with microcontrollers, wireless protocol analysis or low-level hardware stuff in general.

Sadly, Hubsan doesn't seem to be helpful. When asked about protocol changes, they emphasize how much safer their changes make the drone. But it's definitely not safer for a Devo 10 user (unexpected disarming, inability to fly indoors etc.). I carefully explained why I wanted to use the Devo 10 -- it talks to 20+ of my other drones, I'm used to it etc. But thus far I haven't even got the chance to talk to someone from their software team directly.

If I can help, I'd be more than happy to give it a try. Otherwise I'll have to downgrade to 1.1.21, which is nowhere to be found (officially) at the moment. This is an awesome drone with a really nice airframe, but the proprietary software is just killing it. I always have an annoying experience when I update it, because I don't run Windows or other spyware at home. So I have to download a VirtualBox Windows VM, set up USB device passthrough and flash everything from the VM. :-/ Oh, what a joy.

H501S would be much easier to maintain with LibrePilot or {Clean,Beta}Flight. Plus I'd get acro mode. But I have absolutely no idea what controller it is and whether it would be compatible.

The original software only works with to the Devo protocol. It won't even work with the older walkera protocols that deviation supports.

I would be surprised if it's impossible to program wings, flaps and V tail with deviationTx. It won't be as easy as using proprietary software that's tailored for that. Try searching the forums for what you need, I know a number of unusual fixed wing model teammates have been posted. If nothing else, try asking for help. Some of us enjoy the challenge of programming obscure model types.