1
Test Equipment / Re: SDS800X HD Wanted Features
« Last post by electronics hobbyist on Today at 10:34:13 am »Feature request 1: bit rate measurement, please!
This is good feature, will added to wanted feature No.36.
Feature request 1: bit rate measurement, please!
I mean in the US and the power grid infrastructure, not local housing electric supplies. I'm trying to find whatever possible attack vectors someone could have if they were connected to the main power grid. Because of all the suspicious windmill connections in areas you wouldn't expect anyone to build windmills in... Gives you the question if they have some kind of attack vector by doing that.
No, it does not give me that question.
You mean "they" are building windmills because they want to eavesdrop on you? I can put your mind at ease there; no functionality for that "attack vector" is built in. But don't tell anybody: "They" have installed secret switches where they can turn all the windmills into huge fans and cause massive storms in your area!
The "power grid" is nothing more or less than the high voltage, medium voltage, and low voltage power lines that carry the electric power from the machinery that generates it to the point of use (homes and businesses). 60 Hz in the US and 50 Hz in many other places.
Now, the power companies do need to have communication equipment to monitor the state of that grid and to control the various elements (generators, switches, etc.) I would suspect that they use multiple means of communication: microwave, satellite, plain old radio, probably even land (telephone) lines. But, of course even the telephone lines use things like microwave and satellite for long, cross country connections.
But, another thing that I am fairly sure is done is to transmit digital data using those very power transmission lines that form the power grid, or at least parts of it. When I drive under the some local semi-HV power lines my AM radio picks up a lot of static that sounds a lot like digital chatter to me. So the logical conclusion is that those power lines are also carrying digital communication signals that are piggy-backed on the 60 Hz, AC power. This superimposed data signal is probably carrying the monitoring and control signals that the power company uses, as I mentioned above.
Thus, I think that there is no simple answer to the OP's question.
As far as attack vectors, that would be tricky. I mean, these digital signals would not pass through AC transformers very easily. They would need to be stripped of the 60/50 Hz power on one side of the transformer and re-inserted on the other. If the power company had not provided that path, then the first transformer that any malicious hacker's connection encountered would be a dead end. So one could not just connect to a household or business power connection (230 VAC) and expect to receive, alter, and re-transmit those monitoring or control signals.
A hacker would be far more likely to interfere with the control of the power grid by hacking into any internet connections that the power companies are using. One can only hope their engineers are wise enough to guard against any such intrusion. And do consider the fact that the power lines that carry that power for any appreciable distance (like over a kilometer) are virtually all high voltage lines. A hacker attempting to make a connection to them would need a fair amount of equipment to do so. Things like an insulated bucket truck and the equipment that makes the connection would need to be designed for those high voltages. And, of course, the training to properly use them.
Of course anything is possible where technology is involved. Just ask the Germans or Japanese officials who thought their WWII codes were completely secure. I am sure there are malevolent people who are trying to find the weak points in these systems for possible use when they wish.
Good suggestion for the entire platform range and one I believe could be accomplished quite simply by adding a menu View (type) option in the Decode List comprising of a Bytes or Frames choice, Bytes being the current list default view.
Just unboxed my new scope and getting to grips with it - apologies if this is just a setting which can be changed somewhere, but it seems unintuitive and a limitation...
I'm probing a CAN signal - actually one of the training outputs from my MSOX3104A - and before I can decode it, I need to know the bit rate.
I couldn't find an automated measurement that gives this quickly and easily. IIRC it was added in firmware after release on the Agilent, and it's handy. I think it just measures the minimum observed pulse width (either positive or negative) within the captured data.
Feature request 1: bit rate measurement, please!
In the absence of an automatic measurement, I figured I'd just do it the old-fashioned way. Capture a packet, find the narrowest pulse and assume it's 1 bit wide. Then, put the cursors on the edges as accurately as possible, and measure their separation.
The odd behaviour is that the delta-X measurement on screen doesn't show the distance between the cursors if one of them is off screen; instead, it 'clips' to the edge of the screen, and if both are off screen then it just reports the width of the screen, or zero if both cursors are off to the same side.
That's really misleading. It clearly remembers the correct cursor positions if they're pushed off screen, because they come back to the right place if I adjust the time base to bring them back.
If I were feeling unkind, I'd call this a bug, though it's clearly intentional behaviour. I just can't think of any circumstances when I'd want to measure between a cursor and the edge of the display, as opposed to between the two cursors.
Feature request 2: delta-X time measurement actually measures the time between X1 and X2 even if one or both of them is off screen - not between a visible cursor and the edge of the screen.
(Example photos: both cursors on screen, showing delta-X = 8.01us, and the effect of just speeding up the time base 1 click; this pushes X1 off the left side of the screen, and the delta-X readout becomes 6.77us which is effectively meaningless).
I thought that photo was from your real scope?Sorry if I've not been clear on that point.
Try to uninstall all options first, wait for reboot, then install with regen private key flag.
I tried as described, first uninstalled and after reboot I installed with regen private key. Tried it several times but the oscilloscope only replies with "remaining attempts" as described by zauberpilz, now only 2 attempts left. What am I doing wrong? Could you please help?