High CPU using VitalSignsCaptureDrgHL7

[Nico H]

Thanks you for your wonderful job!

I'm using it with a Dräger Vista 120S.

I'm afraid that I have an issue with it, when I launch the app like this :
/usr/bin/dotnet /var/www/myproject/VSCaptureCLI/VSCaptureCLI.dll --devices 1 --device1type 1 --device1model 4 --device1arg -interval 5 -export 2 -devid Moniteur1 -url https://MYDOMAIN/api/moniteur/probe/1 -port 192.168.70.1

It uses instantly 100% of my CPU and create several processes (even if the client is not connected) (please see attached image).

Here is the stdout of the CLI:

Command line used for CLI: --devices 1 --device1type 1 --device1model 4 --device1arg -interval 5 -export 2 -devid Moniteur1 -url https://MYDOMAIN/api/moniteur/probe/1 -port 192.168.70.1

VitalSignsCaptureDrgHL7v1.001 (C)2023-24 John George K.
For command line usage: -help

Connecting to 192.168.70.1...

Requesting Transmission set 5 from monitor

Data will be written to CSV file DrgDataExport.csv in same folder

Press Escape button to Stop
Error opening/writing to TCP port :: No route to host [::ffff:192.168.70.1]:9100

The problem already was with v1.004.
Is there a fine-tuning to use in order to solve this way ? Or a bugfix to do ?

I stay available if you need more information.

Thank you by advance for your answer 😊

Best regards,
Nicolas

[John George]

Hi Nicolas,

From the output (in CSV & JSON url export mode) , it seems the app is not able to connect to the monitor port. Ensure the monitor is set to the correct IP address (check service menu) on the same network & subnet or if the port is not blocked for any other reason.

Have you tried running the app with just JSON file export and then uploading the file in another process with tail -f? Alternatively, you can try MQTT export but test the local file export first.

Please email xeonfusion at yahoo dot com for further troubleshooting.

Regards,
John.