Is the any plans to support the OMP 65A ESC (as used in the M4) telemetry.
I have a Brain 2 in my M4 but as I understand it I can’t get telemetry via PIN 5 on the Brain like I can for Hobbywing ESCs.
Before we invest in all the man-hours needed to develop and for the purchase of the ESC in order to do the testing and possible debugging, we would need to know at least if this ESC provides for sending telemetry parameters and to know the name of the manufacturer (even in case it is a rebranded ESC for OMP).
We would like to avoid buying this ESC (or even the whole model) only to find out that it is impossible to do what you are asking because the ESC does not send any telemetry data.
OMP ESC has telemetry. They support OMP Telemetry that they are working with manufacturers of flybarless systems to get implemented. I believe they are sending ESCs for development work to a few flybarless companies for that purpose based on their thread in another forum. They also support sending Futaba telemetry for the Futaba flybarless system. I am surprised they haven't reached out to MSH yet. Brain2 is pretty popular. They announced on another forum that they were wanting to work with MSH on it anyway.
We are 3 friends and we have each bought an OMPHOBBY M4 including Brain2. Unfortunately, we have only now discovered that the telemetry from the OMP 65A ESC from MSH is not yet supported. Since the models of OMPHOBBY in the model helicopter scene experience more and more widespread, it would be welcome if MSH would support the OMP telemetry protocol with the Brain2.
Many thanks.
OMP ESC has telemetry. They support OMP Telemetry that they are working with manufacturers of flybarless systems to get implemented. I believe they are sending ESCs for development work to a few flybarless companies for that purpose based on their thread in another forum. They also support sending Futaba telemetry for the Futaba flybarless system. I am surprised they haven't reached out to MSH yet. Brain2 is pretty popular. They announced on another forum that they were wanting to work with MSH on it anyway.Which Forum? Can you give a direct link? Thanks.
Yea. Some links below...
https://www.rcgroups.com/forums/showpost.php?p=50694707&postcount=387
"The ESC will output an unencrypted telemetry protocol that can be implemented by any FBL/RF Link manufacturer interested in it. We can provide documentation of the protocol for this purpose. I plan to contact the developers of Brain and Spirit myself once the ESC is completed, as these two systems are currently among the most widely used. If an implementation with other FBL vendors is desired, please have them contact me/us for this purpose."
And more recently about 9 days ago posted by one of the designers of the M4...
https://www.rcgroups.com/forums/showpost.php?p=51259085&postcount=1108
"Yeah, as I said, I don't have time for this right now, so I'm letting Roger (OriginHobbies) handle it. He's also looking to provide my Spirit setup on his website and possibly also looking to carry Spirit, so very convenient that he's talking to them directly. He's been talking to Rik Menta about it as well, so BRAIN2 will hopefully also be getting telemetry shortly."
Hi BRAINDEV,
are there any news about the telemetry support for the OMP M4 65A ESC ? Have you been eventually contacted by OMP guys?
I ask since I'm probably getting an M4 soon and will use BRAIN2 as FBL unit (as for all my helis). Having direct support telemetry would be really a great plus, and probably a smart move for MSH since I think this RC model will be a success in terms of sales...
For your info, the designer of the M4, a Jonas Wackershauser, has recently release some YouTube videos of the M4 with BRAIN installed (for exemple: removed link ).
Thanks in advance for your support, and also for all the improvements you make free of charge for us !
Luca
PS: I have some direct contacts at OMP, please let me know if I can help. Grazie e a presto...
I confirm that we are already working in the implementation of telemetry for OMP ESCs.
In addition to the firmware that will allow the parameters of OMP ESCs to be displayed in the DIAGNOSTIC sections of our apps in the Real Time and Recorded Logs sub-sections, we will of course also enable telemetry data transmission of OPM ESCs via the telemetry protocols of Spektrum, Jeti, Futaba, Graupner, Ethos, OpenTX, EdgeTX, Crossfire (FrSky and RadioMaster), FlySky, Multiplex, with old Spektrum SMP4649 SRXL telemetry receivers, etc. etc.).
We are also implementing the ability to select telemetry of OMP ESCs via the Windows, Android, iOS apps and also via the Spektrum, Jeti, Ethos, OpenTX, EdgeTX, Crossfire (FrSky and RadioMaster), Graupner Integrations which will all be modified and updated.
In addition, we will also update the necessary documentations (instructions and PDF manuals).
After the Alpha versions are completed, we will be able to start distributing Beta versions to Beta testers.
However, we do not know when we will be able to release the official versions of firmware, apps, integrations and documentation, so we are not able to give an official date (as always, unforeseen events and delays are always around the corner).
We ask the courtesy not to start asking us for release updates every day, because for every answer we have to give, time will be taken away from development, debugging and testing work.
Thanks.
Hello. Sorry to disturb, I know you are working on OMP M4 esc telemetry. Since I'm doing the wiring on my new M4, could you please just tell me which cable shall be connected with the Brain? On the ESC there is a 4 pin connection (+, -, Rx,Tx).
In this way I can already install the necessary wires and fix them to the frames.
Grazie molte,
Luca
Manual says:
1. Throttle signal/BEC output wire (Black, Red, White): Plugs into the receiver throttle channel. The white wire carries the throttle signal, the red wire and black wire carry the BEC voltage and ground.
2. RPM signal wire (Yellow): Plug into the RPM input port. (If applicable)
So the 1st will be plugged to the Brain2 throttle output, the 2nd to the Brain2 RPM input.
Best Regards,
Joggt
Thanks but telemetry data are probably carried by a separate wire, as for instance on hobbywing esc...
That's why I asked the question...
Regards
The yellow wire is the telemetry wire. Factory default is RPM. With a separate Bluetooth module you can activate telemetry. But this is at the moment not supported by Brain2. But RPM works fine.
Since I'm doing the wiring on my new M4, could you please just tell me which cable shall be connected with the Brain? On the ESC there is a 4 pin connection (+, -, Rx,Tx).Yes, the serial signal that carries the telemetry data from the ESC to the flight controller is as with all other ESCs a separate and independent connector normally used for configuration, programming and updating the Firmware which however for OMP ESCs unlike other ESCs is not a three-pin connector with a single Half Duplex connection but in addition to the positive and negative has two separate serial ports one for transmission and one for reception for full Duplex communication.
To transfer the serial data that contains the telemetry information to the flight controller (which will then eventually take care of recording the values in the Recorded Logs and reconverting the values to the various telemetry formats of the serial protocols used by the various types of receivers connected to the flight controller) simply connect a singlevire to the ESC's output signal (marked "TX") to the center CH5 pin of the CH4-5-6 connector on the flight controller.
Then as with other ESCs you need to let the flight controller know what protocol format to decode by selecting "Also OMP ESC Telemetry" in the "Telemetry Input" panel dropdown.
PS: The yellow wire (connected to the signal pin of GOV connector) as with other ESC models does not carry any serial data stream containing telemetry values, instead it carries only very simple pulses (squared and transformed into square waves) that correspond to the passage of the motor windings in front of a pair of magnets. By measuring the time elapsing between one pulse and the next, the rotational speed of the motor is obtained. Dividing this value by "Main Gear gratio" the main rotor RPM is obtained.
