Pirx Firmware

[Pinkie Mclucas]

Inthis article we will take a look at the Eachine Pro58 Diversity Receiver and we will see how to install a custom firmware on it, specifically Pirx The Pilot. To do so, we need ST-LINK V2 STM8 / STM32 Programmer which is a USB module used to program/upload the firmware on the receiver.

We have to use a total of four pins in order to power and upload the new firmware on the Eachine Pro58: 5.0V, 3.3V, SWCLK, SWDIO. First two are for power the module up and the other two are used to upload the firmware.

Of course, we need to connect these two wires to the corresponding ST-LINK V2 pins shown before. Looking the Eachine Pro58 from the back, the 5.0V and 3.3V from the ST-LINK V2 have to be connected as shown here (you can choose whatever pins couple that you prefer since they are identical, upper 3.3V/5.0V or lower 5.0V/3.3V):

Different view (I used only two of the four wires supplied because I already had similar wires with a free end, but of course you can use the other two and cut off one end in order to solder them on the receiver SWCLK/SWDIO pads):

If power wires are connected properly (double check before proceed), we should see the Eachine logo on the Eachine Pro58 display when connecting the ST-LINK V2 USB to the PC, meaning that it is booting up. After that we should be prompted with the following screen:

Next we have to click on the second icon from the top left (the one with the downloading arrow) and browsing for the firmware we want to load.Pirx The Pilot Firmware .bin file is available here for free (you just have to register to get the download link).

In this article we have seen how to load a custom firmware, specifically Pirx The Pilot, on the Eachine Pro58 Diversity Receiver using the ST-LINK V2 STM8 / STM32 Programmer. This is a really good diversity receiver with very nice performance and this firmware just make it a must have product especially if you want to upgrade a pair of goggles not having diversity like the Eachine VR006 Mini FPV Goggles.

Achilles is the firmware that people generally buy the Pro58 for. Originally, it was the other way round, but the feedback and reviews of the Achilles firmware were just that good that people now buy the Pro58 en mass just so that they can run it.

Newton updated tnfs server and firmware code to support TCP/IP protocol and finally, fujinet is usable in places where the network is not stable enough for UDF transmission. The default tnfs servers have already been updated and usability reports are very encouraging, with several users mentioning the transition of fujinet from a drawer-dwelling gadget to a useful device.

Test method was to boot the 600XL with the FujiNet enabled and navigate to tnfs.online in the hosts list. This is why only 5 packets are captured in the TCP/IP test - nothing happened beyond a successful connection, which was enough to verify that the protocol was working as expected.

At some point in the future I may set the server to only accept TCP/IP connections, but as it's a) early days for TCP/IP adoption and b) leaving UDP enabled doesn't have any detrimental effects, there's no real reason to at this time.

As the firmware have been updated as shown from the iLO's screenshot and the error indicates that HPE OneView experienced communication issue, if there are , no other tasks to be performed, then, could the firmware updates be stopped and then the appliances manually refreshed?

I have the problem that the Smart Array firmware for E208i is not updating at all, while OV shows it needs to be updates in the FW compliance section.

Current FW is 5.32 and needs to go to 6.52.

When trying to run remediate AGAIN after the same error @pirx expirienced, the staging proces in vLCM just hangs.

I waited 20 minutes and canceled the task ... which eventually (15 minutes later) did.

I tried updating with SPP2023.09.03 which contains 6.22 but it does not contain 5.61 nor 5.32 which are prerequisites when you're updating from lower versions ... why are these bundle's removed from the SPP !?!

So I was forced to use SPP202309.04 which contains 6.52, which can update in one step from 5.32, but it also implied that I needed to manually add the latest SmartPQI driver to the vLCM Image otherwise ... vSAN not compliant !

My favorite FPV Goggles receiver firmware, Achilles, is finally making their own diversity RX module! I really like the performance of the firmware, and now there are some really exciting new features in this module so I am really looking forward to testing it.

There is a speaker on-board which is not difficult to understand, it plays warnings. But there is also a mic, and I am not 100% sure what it does. Maybe you can record your own voice with it in the DVR, like a commentary perhaps? :D

