M1 Client/Server Details

To make the connection between M1 Client and M1 Server, M1 Server must be connected to an oscilloscope or digitizer. Both M1 Client and M1 Server must be connected to a network, with a distinct IP address for each and no firewalls or routers between them. Each must have the appropriate M1 Client and/or M1 Server option enabled. Only M1 Waveform Tools™ can function as an M1 Server. Any version of M1 can function as an M1 Client.

To establish the connections, the M1 Server must be placed into server mode. Any number of M1 Clients may then connect to the M1 Server, though additional connections can cause slower acquisitions and conflicting settings. All M1 Clients must enter the IP address of the M1 Server; the M1 Server displays the IP address of its machine to facilitate this.

The M1 Server can either accept all IP addresses as clients, or the user can specify what IP addresses to accept or what IP addresses to ignore.

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 data. The scope data includes trigger information as well as acquisition data. As long as the connection is active, the M1 Client can perform a live acquisition as if it were connected directly to the scope being controlled by M1 Server. M1 Server performs an acquisition without doing any analysis, and returns the new data to the Client. M1 Client then performs the requested analysis using that data. The M1 Client user sees no difference in operation versus being directly at the scope, except for a small reduction in throughput due to the overhead required to package, transmit, and unpackage the acquisition data over the network.