[INSTRM-67] Not detecting powered-down motor controller from PCM RS-485 traffic. Created: 07/Jan/17  Updated: 02/Feb/17  Resolved: 02/Feb/17

Status: Done
Project: Instrument control development
Component/s: ics_xcu_pcm
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major
Reporter: cloomis Assignee: shope
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to INSTRM-88 PCM returns last response to command ... Done

 Description   

The CCD motor controller is on an RS-485 bus off the PCM. When the motor controller is powered down it returns something that the xcuActor does not recognize. We need to parse and handle it.

ics_xcuActor 1.5.1, FWIW.

To wit:

pfs@bee-r1:~$ oneCmd.py xcu_r1 --level=d motors status
xcu_r1 d text="sending '~@,T2500,/1aM1R'"
xcu_r1 d text="received '0011074006570014036'"
xcu_r1 f text="command failed: RuntimeError('command response header is wrong: 0011074006570014036',) at /home/hostpfs/mhs/products/Linux64/ics_xcuActor/1.5.1/python/xcuActor/Controllers/PCM.py:96"

 Comments   
Comment by cloomis [ 01/Feb/17 ]

A variant of this just occurred, and might clarify the issue. No matter which motor command was sent, the powered-down "controller" always responded with '\0`0', which is the response from a successful motor controller command.

The suspicion is that the PCM (behind which the motor controller RS-485 bus lies) is returning the last response from the device. With that in mind I associated the ics_xcu_pcm component and am passing the ticket to Steve H.

Comment by cloomis [ 02/Feb/17 ]

INSTRM-88 will fix this.

Comment by cloomis [ 02/Feb/17 ]

Not an XCU issue; fixed by INSTRM-88

Generated at Sat Feb 10 16:21:10 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.