DMDX Help.

Remote Monitoring
    DMDX allows you to monitor it's progress on a remote machine connected to it with a network interface. Although the TCP/IP protocol is used conceivably allowing the remote machine to be anywhere on the internet it is expected to be found locally as the network code does not elegantly deal with lost connections (it's going to spend a long damn time waiting till the connection times out).  If you do intend to test on machines beyond the local network see the remote testing section.  Information on setting up the remote machine and the Monitor program can be found in TimeDX's help file.

    If you have setup a remote monitoring machine running the Monitor program DMDX (currently) will connect to it when it is first run -- not at the beginning of a particular run of an item file. If you have not got Monitor running when you start DMDX you will be given the opportunity to retry the connection (assuming you go and start Monitor on the remote machine). If you cancel the connection DMDX will not attempt to re-establish a connection until DMDX is run again; DMDX will function normally unless you were using the remote Monitor for Naming Task Negation (in which case it will use the local machine's display and keyboard).

    Using the remote monitor changes the way several things work in DMDX:

Naming Task NegationAll naming task negation prompts will be sent to the remote machine and not presented on the local machine at all.
Bells For version 1.2.00 and onwards. When using the remote monitor all bells that DMDX would normally sound are sent to the remote monitor as well as to the local machine (the local bell won't sound however if acoustic stimuli have been used).
Experimenter SignalingBoth Acoustic and Visual experimenter signaling is sent to the remote machine as well.

DMDX Index.