Reports 1-1 of 1 Clear search Modify search
AdV-SBE (MultiSAS for end benches commissioning)
bulten - 21:03 Friday 31 July 2020 (49152) Print this report
SDB2 thermal transient test, stepper motors not reachable
As result of the thermal transient test this week performed by Michal Was, the GAS blades of filter-1 of SBE_SDB2 are currently heating up. I expect that during the night, the actuators will clip. Therefore, I attempted to adjust the fishing rods (as I did 3 times this week already). However, in olwin, with the TMCL application, I cannot get access to COM port 2. I tried logging in and out, restarting the program, etc, but I cannot get it to work. The message is that the port may be locked by another process, the port manager in windows may be configured wrongly, or something else may be the matter (maybe some bridge is switched off?). I could not solve this so I opened the loop for SBE_SDB2; this means that the bench position may move down several mm this night.
Comments to this report:
fcarbogn - 21:39 Saturday 01 August 2020 (49156) Print this report

As detailed in this ently:

https://logbook.virgo-gw.eu/virgo/?r=32859

the communication to the motor controller is realized via a Moxa NPort 5130A Ethernet/Serial RS485 bridge.

In case of problem like the one reported, the very first thing to check is the status of the bridge by simply tring to ping it.

Since the communication with the bridge is not possible:

fcarbogn@olserver111[~/experience]: ping ethsdb201
PING ethsdb201.virgo.infn.it (192.168.226.40) 56(84) bytes of data.
^C
--- ethsdb201.virgo.infn.it ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 8999ms

I suspect that the motor electronic, including the bridge, hosted in the DET ELab is switched off

bertolini, carbognani, tacca - 12:46 Monday 03 August 2020 (49164) Print this report

We made further tests without success. At the end, we went in the DET-EEroom and we discovered that the ethernet cable has been left unplugged at the end of Friday's activities. Rplugging the cable solved the problem. We made another test and the motors are now reachable.

Search Help
×

Warning

×