PicoScope 7 Software
Available on Windows, Mac and Linux
USBDrDAQ in Visual Basic
USBDrDAQ in Visual Basic
Hi,
please, what must be the output when I call the subroutine USBDrDaqDO(handle,3,3)?
Could you give me the correct statement to Declare this routine?
Thanks!
Armando
please, what must be the output when I call the subroutine USBDrDaqDO(handle,3,3)?
Could you give me the correct statement to Declare this routine?
Thanks!
Armando
-
Hitesh
Re: USBDrDAQ in Visual Basic
Hi Armando,
That will turn on IO channel 3 and will output 3.3V on that channel.
Please try the following to set the channel:
EDIT: Function call updated
Hope this helps.
That will turn on IO channel 3 and will output 3.3V on that channel.
Please try the following to set the channel:
Code: Select all
Declare Function UsbDrDaqSetDO Lib "USBDrDAQ.dll" (ByVal handle As Integer, ByVal IOChannel As Long, ByVal value As Integer) As Long
Hope this helps.
Re: USBDrDAQSetDO in Visual Basic
Hello,
thanks for the answer!
I modify slightly my Declaration statement, following your indication, but nothing change.
A 3 V LED is wired into channel 3. I'm using this approach inside your GetData macro:
Declare Function UsbDrDaqSetDO Lib "USBDrDAQ.dll" (ByVal handle As Integer, ByVal IOChannel As Long, ByVal value As Integer) As Long
Call UsbDrDaqSetDO(handle, 3, 5)
Hardware is OK. I have tested all the four I/O channels with PicoScope.
Please, there is another way to call this routine?
Best regards and thanks again!!
Armando
thanks for the answer!
I modify slightly my Declaration statement, following your indication, but nothing change.
A 3 V LED is wired into channel 3. I'm using this approach inside your GetData macro:
Declare Function UsbDrDaqSetDO Lib "USBDrDAQ.dll" (ByVal handle As Integer, ByVal IOChannel As Long, ByVal value As Integer) As Long
Call UsbDrDaqSetDO(handle, 3, 5)
Hardware is OK. I have tested all the four I/O channels with PicoScope.
Please, there is another way to call this routine?
Best regards and thanks again!!
Armando
Re: USBDrDAQ in Visual Basic
Hi,
following your indications I solved my problem of using I/O digital channels. I contacted the Support because the usage of those channels is not extensively described in the documentation, contrary at the very good presentation of the EXT inputs channels.
If the aim of the work consist of:
-measure some thing via the internal sensors of the Logger or through the EXT input channels,
-elaborate the so acquired information, and take a decision,
-translate that decision into an output signal or command,
from the result of my experience all these steps must be followed. I give them in scholastic mode:
Hardware
1. connect the Logger to the computer,
2. switch on the Logger if necessary;
Software
3. declare all the routines that will be called in the procedure looking at the
Format established into the DLL library,
4. call a routine to open the Unit in order of put it in conditions of
accepting commands,
5. verify that the Unit was open,
6. call a convenient routine for input the required information,
7. give enough time to the system for putting all the necessary operating
sequences into the stack,
8. call the DrDaqRun() command to execute the so given machine
instructions,
9. process and elaborate the arrived information from the external world,
10. take a decision and produce an output,
11. call a routine to put into the stack the sequences required to send-out
the signal or command so elaborated,
12. call the DrDaqRun() command to execute those instructions present
into the stack,
13. verify that the output action was executed by seeing or hearing a signal
arriving from some external device,
14. wait all the required time for a useful employment of the output action,
15. close the relative output routine,
16. close the Unit in order to live it in conditions of accepting further
commands by empting the stack.
I hope these statements could help some neophyte like me.
Sincerely
Armagi
following your indications I solved my problem of using I/O digital channels. I contacted the Support because the usage of those channels is not extensively described in the documentation, contrary at the very good presentation of the EXT inputs channels.
If the aim of the work consist of:
-measure some thing via the internal sensors of the Logger or through the EXT input channels,
-elaborate the so acquired information, and take a decision,
-translate that decision into an output signal or command,
from the result of my experience all these steps must be followed. I give them in scholastic mode:
Hardware
1. connect the Logger to the computer,
2. switch on the Logger if necessary;
Software
3. declare all the routines that will be called in the procedure looking at the
Format established into the DLL library,
4. call a routine to open the Unit in order of put it in conditions of
accepting commands,
5. verify that the Unit was open,
6. call a convenient routine for input the required information,
7. give enough time to the system for putting all the necessary operating
sequences into the stack,
8. call the DrDaqRun() command to execute the so given machine
instructions,
9. process and elaborate the arrived information from the external world,
10. take a decision and produce an output,
11. call a routine to put into the stack the sequences required to send-out
the signal or command so elaborated,
12. call the DrDaqRun() command to execute those instructions present
into the stack,
13. verify that the output action was executed by seeing or hearing a signal
arriving from some external device,
14. wait all the required time for a useful employment of the output action,
15. close the relative output routine,
16. close the Unit in order to live it in conditions of accepting further
commands by empting the stack.
I hope these statements could help some neophyte like me.
Sincerely
Armagi
-
Hitesh
Re: USBDrDAQ in Visual Basic
Thanks Armagi,
There was an error in the snippet of code which I will update.
Regards,
There was an error in the snippet of code which I will update.
Regards,