I’m using a XEM3001v2 as recognized by the front panel. I am able to use the first.bit from the downloads for the xem3001v2 part and front panel says the configuration completed successfully. I run first.xfp and that seems to work normally. But there is no commuication / feedback from the first example. Basically, there are no errors or warnings, just nothing happens. The only thing I am curious about is that the front panel interface says USB 1.0 in the small brown/black box in the lower left corner. I wonder if that is a problem. This computer is only a couple of years old so I don’t think it is a hardware issue although maybe there is some issue with drivers somehow. I will try to experiment with a different computer and see what the results are.
You see it recognized by the USB drivers but the Front Panel does not notice it plugged in. There must be something simple I am doing wrong.
[ATTACH=CONFIG]240[/ATTACH]
usb_prob.JPG (58.7 KB)
This picture shows the device being recognized in the new way (under FrontPanel devices) and the FrontPanel recognizing the device, but the first does not communicate with the device. I still cannot figure out what I am doing wrong.
Thanks for any help.
[ATTACH=CONFIG]241[/ATTACH]
first_prob1.JPG (64.2 KB)
I turned my attention to pipetest to see if I could see something working. Strangely, it is reporting incredible transfer speed on some items. So I don’t think it is really communicating although the program thinks it is.
Here are the pipe test bench results.
C:\Program Files\Opal Kelly\FrontPanelUSB\Samples\PipeTest>PipeTest.exe pipetest.bit bench
---- Opal Kelly ---- PipeTest Application v1.0 ----
FrontPanel DLL loaded. Built: Feb 1 2012 16:56:13
Found a device: XEM3001v2
Device firmware version: 2.2
Device serial number: hJdJwWhsTH
Device device ID: Opal Kelly XEM3001
FrontPanel support is not enabled.
UpdateWireIns (1000 calls) Duration: 0.625 seconds – 1600.00 calls/s
UpdateWireOuts (1000 calls) Duration: 1.000 seconds – 1000.00 calls/s
ActivateTriggerIns (1000 calls) Duration: 0.250 seconds – 4000.00 calls/s
UpdateTriggerOuts (1000 calls) Duration: 1.000 seconds – 1000.00 calls/s
Read BS:1024 SS:4194304 TS:67108864 Duration: 0.000 seconds – 1.#J MB/s
Read BS:1024 SS:4194304 TS:33554432 Duration: 0.000 seconds – 1.#J MB/s
Read BS:1024 SS:4194304 TS:16777216 Duration: 0.000 seconds – 1.#J MB/s
Read BS:1024 SS:4194304 TS:8388608 Duration: 0.000 seconds – 1.#J MB/s
Read BS:1024 SS:4194304 TS:4194304 Duration: 0.002 seconds – 2000.00 MB/s
Read BS:1024 SS:1048576 TS:33554432 Duration: 0.000 seconds – 1.#J MB/s
Read BS:1024 SS:262144 TS:33554432 Duration: 0.031 seconds – 1032.26 MB/s
Read BS:1024 SS:65536 TS:16777216 Duration: 0.062 seconds – 258.06 MB/s
Read BS:1024 SS:16384 TS:4194304 Duration: 0.063 seconds – 63.49 MB/s
Read BS:1024 SS:4096 TS:1048576 Duration: 0.062 seconds – 16.13 MB/s
Read BS:1024 SS:1024 TS:1048576 Duration: 0.266 seconds – 3.76 MB/s
Read BS:900 SS:1048500 TS:33553800 Duration: 0.000 seconds – 1.#J MB/s
Read BS:800 SS:1048000 TS:33554400 Duration: 0.000 seconds – 1.#J MB/s
Read BS:700 SS:1047900 TS:33553800 Duration: 0.000 seconds – 1.#J MB/s
Read BS:600 SS:1048200 TS:33554400 Duration: 0.000 seconds – 1.#J MB/s
Read BS:512 SS:1048576 TS:33554432 Duration: 0.000 seconds – 1.#J MB/s
Read BS:500 SS:1048500 TS:33554000 Duration: 0.000 seconds – 1.#J MB/s
Read BS:400 SS:1048400 TS:16777200 Duration: 0.000 seconds – 1.#J MB/s
Read BS:300 SS:1048500 TS:16777200 Duration: 0.000 seconds – 1.#J MB/s
Read BS:256 SS:1048576 TS:16777216 Duration: 0.000 seconds – 1.#J MB/s
Read BS:200 SS:1048400 TS:8388600 Duration: 0.000 seconds – 1.#J MB/s
Read BS:128 SS:1048576 TS:8388608 Duration: 0.000 seconds – 1.#J MB/s
Read BS:100 SS:1048500 TS:8388600 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:4194304 TS:67108864 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:4194304 TS:33554432 Duration: 0.016 seconds – 2000.00 MB/s
Write BS:1024 SS:4194304 TS:16777216 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:4194304 TS:8388608 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:4194304 TS:4194304 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:1048576 TS:33554432 Duration: 0.000 seconds – 1.#J MB/s
Write BS:1024 SS:262144 TS:33554432 Duration: 0.032 seconds – 1000.00 MB/s
Write BS:1024 SS:65536 TS:16777216 Duration: 0.063 seconds – 253.97 MB/s
Write BS:1024 SS:16384 TS:4194304 Duration: 0.062 seconds – 64.52 MB/s
Write BS:1024 SS:4096 TS:1048576 Duration: 0.063 seconds – 15.87 MB/s
Write BS:1024 SS:1024 TS:1048576 Duration: 0.265 seconds – 3.77 MB/s
Write BS:900 SS:1048500 TS:33553800 Duration: 0.000 seconds – 1.#J MB/s
Write BS:800 SS:1048000 TS:33554400 Duration: 0.000 seconds – 1.#J MB/s
Write BS:700 SS:1047900 TS:33553800 Duration: 0.016 seconds – 1937.50 MB/s
Write BS:600 SS:1048200 TS:33554400 Duration: 0.015 seconds – 2066.67 MB/s
Write BS:512 SS:1048576 TS:33554432 Duration: 0.000 seconds – 1.#J MB/s
Write BS:500 SS:1048500 TS:33554000 Duration: 0.016 seconds – 1937.50 MB/s
Write BS:400 SS:1048400 TS:16777200 Duration: 0.000 seconds – 1.#J MB/s
Write BS:300 SS:1048500 TS:16777200 Duration: 0.000 seconds – 1.#J MB/s
Write BS:256 SS:1048576 TS:16777216 Duration: 0.000 seconds – 1.#J MB/s
Write BS:200 SS:1048400 TS:8388600 Duration: 0.015 seconds – 466.67 MB/s
Write BS:128 SS:1048576 TS:8388608 Duration: 0.000 seconds – 1.#J MB/s
Write BS:100 SS:1048500 TS:8388600 Duration: 0.000 seconds – 1.#J MB/s
Did you ever fix this problem? I am having a similar issue. Thanks.
The problem above is most likely the wrong pipetest.bit file for the XEM3001. As you can see, it downloads the file but then reports “FrontPanel is not enabled”.
I have not solved the problem yet. I note that the firmware that this board is set to is Version 2.2 which I see when I click the “Firmware Update Wizard” menu item under the FrontPanel Interface. I would like to upgrade this to firmware version 3. Can you help me do that? I cannot find where to download the firmware from the web site.
Thanks for any help.
There is an incompatibility with the most recent versions of FrontPanel software with older (pre 3.0) USB 2.0 firmware. We’re still working on this and hope to have something to fix it in the next release.
Alternatively, you can contact support to send your device back and have us upgrade it to 3.1 firmware.
I reprogrammed the firmware (Version 2.2) on the board and now the board is finally responding. I am having some issues because I’ve got different versions of the sample .bit and .xfp files. I don’t know what might have corrupted the firmware but this seems to be the cause of the problems.