In the past days we made some tests in order to check the communication between the computer and the picomotor controller.
Details on the picomotors drivers can be found in the user's manual at this link:
http://164.54.212.3/control_systems_manuals/87XX_Manual_RevC.pdf
We followed the instructions to configure the ethernet connection at page 48/50 of the manual but we didn't succeed in setting the communication.
We did the following steps:
1) Connect a PC to the serial port and send a IPADDR MCL command to get the IP address of the controller. For the controller named NM2 we got the IP 10.68.10.241.
2) Connect the controller and the computer to the same ethernet network in TAMA and try to ping the drivers from the pc without success.
3) Since we are convinced that the IP we got is not the good one to connect to TAMA newtwork ( all the other adresses are of the form 133.40.XXX.XX) we tried to ask the IP adress (again by using serial port) after having connected the drivers to the ethernet but we got the same answer.
We probably need the advice of a TAMA network expert in order to fix the problem.
I found that NAOJ network uses DNS, so I follow the instructions of "Ethernet Configuration Example 2" at page 50 of the manual. (last time we tried Example 1 and, apparently, it didn't work because of DNS).
Through serial port, the IPADDR command returns 192.168.11.121 for one controller and 10.68.10.241 for the controller labeled NM2.
I connect the controller with IP address 192.168.11.121.
HOSTNAME command returns: nf8752-295333
I change the hostname with the command HOSTNAME NF8752-001
Save the configuration with the SAV command
RESET
Try to ping NF8752-001, failed (it says: "Ping request could not find host NF8752-001")
following Takahashi-san's advice I connected PC, controller and network cable to the same Ethernet hub. The ping still fails. BUT if I unplug the nework cable, which means I isolate my system from NAOJ network, then I get this ping returns:
Pinging 10.68.10.241 with 32 bytes of data:
Reply from 133.40.117.65: Destination host unreachable.
Reply from 133.40.117.65: Destination host unreachable.
Reply from 133.40.117.65: Destination host unreachable.
Reply from 133.40.117.65: Destination host unreachable.
Ping statistics for 10.68.10.241:
Packets: Sent = 4, Recieved = 4, Lost = 0 (0% loss),
In the case of 192.168.11.121-IP controller the ping still fails, even in the isolated case.