spec - Local Sector 7 web page

Please note, many users have had problems establishing initial communicationbetween the MCU-2 controllers and their computers. The problem is almost alwaysrelated to the cable. Standard RS-232C cables do not appear to work. Acustomcable wired according to the diagram in the MCU-2 manual seems to be needed.Note also, that the connections for pins 2 and 3 may need to be swapped from what isshown in the manual. Be prepared to try the cable both ways before adding the finaltouches.Command pass through for the MCU-2 controllers is available using the following:motor_par(motor, "send", cmd) — Sends the string cmd to the MCU channel associatedwith motor . For example, set cmd to "J500" to set the jog rate for motorto 500 steps per second.motor_par(motor, "read", cmd) — Sends the string cmd to the MCU channel associatedwith motor ,asabove, and returns a string containing the response.Compumotor 3000 (GPIB and Serial)config file:RS_CM3000 = device_name baud_rate number_of_motorsGP_CM3000 = gpib_address number_of_motorsedconf devices screen:MOTORS DEVICE ADDR MODE NUM TYPEYES /dev/tty00 9600 4 Compumotor 3000 (Serial)YES 6 4 Compumotor 3000 (GPIB)Use of this old motor controller is not recommended!Compumotor 4000 (GPIB and Serial)config file:RS1_CM4000 = device_name baud_rate number_of_motorsRS2_CM4000 = device_name baud_rate number_of_motorsGP_CM4000 = gpib_address number_of_motorsedconf devices screen:MOTORS DEVICE ADDR MODE NUM TYPEYES /dev/tty00 9600 4 Compumotor 4000 (Serial port 1)YES /dev/tty00 9600 4 Compumotor 4000 (Serial port 2)YES 3 4 Compumotor 4000 (GPIB)The Compumotor 4000 can be used on either an RS-232 or GPIB interface. Youmustprogram the RS-232 baud rate or the GPIB address using the Compumotor front230 HARDWARE REFERENCE INTERIM WORK-IN-PROGRESS (8/16/01) NOT FOR GENERAL DISTRIBUTION