Feature Request: Multi-Device Monitoring and Extended Graph Functions

[Stam-59]

Hello,

First of all, thank you for this great application. I use it regularly for audio amplifier measurements and monitoring, and it has become a very useful tool for my work.

I would like to suggest a few features that could make the application even more powerful for long-term amplifier testing and monitoring.

1. Multi-device support

It would be very useful to connect multiple devices simultaneously on the same interface.
For example:

• 2 devices dedicated to bias measurements
• 2 devices dedicated to temperature monitoring

This would allow monitoring several amplifier parameters at the same time from a single interface.

2. Extended time base ranges

Longer monitoring intervals would be extremely helpful for thermal stability tests and long-duration measurements.

Suggested ranges:

• 30 seconds
• 1 minute
• 5 minutes
• 10 minutes
• 30 minutes
• 1 hour
• 2 hours
• 4 hours
• 8 hours

3. “Clear Graph” button

A button to clear/reset the graph data and restart the graph from zero would also be very useful during measurements and testing sessions.

4. High / Low alarm thresholds

Another very useful addition would be the ability to configure alarm thresholds with:

• High limit alarm
• Low limit alarm

This would help detect abnormal bias drift or temperature issues automatically during monitoring.

Thank you again for your excellent work and for considering these feature requests.

[maj113]

Thank you for the kind words and the detailed suggestions! Good news, most of these are already in the works for the C++ version.

Regarding point 3, it's actually already implemented There's a "Clear" option in File menu in the menubar:

Although I understand that it is confusingly placed (and named) in the File Menu, it might be better if it was placed in a View menu or something

For point 1, two simultaneous devices should work, but Bluetooth (BLE) on Windows is fairly unreliable in general, so I wouldn't count on stable connections with more than that.

Regarding 4. What would you want the Alarm to do? e.g. what should it do on the condition, alert with a message box, stop sampling until alarm cleared etc?

Stay tuned for the C++ release, it should address most of your other requests.

[Stam-59]

Thank you for your reply. I’m very happy that my suggestions are being considered, and I’m looking forward to future versions of the application with great enthusiasm.

Also, thank you for pointing out the graph clear/reset button — I had completely missed it. Its location is perfectly fine once you know where to find it 🙂.

Regarding the possibility of using multiple devices simultaneously, I completely understand the limitation and the fact that it is outside the scope of your application. I had not considered that aspect before.

About point 4 regarding alarms, what I had in mind would mainly be a non-intrusive visual alarm indicator, for example a colored warning light or status indicator on screen.
Possibly an optional sound alarm as well.

The important point is that the alarm should NOT block the measurement process.
It would be better to avoid popup dialog boxes requiring the user to click “OK”, as this can become very inconvenient during amplifier calibration or long monitoring sessions.

Ideally:

the alarm activates automatically when the measured value goes outside the target range
the alarm stops automatically when the value returns inside the acceptable range

For example, during amplifier bias adjustment, a common target could be:

5 mV ±0.5 mV

This creates an acceptable operating window, and the alarm would trigger only when the measurement goes outside this range.

Another small suggestion that could improve the interface usability would be the ability to hide/show sections such as:

RAW packets
Connected devices

This could help keep the interface cleaner and more focused during measurements.

Thank you again for your work and for taking the time to discuss these ideas.

[maj113]

also regarding the multi device support, as a workaround you can open up another app window
something like this:

although note that even this way one device seems to always drop after a couple minutes (at best) sometimes earlier