M1 Logo M1 Oscilloscope Tools™: Client/Server

  • Connect the M1 OT installation loaded on your oscilloscope in a remote location to your M1 OT on your PC in your Office
  • Get out of the lab so you can think clearly about the data that M1 OT provides you
  • Collaborate and exchange ideas across geographic office locations
  • Get your vendors and your customers working on the same page as you are

M1 Oscilloscope Tools™ and M1 Reader™ now have the ability to talk to a second M1 Oscilloscope Tools™ setup that resides on an oscilloscope in another location. This enables the user to collect live data acquisitions on the remote scope and have them sent to the local PC for analysis, allowing the user to be free from the requirement that they must be sitting in front of the oscilloscope in order to analyze and explore waveforms.

This ability is available so long as both M1 licenses can be accessed over a network. While controlling a remote installation of M1 (the “Server”), the local M1 (or “Client”) has access to whatever oscilloscope the Server controls. The scope data is transferred over the network to the Client, where all normally available M1 functionality can be performed on the data -- as if the Client had performed the acquisition itself. The user of the Client will see nothing different about M1's operation after he has connected to the Server, except that acquisitions may be perceived as slower due to the additional time needed to transmit the data over the network.

To make the connection between a local M1 Client and a remotely located M1 Server on an oscilloscope, the M1 setup at both the Client end and the Server end must be connected to a network with a distinct IP address and no firewalls or routers between them. Each M1 must have the appropriate M1 Client and/or M1 Server option enabled. The M1 Server option must be enabled on an M1 OT that is licensed to a specific scope serial number, and the M1 Client option must be enabled on the M1 that will be used as the remote Client.

Multiple Clients can connect to a Server at one time, though additional Clients will eventually start to cause acquisition delays. There are also limitations as to how many different IP addresses of M1 Clients are allowed to connect to one M1 Server.

What does a connection mean?

When connected, the M1 Client will maintain a TCP/IP connection to the M1 Server. When this connection is first established, the Client will get a local copy of the Server’s scope information. This will include trigger information as well as acquisition data. As long as the connection is active, any attempt to make a live acquisition with the Client will cause a command to be sent over the remote connection. The M1 Server will perform an acquisition without doing any analysis, and return the new data to the Client. The M1 Client will then perform the requested analyses using that data. The Client will see no difference in operation versus being directly at the scope, except a small reduction in throughput due to the overhead required to package, transmit, and unpackage the acquisition data. If the M1 Server is not connected to an oscilloscope, or does not have a license that lets it use an oscilloscope, then the connection will have no effect.