I returned mime and got a full refund rather than mucking around and using another signal generator to produce sync square waves.
I can understand this, no telling how long it will take for a bug fix, although Siglent were quite quick fixing the log sweep bug a few years ago
I have to correct my previous comment on the Sync output working at 20MHz on sweep, there is a pulse at the start of the sweep only its at the low level of 30mV (I forgot I had the 10x on the scope) . Once you go above 2MHz with the Sync output on there is a warning message on the screen and the Sync output is disabled (not completely as it still `leaks` out at 30mV)
From the manual (For the SDG1000 and SDG800)
“For non-modulated waveform, the Sync Signal reference is the carrier.”
This works up to 2MHz, as per spec. (it actually is still outputting a 30mV pulse correctly up to 3.9MHz after that it gets a bit random)
“For internal modulating AM, FM and PM, the Sync signal reference is the modulated signal (not the carrier signal).”
Again this works only when the carrier is below 2MHz, although the output is still there in its disabled state reduced to 30mV. This a obviously a bug
“For ASK and FSK, the Sync Signal Reference is the keying Frequency.”
Same as above
“For a Sweep, when the sweep starts, the Sync Signal becomes TTL Level High. The Sync frequency equals the specific Sweep time.”
This one we know about
“For the Burst, when the burst starts, the Sync Signal is Level High.”
Again limited to 2MHz, in Ncyle the Sync pulse is at the 50% point between the bursts, in Gated its at the start of the burst.
“For the External Gated Burst, the Sync Signal follows the External Gated Signal.”
Nope, it stays with the internal signal
I can only assume theses are rarely used functions, especially by me
as I have not seen these problems reported before, but if you need them or bought the generator after reading the spec / manual specifically needing this functionality I can see how this would be an issue