Having Issues Writing a Server Config

[aidanj5]

Sorry, I don't know if this is the best place to put this, but I do not understand why something I am writing is not working.

I am trying to connect a simulated DAQ to the new instrument server. It worked fine on the old nspyre. Now, this is the result I get, followed by three different tracebacks.

I took the input I had in the old code, which is the picture shown below:

I transferred it to a new config file set up as default to my instrument server, and I believe I put it in the correct syntax.

The other simulated instruments load properly. The only informative error message I am able to get is the following:

However, I don't understand this. What am I doing wrong?

Note: I am starting the inserv with the daq instrument commented out. I then uncomment it, reread the config, and type ">dev daq" to connect the device. If I have it uncommented while I start the server, I am not able to keyboard interrupt, so I have to restart my terminal.

[jacobfeder]

Hi @aidanj5 , I suspect this may have something to do with outdated values in mongodb from the previous version of nspyre conflicting with the new version. Can you try rerunning nspyre-mongodb and see if that changes anything?

[aidanj5]

After a computer restart for the night, I reran nspyre-mongodb in one command prompt. Then "lantz-sims fungen tcp" for the fake instrument in another. Then nspyre-inserv in another.

I make sure mongo is working, after seeing this prompt :

I get a bunch of these debug messages from PyVISA, I'm unsure what this tells me.

Then I get the errors still.

Am I doing something wrong with running mongodb?

[aidanj5]

I just realized, the mongo server version is 4.2.10, despite having 4.4 on my computer. I am going to try to reinstall mongodb.

[jacobfeder]

Everything looks ok to me (except for the error of course). The mongo shell version doesn't particularly matter. I can take a closer look with you.

[mtsolmn]

hi @aidanj5, try using the following in the config file and let us know the error you get:

...
daq:
  lantz_class: ni.simple_daq.Read_DAQ
  args: [{'Dev1'}]
  kwargs:

I'm not sure if that will work, but I'm interested in the error you get if it doesn't. Thanks.

[jacobfeder]

@mtsolmn - @aidanj5 and I traced it a bit this afternoon and it seems to be an issue inside the DAQ lantz driver. I suspect something resulting from the transition to new lantz. We fixed the issue, but then immediately ran into something else. I think there may be several more changes required to get it up and running on new lantz. I've filed a report in lantz-drivers: https://github.com/lantzproject/lantz-drivers/issues/9

[aidanj5]

Just to be clear, I tried your suggestion @mtsolmn, and there is no change. I still have the same errors. The traceback shows that the error occurs when calling the lantz_class. @jacobfeder and I found there are problems with the initialization of the DAQ driver, and so this result is expected. Still, thank you for the suggestion!

[mtsolmn]

yes, thanks for the update both of you. I just wanted to confirm that this was an issue with the lantz driver and not something that needed to be addressed on the nspyre side. I'll leave this open for now, but maybe we close this soon.

I will also mention that there is a relatively new python API from National Instruments called ni-daqmx that is feature complete -- everything you can do in LabView with their DAQs you can now do through python -- until pydaqmx. It's also the official and supported python API now. We are trying to get everyone internally to use it going forward. Although there is no lantz driver for it, we have documentation for it available here: https://nspyre.readthedocs.io/en/develop/guides/ni-daqmx.html