gilgeonics

Thanks Fausto for the explanation and Omni installation instructions. Like a lot of the directions I've been trying they just don't seem to work at first, but eventually got there. Things are going ok so far and hopefully I won't need to bother you again, at least for a while. Thanks again and best regards - Gil

I'm trying to port an app that works with a dt9816 on a win7 Panasonic Toughbook (and has run for many years) to a win11 computer. I installed Instacall 6.74, but it doesn't see the board. I checked the DT9816UM manual but found little help and bad links. I saw reference to a special 5 line usb header for the board, but the actual connector on the board and the cable it has been running with seem to be standard. I'm not able to locate the original info for the board, but it does have a label with the numbers 142520B and 1CE990F. The win7 system is running instacal 6.73, but when I try to download this the only versions available are much earlier, and v6.23 is now claimed to be the "latest". What is going on? What should I try next ? Thanks for your help - Gil

Workaround: Set scan to reset after each read, add count to final total count which can be re-set as wanted.

Hi, We make equipment that uses a USB-1604HS-2AO. I am now trying to add a pulse counter function using one of the counter inputs - cbCConfigscan() and cbCIn32(). However I find that the cbCClear() function fails to reset the count. Further, if I run, exit the program and then re-start, the count still does not reset unless I turn everything off first. Any suggestions?

Hey John, Fausto: So migrated to a Win10 system and VS2022 (must have taken hardly an hour once the download done). No difference. Problem was hardware. I suppose I should be embarassed, but I'm just grateful. Thanks for your help along the way - Gil

Hi again John - spoke too soon re things being ok. We have two different systems that use the USB-1604HS-2AO, call them E and G. Problems started when trying to revise coding for E. Revisions had nothing to do with DAQ coding, but after compiling, the A/O function was not operational. Revised initialization coding according to your example and eventually all seemed ok (D/A output ok, A/D channels all working), but some problems with E hardware. After fixing hardware, the software now finds only 1 Analog input channel, and there is no D/A output, although the output code runs without error messages. The initialization coding with your test section modified to check 4 AI's seems to run ok. Tried to check with system G, which runs ok with software dated Nov/22, and Win10. However when trying with same .exe on a different Win10 computer (or with a Win7) get message that cannot find A/O. Original installation continues to work ok. What can be causing this behavior? Is instacal being updated automatically and changing something? (It is always being used when boards are switched) To get the revised E coding to run it was necessary to download the latest Instacal instead of v6.55 which you had suggested. Suggestions? Thanks - Gil

Hi John - Success!! Colleague could not compile coding you sent, but I patched and adapted into the target source coding, and at this point things look good. Many thanks for your help - Gil

Hi John - Thanks for the program. A colleague will compile and we'll try tomorrow. InstaCal does see the board and recognizes it as USB-1604HS-2AO. Regards - Gil

Hi John, I put your coding into the software, adding the type declaration "DaqDeviceDescriptor DeviceDescriptor,inventory[50];". I also moved "cbIgnoreInstaCal();" ahead of "ULStat = cbDeclareRevision(&Rev);" However on running, "numberofdevices" is 1, and the coding exits with "USB device not found..". The board is definitely connected - the blue LED is on and the system makes the appropriate beeps on connecting or disconnecting. Suggestions?

Thanks John, I'll give it a try Monday - Gil

Getting farther!! Replaced cbw files in source folder with versions from new download (v6.73) and compile is ok now. But there are still problems. When cbIgnoreInstaCal() is not used, the D/A "function cannot be used" message is thrown. And when it is used (first cb call) the software doesn't seem to see the board at all: GetNameOfBoard returns 0 with no name for the board (""). Again, suggestions? Thanks John & Fausto.

Hi John, Fausto, I reloaded the MCC CD software with the current version, including TracerDAQ v2.3.4 and InstaCal v6.73. Tried TracerDAQ A/O test and it seemed ok as long as board was plugged in(waveform shifted when offset was changed), complained when unplugged. But same _IFC variable errors on compiling.

Hi, Uninstalled Instacal and re-installed with the installer from the link you sent (same .exe that seemed to work a couple of days ago). But now the only files in c:\users\.....\DAQ\c\ are cbw.h, cbw32.lib and cbw64.lib, all dated 2017, plus folder sample32\ which has only a lot of small .c files dated 6/6/2016 plus 2 very small .bat files. System32 no longer has any cb*.dll files. (There are a number of Cbs*.dll files in other \windows\ folders.) What have I done wrong? Try again?

Hi John, So in cbw.h I added "#ifndef USB_IFC" in front of the "typedef enum" section that throws the errors, and added "#endif" after. No difference. Changed to "#ifndef DaqDeviceInterface" - Same Commented out whole "typedef" section, got many errors in other sections.

