edgetx icon indicating copy to clipboard operation
edgetx copied to clipboard

Companion Simulator shows wrong tx battery voltage

Open MirlynG opened this issue 1 year ago • 6 comments

Is there an existing issue for this problem?

  • [X] I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Companion

Current Behavior

When opening a model on RM Pocket in Simulator, it shows the wrong battery voltage on the model page. i.e, radio voltage is 8.0 but shows a 6.7 in sim. It also plays the low battery warning, even though the battery range is set to 6.6-8.4v.

Expected Behavior

I'd expect that the simulator will reflect the radio voltage correctly.

Steps To Reproduce

Open a model in simulator and see resulting error.

Version

2.10.0

Transmitter

RadioMaster Pocket

Operating System (OS)

Windows

OS Version

10

Anything else?

I have uploade a video here: https://drive.google.com/file/d/1DZsGEfZc3gTu2-D8ZLq2N17LX7roOa2u/view?usp=sharing

CompSim1 CompSim2 Radio1 Radio2

MirlynG avatar May 22 '24 15:05 MirlynG

How exactly do you expect the simulator to know your radio battery voltage?

what you are showing is not the alarm range, but the indicator range. Alarm is a bit below

3djc avatar May 22 '24 16:05 3djc

This was all done immediately after reading from the tx and saving the .etx file. I would expect the voltage on Companion to be the same as it was at that time. I realise it won't change.

As for the alarm, yep my mistake.

MirlynG avatar May 22 '24 16:05 MirlynG

Clearly not how it is designed to work, so not a bug. what you want is an enhancement then, but I'm not overly sure it makes a lot of sense. Maybe allow to change it on the telemetry simulation panel

3djc avatar May 22 '24 16:05 3djc

This is the same for all radios btw, not specific to the RM Pocket or Windows. It is a hard-coded value that with stock settings shouldn't trigger the battery alarm. Not sure if it belongs in the telem simulation panel though, as it is a handset value, not telemetry... although there isn't really anywhere else to put it... i.e. it could be a simulator preference, but then that makes it hard to change if you want to change it dynamically... what about a dialog box off the tools menu?

pfeerick avatar May 23 '24 03:05 pfeerick

I have a similar issue with the Companion 2.10 simulator (Mac OS) and a RM Boxer. On Companion 2.9 simulator the Boxer battery is set to 7.9V and doesn't trigger my LV alarm (7.2V for 2S lipo):

screenshot_boxer_24-05-25_09-14-50

However, on Companion 2.10 simulator the Boxer battery is set to 6.5V and, hence, does trigger my LV alarm, which is annoying whilst trying to check out settings using the simulator:

screenshot_boxer_24-05-25_09-16-58

To get around this I'm reducing the LV alarm setting to 6.4V in the radio settings and then trying to remember not to write these settings to the radio (I think 3.2V/cell is too low for a lipo).

As I understand it, the 7.9V/6.5V values are hard coded in to the simulator and cannot be changed by the user? Is there any other way to disable the LV alarm in the simulator without altering the radio LV settings that are sent to the radio?

Chris-1066 avatar May 25 '24 08:05 Chris-1066

I am seeing the same problem with a boxer with all the default settings and the battery alarm goes off in the simulator

beau76 avatar Jul 23 '24 15:07 beau76

I've just updated to Companion 2.10.5 from 2.9.4 and encountered this problem.

In 2.10.5, the simulated Tx voltage is 6.8V, which triggers my low voltage alarm of 7.2V.

In 2.9.4, the simulated voltage is 7.7V, which does not trigger the alarm.

I use the relatively high alarm of 7.2V because of the high power requirements of some ELRS Tx modules. In some cases, Dynamic Power can really suck the juice from a transmitter pack and cause bad things to happen.

VancouverUmbrella avatar Jan 03 '25 00:01 VancouverUmbrella

This is the same for all radios btw, not specific to the RM Pocket or Windows. It is a hard-coded value that with stock settings shouldn't trigger the battery alarm. Not sure if it belongs in the telem simulation panel though, as it is a handset value, not telemetry... although there isn't really anywhere else to put it... i.e. it could be a simulator preference, but then that makes it hard to change if you want to change it dynamically... what about a dialog box off the tools menu?

A simulator preference would work for me. In fact, that's where I looked to see if such a preference already existed. Personally, I have no need for the value to be dynamic.

VancouverUmbrella avatar Jan 03 '25 00:01 VancouverUmbrella