dvogonen / cyclop_plus_plus Goto Github PK

A number of transmitters have added support for eight new channels that are in a frequency range just below the normal 5.8 GHz band. This adds the possibility to use twice as many channels at the same time without interference, so it is is a good thing. The not so good aspect is that transmission on this new "Low Band" is illegal in most countries. Reception is however never illegal, so it would be a good idea to implement support for low band channels in the Cyclops googles.

The "Low Band" frequencies are outside of the stated specifications for the receiver chip in the Cyclops (a RichWave RTC6715). There is however no mechanism in place that blocks selection of the somewhat lower channels. I will make a practical test of the viability of tuning the receiver chip to the "Low Band" frequencies. If success full, I will add support for all 48 channels as a standard feature.

When flying on a locked in channel and range becomes extended and rssi becomes low (note 344 in top right) the picture and the OSB begin to jump around and the signal drops and everting goes for a moment before returning....

I am unsure as to the Voltage setting on the RX end as i have no Multi meter at the moment could this effect the matter...

When powering on the cyclops it does not always come on the last chanel used meaning I have to retune. This doesn't happen every time.

I have favourite channels set and everything except race band is turned off. It has always come on a channel that I have disabled I have never noticed it turning on on a raceband channel that I didnt use last time.

Would it be possible to add displaying the voltage instead of the percentage. Since voltage is available on the calibration page I suspect this would be a simple addition as an extra option in the menu.

A pull request has been posted to add the possibility to display a textual representation of the battery level next to the battery.

Being able to limit which bands are used will make it easier to step between channels. If someone uses the A-band for his transmitter, he/she will not be interested in stepping through all other channels on band b, c etc.

Hey, thank you so much for your work on this Project! I did install the the mod without problems and it is working. One problem still remains:
Stability of the video feed has decreased significantly. I get flickering and grey screen/blank screen as soon as RSSI falls a little (i.e. below 400 in the OSD). Before the mod picture would just get a little grainy, now it shuts off completely.

Have you made similar observations? Is it because the minimOSD looses video signal quicker that the installed display driver board?

Hope you have any suggestions on how to improve this, if it can be improved.

Thanks again for your great work!

Очень нужна ваша помощь с похожим проектом. В идеале просто ускорить ю упростить ваш.

Если вас не затруднит мне помочь, напишите, пожалуйста, в телеграмм @LOSTLY3D

There is a bug in the channel table.
Please see error description in the bug report (#19) for cyclops_plus: Dvogonen/cyclop_plus#19

Will this ever be ported to the new version of the goggles that have diversity?

Currently its possible to display the channel, RSSI and volts at top left or top right. Could additional options be added to put it in the following places: Top centre, bottom left, right and centre

Is the only reason for the MinimOSD (instead of MicroMinimOSD) is because the guide taps vBat for power instead of the regulated rail that seems to be able to run all the way down to 5v from the Cyclops+ documentation? I ask because I've got a couple of micros littering my workbench, but my only regular one is tied up.

The battery alarm of CYCLOP+ sets in to early according to this post by awap at RCGroups:
"Hi, I'm very happy with version 1.4 and the Eachine DVR installed. One whish however: I'm on a 3S battery and the beeper starts at 11.4V (3.8V per cel) and the second level beep starts at 11,2V (3,73V per cel). This is too soon. Is there a way to start the beeper at 3x3.65= 10.95 -11.0 V?"

The behavior is not really a bug, the level in CYCLOP+ was set unnecessarily low.
The levels in CYCLOPS++ are probably the same, or at least similar, so the change has to be made in this project to.

When using the graphical scanner after power up you have to first tune into an image from a camera before it scales the graphical scanner correctly and shows the x axis text.

If you have nothing tuned in the text stating the frequencies falls off the bottom of the screen. After the first camera image is displayed on the screen from a transmitter this issue stops even if the transmitter is turned off or the channel changed.

Setting the level to values between 1 and 7 produces ever higher sound levels but setting it to 8 produces a sound level lower than 1!
Clearly a bug.

The battery alarm sets in to early according to this post by awap at RCGroups:
"Hi, I'm very happy with version 1.4 and the Eachine DVR installed. One whish however: I'm on a 3S battery and the beeper starts at 11.4V (3.8V per cel) and the second level beep starts at 11,2V (3,73V per cel). This is too soon. Is there a way to start the beeper at 3x3.65= 10.95 -11.0 V?"

The behavior is not really a bug, the level was set unnecessarily low.