The device file for the Owon ODP6033 is for IP communication. The address would be the IP address of the ODP6033.
Ah, makes sense thanks for the quick reply. When I have time I may try to read into HKJ's documentation to see about a usb configuration.
If the Owon uses a virtual serial power for USB communication you only need to add the word "com" after the port number in the device definition file.
I have not yet had the chance to test if it works at all, but...
At my work we have a KP284 which more or less is just two separate KP184 in one cabinet, but with just the RS-485 interface. Is there any chance the TestController Java program could be made working for both channels at the same time, like eg. expanding the address range to include 1 & 2 ?
Since I now own a Siglent SDG 2042X, I am now upgrading may home grown measurement amplifiers and precision rectifiers to 1 MHz and producing a reasonably fast F/V converter. My VC940 is pretty slow in this area and the Keysight 34465A is only good up to around 400 kHz. The Siglent can, while sweeping, not be queried as to the momentary frequency.
While doing so, I was wondering on a different track why the sound card output can not be used with "Test Controller". Has nothing to do with my 1 MHz drive, but having 16+ bit AD/DA capability to measure voltages and frequencies is in my opinion an opportunity which should not be lost, if not too difficult to implement.
Any ideas?
Why not control the Siglent directly from TestController? It already contains script for doing a logarithmic frequency sweep. As for measuring voltage, it is possible to use the voltage measurement from a oscilloscope, TestController has a few (The dynamic range may be too low without changing input range on the scope).
I do not have any experience in sound analysis, not that it would be that hard to search a recorded curve for zero crossings and calculate frequency and rms values. This will, of course, only work for a fairly clean tone. The level will, of course, be relative, as far as I remember sound cards to not have any well defined calibrations.
Will look into that script thing. My abilities are certainly not the best in this area .
Thanks for the hint. Will try as soon as I get up in the morning. 7 hours or so from now.
OK. The log generator script worked to an extent. Script controlled generator sweeping worked.
But experienced bad freezes before the graph completion. Had to restart windows and the Siglent in each case.
What's also been bugging me is that upon starting to log and when changing to Chart,
the X-axis is always set to time and I will then have to change the X-axis type each time. I.e. the X-axis setting is not retained. By the time I have done that, a sweep, for example, has already finished.
Just one further idea: Why can't the generator which is to be controlled be selected through the VLG popup?
Starting
;; Start thread for: 192.168.1.173 - Kollmorgen AKD1G Servo
;; : Tx <txrx? DRV.INFO>
;; 192.168.1.173: Tx: <DRV.INFO..> 44 52 56 2E 49 4E 46 4F 0D 0A
;; 192.168.1.173: Rx: <Drive model : AKD-P00606-NBEC-0000> 44 72 69 76 65 20 6D 6F 64 65 6C 20 20 20 20 20 20 20 20 20 20 20 3A 20 41 4B 44 2D 50 30 30 36 30 36 2D 4E 42 45 43 2D 30 30 30 30 0D
;; Found Kollmorgen AKD1G Servo on 192.168.1.173
;; Start thread for: 192.168.1.173 - Kollmorgen AKD1G Servo
;; : Tx <txrx? DRV.INFO>
;; 192.168.1.173: Tx: <DRV.INFO..> 44 52 56 2E 49 4E 46 4F 0D 0A
;; 192.168.1.173: Rx timeout 1000ms In buffer:
;; 192.168.1.173: **Device do not match** <Unknown>
;; : Tx <txrx? DRV.INFO>
;; 192.168.1.173: Tx: <DRV.INFO..> 44 52 56 2E 49 4E 46 4F 0D 0A
;; 192.168.1.173: Rx timeout 1000ms In buffer:
;; 192.168.1.173: **Device do not match** <Unknown>
;; Stopping thread for: 192.168.1.173 - Kollmorgen AKD1G Servo
I just updated to V1.09 and I think I found an obscure debug mode bug.
I am working to start writing scripts using the #math script statement to record extra data from the device. Inside the script I need to refer to the logged value. Before, for values defined in the device file with #value and polled in #askValues, I used <Device name>.<signal name>. For example, like AKD2G.A1_Current. When using #math with formulaNU for extra log data how do you refer to the value in a script?
I tried math.<signal name> but got errors.
I just updated to V1.09 and I think I found an obscure debug mode bug.
Please check on the dos window if there are some Java error messages.