[1] Request:
I would like to request an RMA (replacement, not refund) for my Herelink receiver.
The Korean reseller (ERCmall) received the defective unit but did not forward it to CubePilot.
They had been holding the item for about 4 years without taking any further action, and their response was very passive.
I have recently received the unit back from ERCmall, since they did not proceed with the repair.
If CubePilot can clarify an official position regarding this RMA case, I am willing to send the unit back to the reseller (ERCmall) again based on CubePilot’s decision.
I am not asking for a refund — a replacement would be much more reasonable and less burdensome for both sides.
[2] Reason for Request:
The Herelink receiver failed immediately after purchase, and the cause appears to be a labeling and documentation issue from the manufacturer.
The unit’s power label clearly states 5–12V, so I powered it with a 5V Ni-MH source to stay within that range.
However, the device failed instantly after applying 5V, which indicates that the actual safe operating voltage was higher than stated.
This misleading voltage labeling directly caused the failure — therefore, I believe it is the manufacturer’s responsibility, not user misuse.
For this reason, I am requesting a replacement through an official RMA.
[3] Purchase Date:
Around 2020–2021 (approximately 5 years ago)
[4] Model:
Herelink Beta
[5] Failure Details:
The power label on the Herelink unit indicates 5–12V.
Since a 3-cell Li-Po battery outputs up to 12.6V, I could not safely exceed 12V and instead used a 5V Ni-MH power source.
However, according to the following discussion, using 5V can cause a brown-out issue, and it seems to be a relatively common problem:
https://discuss.cubepilot.org/t/air-unit-not-working/7978/6
Here’s my original post from that time:
https://discuss.cubepilot.org/t/herelink-air-unit-wont-boot-up/6736
Given the incorrect voltage labeling and lack of proper documentation, I believe this failure was caused by a manufacturing responsibility, not by user error.
[6] Reason for Delay in Request:
At that time, the reseller initially failed to identify the root cause and mentioned it would be a paid replacement, so I paused the process.
Later, I had to onboard merchant ship to work for 2~3 years, making it difficult to follow up.
I still have a strong interest in ArduPilot open-source development and would like to continue contributing to the community — I’m modifying Mission Planner UI, although it is not revealed yet.
so I would really appreciate it if this issue could finally be resolved.