Clock output: JP2-17
Trigger in: JP2-46
There are nearby ground pins at JP2-19, JP2-49 and JP2-2Ext Ref Clk In: JP2-4
--
You received this message because you are subscribed to the Google Groups "The labscript suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labscriptsuit...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to a topic in the Google Groups "The labscript suite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/labscriptsuite/fGw7wU6RSsY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to labscriptsuit...@googlegroups.com.
Hi Rohit,BLACS will take care of it. BLACS chooses the correct firmware file based on the "reference_clock" keyword argument used in the connection table, and loads it onto the device using the Python API for Opal Kelly's Front Panel software. This of course only works if you have put the firmware files in the labscript_devices folder!So you do need Front Panel installed, but you don't have to load the firmware file yourself. I think the BLACS tab also has a button for flashing the firmware if you power cycle the device and don't want to restart BLACS.Cheers,Phil
To unsubscribe from this group and stop receiving emails from it, send an email to labscri...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "The labscript suite" group.
To unsubscribe from this group and stop receiving emails from it, send an email to labscri...@googlegroups.com.
Hi Rohit,
Unfortunately, sometimes the Opal Kelly installer doesn't detect the Python location properly (especially if you are using a Python virtual environment). The API is located here on windows: C:\Program Files\Opal Kelly\FrontPanelUSB\API\Python\In that folder you will see the API for v2 and v3 of Python, and for 32-bit and 64-bit Python.Pick the one that is appropriate for your Python installation and copy the ok.py and _ok.pyd files to C:\Your\Path\To\Annaconda\Environment\Lib\site-packages\ok\For me, this was C:\Anaconda3\Lib\site-packages\ok\ (or for a Python virtual environment C:\Anaconda3\envs\labscript_py36\Lib\site-packages\ok\ )If there isn't an "ok" folder, create it, then copy in the two files!If there is already an "ok" folder, delete it first (there is a package on PyPi called "ok" which is completely unrelated to Opal Kelly), then recreate the folder.P.S. I'm unsure about the default state of the output when no firmware is loaded. It's probably unpredictable though!Cheers,Phil.
Hi Rohit,
You can ignore the compilation warning. It's just due to the way we're changing how labscript_devices works. It's a warning saying the class is doing something unnecessary (but harmless).It's possible your main issue is a Python 3.7 problem. I would use conda to create a Python 3.6 environment to test in. You don't need to install the whole labscript suite to test, just copy the "ok" module in and try and import it in a terminal (using: import ok).Also, just to confirm, the _ok.pyd file does exist in the ok folder?Let me know how it goes!Cheers,Phil
assert self.dev.OpenBySerial(self.serial) == self.dev.NoError
Hi Phil,
I am sorry for the late reply.
Actually after the Opal Kelly started working I did not really dig into the case when I saw the error. However the Opal Kelly is not yet deployed in the experiment so I could test it. But since I am working on a different part of the experiment, I think I will do it later.
So I definitely had to change both the lines (self.dev.OpenBySerial and self.dev.ConfigureFPGA) as
you had suggested. After that everything was shown fine in BLACS.
But then (as I vaguely remember) when I tried to run too short a
code (like switch ON one DIO), I got an error about too less
samples written. The error did not occur on using more channels,
but I really have not yet tested it systematically.
I know that because of a DAQmX issue, one always has to use even
number of channels. But this error was something different.
Also thanks for the fixes. I will post an update here when I run
a re-check of the issue I had encountered.
Regards,
Rohit Prasad Bhatt
Hi Rohit,
Unfortunately I'm having trouble testing a solution because my Opal Kelly board is no longer being recognised by my PC.That said, I think the temporary solution for you is to change the line it is crashing on to:
assert self.dev.OpenBySerial(self.serial) == self.dev.NoErrorI was able to see the same error you did, but can't test if this is the correct fix due to not having working hardware.I'm guessing there is either something different about certain Opal Kelly Front Panel versions, or possibly a Python 2.7 vs 3.6 bug in my code, which is why the serial needed to be wrapped in bytes() on the PC I used to develop this code. Once I get working hardware I'll work it out properly, but for now I would just go ahead and make this change to your local copy to get it to work!P.S. You may run into a similar issue with the line self.dev.ConfigureFPGA(bytes(fpga_path)). Presumably removing bytes() will also fix that too if you get an error.Hopefully this is the last of the bugs!Cheers,Phil.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/604a54a5-7147-422f-8f54-39d97a01bb85%40googlegroups.com.
Hi Apoorva,That looks like a slightly different error. It seems that the assertion is failing, indicating that the code is correct, but couldn't connect to the device.Can you confirm if the OpalKelly Front panel software can see the board?Also, make sure that the FrontPanel software is not running while BLACS is as only one program can use the board at a time (You will likely need to revert any changes you've made to the BLACS device class as well as I'm reasonably confident it is correct).If FrontPanel works, but BLACS still doesn't, then there is something else wrong that I don't understand and we'll have to do some debugging together to get to the bottom of it!Cheers,
Phil
To unsubscribe from this group and stop receiving emails from it, send an email to labscri...@googlegroups.com.