Hi again John: Getting farther but still no cigar! Instacal 6.55 installed from the link you sent. (It declined to install DAQami because the existing version was as new or newer.) I copied the cbw.h file to both the Include and source folders, and cbw32.lib to the lib folder. However when I tried to re-build the solution I got the following set of errors: 1>Contadc.c 1>c:\em633data\cbw.h(25) : warning C4005: 'CURRENTREVNUM' : macro redefinition 1> c:\em633data\em633-e\cbw.h(23) : see previous definition of 'CURRENTREVNUM' 1>c:\em633data\cbw.h(1513) : error C2365: 'USB_IFC' : redefinition; previous definition was 'enumerator' 1> c:\em633data\em633-e\cbw.h(1511) : see declaration of 'USB_IFC' 1>c:\em633data\cbw.h(1513) : error C2086: 'USB_IFC' : redefinition 1> c:\em633data\cbw.h(1513) : see declaration of 'USB_IFC' 1>c:\em633data\cbw.h(1514) : error C2365: 'BLUETOOTH_IFC' : redefinition; previous definition was 'enumerator' 1> c:\em633data\em633-e\cbw.h(1512) : see declaration of 'BLUETOOTH_IFC' 1>c:\em633data\cbw.h(1514) : error C2086: 'BLUETOOTH_IFC' : redefinition 1> c:\em633data\cbw.h(1514) : see declaration of 'BLUETOOTH_IFC' 1>c:\em633data\cbw.h(1515) : error C2365: 'ETHERNET_IFC' : redefinition; previous definition was 'enumerator' 1> c:\em633data\em633-e\cbw.h(1513) : see declaration of 'ETHERNET_IFC' 1>c:\em633data\cbw.h(1515) : error C2086: 'ETHERNET_IFC' : redefinition 1> c:\em633data\cbw.h(1515) : see declaration of 'ETHERNET_IFC' 1>c:\em633data\cbw.h(1517) : error C2365: 'ANY_IFC' : redefinition; previous definition was 'enumerator' 1> c:\em633data\em633-e\cbw.h(1515) : see declaration of 'ANY_IFC' 1>c:\em633data\cbw.h(1517) : error C2086: 'ANY_IFC' : redefinition 1> c:\em633data\cbw.h(1517) : see declaration of 'ANY_IFC' 1>c:\em633data\cbw.h(1531) : error C2371: 'DaqDeviceDescriptor' : redefinition; different basic types 1> c:\em633data\em633-e\cbw.h(1529) : see declaration of 'DaqDeviceDescriptor' I only find "_IFC" in file ifc.h, and the only versions I have under c:\users\ are both dated 25/01/2013, slightly different times & sizes, and both give the same compile errors as above when copied to the source directory. Sorry to have to keep asking, but what to do from here? Thanks for your help - Gil

Hi again John, I tried to download instacal again from the archived list, this time v6.60, with the same result as when I tried 6.55; I.e. notice "failed to fetch" after the re-start, and no MCC DAQ folder under c:\users\, only under c:\program files\ with old files. What to try next? Thanks - Gil

Hi John, Thanks for the instructions. I did download v6.55, but after the re-start there was a message "failed to fetch" (or something like that). Couldn't find a DAQ folder anywhere under under c:\users, but did find under c:\program files\measurement computing, dated today. However this only contained .exe & .dll (and some .txt) files, all dated 2016 or 2017. No .libs or .h's. Should I try one of the newer versions? Thanks - Gil

Hi again; I thought I had found the answer to the USB-1604 D/A problem, i.e. add the call "cbIgnoreInstacal ()" when initializing the board. Unfortunately this throws a linker error " cannot open file '.\lib\cbw32.lib' ". The same message appears whether cbw32.lib is in the include\lib folder or in the main folder with the source files. Last summer all was working ok (with the call?). Any suggestions?

Hi John, Thanks for the help - I'll give it a try tomorrow. (Instacal was installed from the website.) Regards - Gil

Hi John, Thanks for your response; at least now I know that Instacal won't be a help. Is there other MCC software I could use to test? Our software uses the library with OLD*.h files. The particular call that gives the "function can not be used" message is FindAnalogChannelsOfType(... , ANALOGOUTPUT , .....). We have used this DAQ (previous boards) and software for a number of units with no problems. So it looks like this particular board is the problem now. Thanks & regards - Gil

Trying to use a new USB-1604HS-2AO board (s.n. 1000127) in our equipment, but the D/A function isn't working. Driver software gives a message "X function can not be used with this board". Trying Instacal, the "Calibrate" tab on the top line shows an A/D option, but the D/A option is greyed. The next line also shows an A/D graphic, but the D/A graphic is also greyed. Does this mean the board is bad? Should I be able to test the D/A with Instacal?

How can I find documentation re error messages that occur when running a DT9816 DAQ with VS C++? (On Win7.) I do have the list of messages & numbers in Olerrors.h UMDataAcq.pdf does give a bit of information about a couple of the messages on pages 160 and 162, but I'm looking for much more. How to find?

cbDaqInScan( ..| EXTCLOCK .. ), with clock at a/d rate

Hi, How to use external clock on usb-1604HS? Using C++, have not been able to find enough detail in ULHelp: how to configure; frequency (10MHz, a/d rate, or??). Any suggestions? Where to find further documentation? Thanks - Gil

How to use the external clock on a USB-1604HS DAQ? How to configure; does it need 10MHz or the a/d sample rate or? I couldn't find in ULHelp.