Products > Test Equipment
Hantek HDG2002B AWG: 5Mhz or 100MHz? Let's see!
<< < (94/134) > >>
fremen67:

--- Quote from: markone on March 06, 2015, 12:24:25 am ---Hi Fremen,

i tried your 1.00.3 update package on my HDG2002B (PCB 1004, SW 1.00.2, FPGA 20, KB 3) and my generator started to improperly read signal amplitude setting and to fail output & zoom steps on selftest.

Previously selftest was fully OK.

Reverting to 1.00.2 did not solved self test errors, while signal amplitude is almost right.

Do you have any suggestion to fix it ?

Useless to say, i have not done FW backup before to upgrade  |O

--- End quote ---

The calibration data are completely different beetween 1.00.2 and 1.00.3.
In fact I had exactly the same problem when I upgraded to 1.00.3. I suppose it's coming from the calibration data provided with 1.00.3.
The problem was solved after a full calibration.
I suggest you run a full calibration too. What kind of scope do you have? At least if you don't have a rigol ds1000Z, you can use the exel calibration tool I posted to ease the calibration process.
If your scope is SCPI compliant, the calibration tool could easily be adapted.

Edit: The calibration data file for fw 1.00.3 has no values after 30Mhz. So if you changed your device model, f.e. to HDG2102C, you will have anyway to perform a calibration of both channels.
fremen67:

--- Quote from: smgvbest on March 06, 2015, 02:50:11 am ---FWIW
My HDG2002B with that came with the 1.03 and it fails the self test for the zoom unit 1 I think on both channels
you can see my posts earlier on it with screen shots so that part is known.  I thought I had a defective unit but now I believe it's a bug in 1.03

--- End quote ---
Did you manage to use the calibration tool? I think it could be worth running a full calibration of your unit. This solved the selftest problem on mine.
smgvbest:

--- Quote from: fremen67 on March 06, 2015, 05:00:23 pm ---Did you manage to use the calibration tool? I think it could be worth running a full calibration of your unit. This solved the selftest problem on mine.

--- End quote ---

I have not run it yet.  Not had the time or a PC near the equipment.   I was trying to get the Connection Manager to work over the network and it won't see my Rigol Scope at all.  But that won't help with the HDG so need to see how I'd get USB going or move stuff closer to the PC
smgvbest:
I get an error when running your script on a 64bit PC/Excell

I found this on the errors which is basically Declares must be changed as well as some Longs to be compatible with 64Bit Systems
https://msdn.microsoft.com/en-us/library/office/ee691831%28v=office.14%29.aspx

I made a change which seems to work.  at least I don't get the error anymore but I've not run it for real yet.

Changed
Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long)
to
#If VBA7 Then
    Private Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As LongPtr) 'For 64 Bit Systems
#Else
    Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds as Long) 'For 32 Bit Systems
#End If
fremen67:

--- Quote from: smgvbest on March 06, 2015, 07:10:04 pm ---I get an error when running your script on a 64bit PC/Excell

I found this on the errors which is basically Declares must be changed as well as some Longs to be compatible with 64Bit Systems
https://msdn.microsoft.com/en-us/library/office/ee691831%28v=office.14%29.aspx

I made a change which seems to work.  at least I don't get the error anymore but I've not run it for real yet.

Changed
Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As Long)
to
#If VBA7 Then
    Private Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As LongPtr) 'For 64 Bit Systems
#Else
    Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds as Long) 'For 32 Bit Systems
#End If

--- End quote ---

Thanks a lot for the feedback. I used a 32bits version of Office 2010 and you are right , the declaration of "Sleep" which I used in the scripts have to be modified to work on both 32/64 bits versions. In fact we have to use the "Win64" compilation constant rather than the "VBA7" compilation constant (wich will always be true in Office 2010),  otherwise the modification will only work on office 64bits:
 
#If Win64 Then
    Private Declare PtrSafe Sub Sleep Lib "kernel32" (ByVal dwMilliseconds As LongPtr) 'For 64 Bit Systems
#Else
    Private Declare Sub Sleep Lib "kernel32" (ByVal dwMilliseconds as Long) 'For 32 Bit Systems
#End If
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod