Same on my unit which doesn't need the pins to be tied together - went back to 01.09 and normalise works as it should.
Thank you for the confirmation!
I upgraded mine to 1.12 yesterday :-( does anyone can share the 1.09 .sys file ?
Can I downgrade to 1.09 just by providing the 1.09.sys file through the USB port and perfrom an "update" with this file ?
Does anyone know if downgrad to 1.06 will allow the keygen to work ?
thanks
Yes, you can downgrade from 1.12 to 1.09. Although I had tried 1.12 before, there was no additional benefit for me so I'd already gone back down to 1.09 and that supports -30dBm TG on the version of hardware here (not all DSA815s support -30dBm).
I don't know about downgrading to 1.06: I tried downgrading to 1.08 but it wouldn't work, there is a newer bootloader (1.04) on my hardware that didn't like 1.08.
PM sent regarding firmware.
Thanks a lot, at least will downgrade back to 1.09
I have the same boot loader as you, So I can forget the keygen. I still have few days to see If I try your "Pin" solution
Another thing I noticed using FW 00.01.012 was that the SA always powered itself on immediately it was connected to mains (without the use of it's ON button.) I only noticed this as I tend to disconnect
my test instruments from the mains at the end of the day using remote mains plugs. Once mains was applied the next day the SA would power itself up.
Using FW 00.01.09 it doesn't do this and has to be started as it should (via it's ON button) Even if mains is introduced via the remote switch.
Orbiter
i noticed the SAME THING with my dsa regarding powering on, I thought it was some setting that i had to select, but it sounds like it is a fw bug.
Isn't there a menu setting that sets what the power up/down functions do??
Isn't there a menu setting that sets what the power up/down functions do??
Nope. This is an issue that occurs as soon as mains is applied using FW 00.01.12 and the unit coming on even without pressing anything.
Interesting, my 00.04 board version 815TG with 1.12 doesn't have this issue. Tried it a few times, doesn't power up when mains is applied.
Jeff
Ok... Contacted Rigol who got back to me today. They have kindly sent the report regarding Normalization off to R&D for investigation. Basically it could well still be a FW bug, however the Application Engineer who contacted me told me that he had confirmed the steps we're taking to recreate the issue (Store Ref > Normalize) and that Normalization indeed didn't work.
HOWEVER (and I have done this AFTER reinstalling FW 00.01.12 again) .. It seems that as suggested by the App Engineer... If you set NormRefPos 1% up and back down to the original setting 0% again the Normalization can be switched on".
I've also basically checked that as long as you initially change ANY value within either the NormRefLvl OR NormalRefPos settings, BEFORE hitting Normalise, then Normalization will work.
What is the purpose of Storing The Reference Trace? I know what is does, but why would we want to do it when using the Tracking Generator? Why would I care what the trace looked like before Normalization? And you certainly don't need to press 'Stor Ref' before dong a Normalize. I have never done the Store Reference prior to a Normalize after initially seeing what it did. So I wouldn't have even known about this Bug (?) without reading about it here in this thread about the 00.01.12 Firmware glitches. And some people have gone back to 00.01.09 to have this function. Why?
Can someone please tell me what I have been missing by NOT Storing a Reference Trace?
I don't think there's any need, like sheep we just follow what Dave does.
Baaaaah, baah.
I don't think there's any need, like sheep we just follow what Dave does.
Baaaaah, baah.
LOL, I've never bothered with it either. Only useful thing I could is to display it for reference, it doesn't nothing for the actual process that I can see.
Jeff
What is the purpose of Storing The Reference Trace? I know what is does, but why would we want to do it when using the Tracking Generator? Why would I care what the trace looked like before Normalization? And you certainly don't need to press 'Stor Ref' before dong a Normalize. I have never done the Store Reference prior to a Normalize after initially seeing what it did. So I wouldn't have even known about this Bug (?) without reading about it here in this thread about the 00.01.12 Firmware glitches. And some people have gone back to 00.01.09 to have this function. Why?
Can someone please tell me what I have been missing by NOT Storing a Reference Trace?
Wouldn't it be handy say for someone else to see, if you were sending the trace data elsewhere for comparison measurements?
I don't think there's any need, like sheep we just follow what Dave does.
Baaaaah, baah.
I realize that I was potentially setting myself up for embarrassment if I'm missing something basic here. Although I use the Tracking Generator a lot and have never seen a use for storing the reference. Then also, you would think that Rigol must have had something in mind for it because it is listed in the User Guide as something that
can be done before Normalization(?).
And of course storing the reference can be, and is, very useful for many of the other SA measurements.
One thing that Dave doesn't do that I feel he should, is do a Normalize again after he changes the Start, Stop, or Span Frequencies.
Interesting, my 00.04 board version 815TG with 1.12 doesn't have this issue. Tried it a few times, doesn't power up when mains is applied.
Jeff
Could it be with 220VAC the issue is there and with 110VAC (US) everything is OK?
Bah
Interesting, my 00.04 board version 815TG with 1.12 doesn't have this issue. Tried it a few times, doesn't power up when mains is applied.
Jeff
Could it be with 220VAC the issue is there and with 110VAC (US) everything is OK?
Bah
Yah, I'm running the 110-120v version. Didn't even see if it supports 220-240, if it does guess I could step it up and try.
Jeff
As far as the DSA815/TG powering up right away when plugged into a 120VAC outlet, etc goes: This is a problem with a lot of DSA8115 users, and this appeared for most all before upgrading to firmware 00.01.12. It doesn't seem to matter if it is used on 120 or 220 VAC. If it is happens on 220VAC, it is also an issue with 10VAC.
mine is 220 v powered and I was having the same bug, thi is why I downgraded to 1.09
mine is 220 v powered and I was having the same bug, thi is why I downgraded to 1.09
We need a 110vac user reporting the issue to throw away my theory. Anyway I don't think it is related to the main suppy voltage in the new FW 1.12 units, it is more curiosity. In God we trust, the others bring data please.
Hello,
I have no problem with switching on and Firmware 1.12, here 230 V.
Have you checked the settings for the power button?
Peter
Hello Peter:
My DSA815 was configured with Front Switch 'On', and I had the problem with it automatically coming on when 120VAC was initially applied.Solution: I
set the Front Switch to 'Off' and
then recycled the power (Off/On). Then
set the Front Switch setting back to 'On'. I also re-selected Factory Default, although I doubt now that this was required.
And now it is Ok again and does NOT come on anymore when 120VAC is applied to the DSA.When I first saw this issue quit some time ago I checked the Front Switch setting and it was '
On', so I just assumed - OK that's not the issue. Thank you Perter for indirectly encouraging me to re-visit this setting and playing with it. So yes it is some sort of bug alright, just apparently not part of any specific firmware version. Ted
Edit: To highlight more of the process/issue. And also to report that I have had
other DSA users tell me that doing this also corrected their DSA automatic power On issues.
Hello all, is my 815 the only one where the TG power sweep function is out to lunch ?
same with 1.09 & 1.12
Was messing around one day and decided to check the stability of the tracking gen of the 815 to be used as a signal source and thought I would share my findings. Using my Flex 5000A that was locked to a double oven source like the 010 option that are used in some of the HP freq counters. Using the PC's sound card I offset the receive frequency by 1Khz to receive WWV's carrier but using WWV this way is useless because of the Doppler effect caused by the ionosphere and maybe some cows jumping over the moon?
I did not calibrate the sound card and the ref osc. I just ball parked since I have no real reference source.
Well, thats my 2 bits worth !