Is it possible do external trigger with this 4 ch rigol?
Just to make shure if i understood this..., if i just need from channel 1-3 to show signal, i still have the channel 4 as a tigger source (in this case, turned into a external trigger)?
As i´m returning to electronics world, planning to buy a RIGOL, need study more, instead of make silly questions again.
A terrific feature, now that these oscilloscopes include an Ethernet interface, would be NTP synchronization, so that captures would be accurately timestamped.
That's so much better than a RTC, having the correct time within several milliseconds.
A terrific feature, now that these oscilloscopes include an Ethernet interface, would be NTP synchronization, so that captures would be accurately timestamped.
That's so much better than a RTC, having the correct time within several milliseconds.
A terrific feature, now that these oscilloscopes include an Ethernet interface, would be NTP synchronization, so that captures would be accurately timestamped.
That's so much better than a RTC, having the correct time within several milliseconds.
I would never connect a commercial test/measuring instrument to the internet, not even via a firewall.
Test/measuring instruments are not designed with security in mind.
I would never connect a commercial test/measuring instrument to the internet, not even via a firewall.
Test/measuring instruments are not designed with security in mind.
I know, but you can do it safely if you are behind a NAT router.
I would never connect a commercial test/measuring instrument to the internet, not even via a firewall.
Test/measuring instruments are not designed with security in mind.
Agreed.I know, but you can do it safely if you are behind a NAT router.
To each his own. Routers get hacked too, especially consumer-grade ones with shoddy manufacturer firmware.
NTP usually just syncs the time and then uses an RTC to keep the time so it's not going to be that accurate anyhow, plus do you want to burden the already overworked processors and slow the scope down slightly more? I don't see a big gain on this since it can't be precise enough to sync say two pieces of test equipment to the point that the data will align perfectly.
Maybe you'll be able to sync them to +- 10ms, what will that give you?
Take into account that the time kept after sync depends on the scopes internal timing and two crystals will alias from each other because they are just not going to be at the same exact frequency and there is little you can do to compensate for that. And syncing for better than 1ms, forget about it without additional hardware and/or software if for example you could use the CPU instruction counter but that will drift with temperature or uptime.
The ablity to determine which of a flood of debugging messages can correlate to, for example, an anomaly detected on a power line.
I stand by NTP not being too useful for a DS1054Z, as for being done properly and not needing "time after sync" do you care to elaborate?
Maybe you should read this:
http://www.ntp.org/ntpfaq/NTP-s-algo.htm
I could see some benefit for nanosecond synchronization but the hardware needed would be cost prohibited for entry level scopes.
NTP isn't rocket science and it's widely implemented (and works just fine under Windows, not sure where that came from). It's the bog-standard interface for network time delivery. If there was going to be some sort of time synchronization it seems silly to use anything else.
NTP isn't rocket science and it's widely implemented (and works just fine under Windows, not sure where that came from). It's the bog-standard interface for network time delivery. If there was going to be some sort of time synchronization it seems silly to use anything else.Microsoft claims that their implementation does not support synchronization to a precision of one or two seconds, what they call high accuracy environments.
https://support.microsoft.com/en-us/kb/939322
This certainly reflects what I've seen in the WSJT mailing lists, where people seem to be solving puzzles in order to keep an accurate time on Windows. Otherwise, why would anyone recommend a third party time synchronization program?
It's not really a claim, more a statement of fact by the software provider,
Calibration date sheet (certificate of calibration): 25-dec-2015 ....(working at xmas???)
Att
Calibration date sheet (certificate of calibration): 25-dec-2015 ....(working at xmas???)
Att
Christmas isn't a holiday in China.
McBryce.