Some problems encountered while using the simulator

🆘 Support
1

Since the virtual box is difficult to use， I moved the simulator to a Ubuntu 24.04 system, and it runs ok， and the ‘client_discovery’ example can find the simulator and make a connection to it.

Then I downloaded the openDAQ source code from GitHub, successfully compiled it, and replaced the application_simulator program and all dynamic library files in the original program path. The program runs successfully, and the logs printed are consistent with the version on VirtualBox.

However， The ‘client_discovery’ program can detect the simulator, but the program crashes when attempting to connect (using instance.addDevice ). I compiled a debug version of the dynamic library and obtained the error message shown in the screenshot below. Unfortunately, I still cannot determine the root cause or figure out how to fix this issue.

image
image2469×1253 281 KB

and the following is the log of the simulator:
image
image1293×112 28.4 KB

Thank you in advance for your help.

2

Hi welling, can you please share on which version of openDAQ you observed this?

3

V3.3.0，the latest version

4

Thank you! I will let you know here as soon as there is progress on the front.

5

Hello, would it be possible for you try the latest 3.10 version that’s been released today?

It’d be the easiest to check whether you are able to connect to the simulator via python GUI application that can be accessed by running the following shell commands

py -m pip install opendaq
py -m opendaq
1 Like
6

:ok_hand:，I’ll try that later

7

@welling Any updates?

8

I tried it on a windows pc.
If the simulator and the opendaq demo is on the same pc, things work ok;
if they are on different pc in a LAN network, simulator cannot be found from the opendaq demo

9

There is a known issue with client_discovery.cpp example (while running Virtual Box simulator), it fails with:

daq::DuplicateItemException
Device with the same local ID already exists.

Is this the issue you are facing?

There is a potential fix coming, I will test it and let you know if it helps.

Then you can try the newer version of openDAQ SDK.

10

I haven’t encountered this exception; I think it might be due to something else. Of course, I will verify it as soon as the new version is released.

11

@welling I think the issues you were facing should now be resolved on the latest main. You can get the latest development version here: https://docs-dev.opendaq.com/.