Methods for Testing the Setup/Configuration

In order to perform a thorough test of the Valisys mode functionality, it is necessary to actually have a Valisys host system connected with a Valisys program prepared that can be executed. The configuration of a Valisys host, as well as how to create and execute a Valisys program is beyond the scope of this document.

However, it is fairly easy to use readily existing utilities to do a simple test by manually typing a few of the Valisys commands. That is enough to verify whether or not the INI settings have been input properly and that a connection is possible.

Serial Port Case

When connecting via a serial port you can use Hyperterminal or any similar terminal emulator program on a laptop or any other available computer to simulate the Valisys host. If the PC-DMIS system has an extra unused comm port, you can even run the terminal emulator on the same system by cabling the two ports together. The baud rate, parity, etc. for the port must be set in the terminal emulator to match those listed in the previous section.

TCP/IP Case

When connecting via TCP/IP you can use Telnet to connect by specifying the port number used in the configuration. You can run Telnet on another computer on the network or on the PC-DMIS system itself.

Regardless of which of the above utilities you use you then just type a command and hit RETURN and wait for the response. PC-DMIS does not echo the individual characters of a command back to the sending system so if you want to see what you are typing you will need to enable local echo in the utility you are using.

The general sequence you would use for a test is:

  1. Issue the command to establish a Valisys mode connection.

  2. Send the units command to specify what units you want for the commands/responses.

  3. Issue other commands as desired to test specific functionality.

  4. Issue the command to disconnect and terminate the Valisys mode connection.

A subset of the available Valisys commands is listed in the following section along with the expected responses.

NOTE 1: Before you can send commands, you must open a part program in PC-DMIS. Generally, it’s best to use a minimal program that has virtually nothing in it but the default commands from a new part creation. However, note that when using PC-DMIS V2.x you should have either MODE/MANUAL or MODE/DCC as the last statement in the program.

NOTE 2: As soon as you issue the connection request (CH command) PC-DMIS should go into execute mode and remain there until you disconnect (CF command). During that time the regular PC-DMIS execution dialog is displayed. If you send the connection request and the execute dialog does not appear then PC-DMIS did not receive and process the request and it indicates there is probably something wrong in the setup/configuration. That might mean a problem with INI settings or for a serial port, it could also mean port setup and/or cabling problems. When using TCP/IP is could also mean general network connectivity problems between the two systems.