I finally bought mine from a local retailer. Unfortunatelly, the module arrived with an OSD issue and the image inside mi fatshark T2 was not clear enougth for been usable.

I already have the replacement on the way.

10/10 For the FuriousFPV support, they took care of the situation inmediatelly even if the module was bought through local retailer :D

I had/have the same issue and like you I agree their costumer service is 10/10 but I did get my replacement unit and still having the same issue so please keep us updated and see if your issue is resolved

Agree! Tested wpro58 and PirxThePilot so far. What I found out in terms of performance, I like the Pirx firmware most. It has the ability to fine tune manually in one Mhz steps. That can result in a better image quality and additional range. IOn comparison Achilles does have multiple options for this kind of fine tuning, manual tuning, automatic tuning (during ultra search) and Kerveros mode (on the fly tuning). So in terms of picture quality and range, i guess Achilles is in the pole position, followed by Pirx and then wpro58 (no tuning).

hi All those features that Pirx and Wpro58 have , are all legasy of achilles , everything was from achilles , for example

the fine tuning tecknique achilles have it 2 full years , back in the realacc module !

Few days ago I have successfully installed an ESS system based on MultiPlus II 48/5000/70, CCGX and BYD B-Box Pro 7.5. It worked fine until yesterday. The batterie went off and cannot be turned on again. The error message when trying to turn it on is: "yellow error LED plus 4x buzzer" indicating a safety mode. The last information in the logger stored before the outage is showing the battery at 100% and 65,18V which is way too high. It should be below 58V.....

I already contacted the BYD support, but wanted to know whether anybody out there has experienced such an issue or has an idea what the root cause is?

If you don't upgrade to the latest firmware, you won't get support from Victron. You can search for a change-log if you want.

If there are problems, first update and see if there are still problems, if problems persist, then you can get support.

Hi @Pirx

Ok sorry to hear that, best to go to your installer / distributor for support.

I've asked if there are known issues with this combination, my first guess would be the battery as it is disconnecting without warning.

Now I'm one step farther with the problem analysis. If I disconnect the DC wires the BYD battery is starting without any problems. The CAN communication to CCGX is working and I can review the status of the Battery. No alarms nor issues can be seen.

If you turn a BYD module on, it always checks for short circuit condition before turning the internal relays on, which connects the battery with his DC output. If this is the case, it gives an error message (a. o. 5x buzzer) and turn itself off.

the challange is that while I can turn on the Multi and the CCGX (using external 12V power unit), I cannot turn on the Battery. To be more precisely I can turn on the Battery, but it goes off within few seconds after showing me the error. So the high voltage trigger is somewhere in the BMS of the Battery. Do you referring to a General flag within the BMS?

I have contacted the BYD support and keen get their guidance as well. Furthermore before any other action I'll update the Firmware of the Multi from 453 to 459, although I don't believe that this is the problem, but who knows...

I have chosen this module because it is cheap and there are several free and paid firmwares available for it. This module is sold for $24 on BangGood at the moment and the only drawback is that you will have to purchase an ST-Link V2 programmer in order to flash the custom firmware.

Pirx The Pilot is relatively new and with a bit less functionalities than the Achilles. For me it is far better than having none of that on the diversity receiver that comes with the Eachine VR D2 goggles. I really appreciate having features like auto search, favorites, OSD, manual tune and spectrum analyzer. For more extensive feature list along with explanations visit the features page on the firmware website.

Depending on the set of goggles that you own the upgrade process may differ from the one that is outlined below. Basically it comes down to hijacking the video input wire entering the goggles display and outputting the Pro58 video out onto that wire.

Based on the info that and the wiring diagram of the Eachine VR D2 that could be found on RC Groups I found that I have two video signal wires going into the display, the first oneV1 is from the build in diversity module and the second one V2 is form the DVR module that enables you to watch the recorded videos.

I have decided to cut the second video in wire and loose the functionality to watch the recorded videos. Also I will have to blindly control the DVR recording. I have split the video output cable coming out from the Pro58 module into two wires, one going directly to the second video input on the goggles display and the second one entering the DVR video in so I could preserve the DVR functionality.

3a8082e126