RE: Delta Tau issue

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

Hi Giles,

 

Thanks for that info, the PMAC Python GUI is very useful.

 

This is what I see with it:

 

 

 

So the “Any Memory Checksum Error” bit it set.  I typed the “clrf” command, but that did not clear it.

 

The system is at the University of Chicago and I am at the APS, so I can’t power-cycle it.  But the next time one of us is there we will try that.

 

Any suggestion on how to get more information on what checksum is in error?

 

Thanks,

Mark

 

From: Knap, Giles (DLSLtd,RAL,LSCI) <giles.knap at diamond.ac.uk>
Sent: Tuesday, July 26, 2022 4:06 AM
To: Mark Rivers <rivers at cars.uchicago.edu>; Andy Foster <ajf at observatorysciences.co.uk>
Cc: tech-talk <tech-talk at aps.anl.gov>
Subject: Re: Delta Tau issue

 

I just noticed that the instructions fail to say that you can install and run with:

 

• activate a python virtual env
• pip install dls-pmaccontrol
• dls-pmac-control

---

From: Knap, Giles (DLSLtd,RAL,LSCI) <giles.knap at diamond.ac.uk>
Sent: 26 July 2022 10:02
To: Mark Rivers <rivers at cars.uchicago.edu>; Andy Foster <ajf at observatorysciences.co.uk>
Cc: tech-talk <tech-talk at aps.anl.gov>
Subject: Re: Delta Tau issue

 

Mark,

 

You may also find that this command will clear the error.

 

clrf

 

(Which means clear fault)

 

For a GUI tool that lets you send arbitrary commands and also shows the status bits see https://dls-controls.github.io/dls-pmac-control

---

From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Andy Foster via Tech-talk <tech-talk at aps.anl.gov>
Sent: 25 July 2022 22:43
To: Mark Rivers <rivers at cars.uchicago.edu>
Cc: tech-talk <tech-talk at aps.anl.gov>
Subject: Re: Delta Tau issue

 

Hi Mark,

 

My understanding of this is that a checksum error has occurred in downloading a program such as a PLC or motion program to the PMAC user buffer space. I think it can also be caused by a download of the firmware, but since you don't do that very often, if ever, unlikely to be that.

 

In my experience, it needs a power cycle of the logic power to clear that bit.

 

Cheers, Andy

 

On Mon, 25 Jul 2022, 21:25 Mark Rivers via Tech-talk, <tech-talk at aps.anl.gov> wrote:

Folks,

 

I have a Delta Tau GeoBrick 8-channel system.  I have been using it with the Model 2 driver (not based on asynMotorDriver) in the tpmac repository: https://github.com/epics-modules/tpmacc.  I had not seen any errors with that driver.

 

I have just updated it to use the Model 3 driver (based on asynMotorDriver) in the pmac repository: https://github.com/dls-controls/pmac

 

The motors seem to be driving OK.  However, the OPI screens show a Controller Error, and the poller prints this message:

 

2022/07/25 15:10:09.937 pmacController::fastUpdate *** Hardware Problem *** global status [???] => 8400913

 

The controller error is generated if this _expression_ is non-zero:

const epicsUInt32 pmacController::PMAC_HARDWARE_PROB = (PMAC_GSTATUS_REALTIME_INTR |

                                                        PMAC_GSTATUS_FLASH_ERROR |

                                                        PMAC_GSTATUS_DPRAM_ERROR |

                                                        PMAC_GSTATUS_CKSUM_ERROR |

                                                        PMAC_GSTATUS_WATCHDOG |

                                                        PMAC_GSTATUS_SERVO_ERROR);

 

 

That Global Status value 8400913 in hex is 0x803011.  This translates to the following status bits being set:

 

Bit	Symbolic constant	Problem bit in PMAC_HARDWARE_PROB?
0x1	PMAC_GSTATUS_CARD_ADDR	No
0x10	PMAC_GSTATUS_MACRO_RING_ERRORCHECK	No
0x1000	PMAC_GSTATUS_CKSUM_ACTIVE	No
0x2000	PMAC_GSTATUS_CKSUM_ERROR	Yes
0x800000	PMAC_GSTATUS_RESERVED3	No

 

So it appears that the Controller Error on the OPI screen and the error message being printed is because the PMAC_GSTATUS_CKSUM_ERROR bit is set.

 

Does anyone know what that bit means, and why it might be set?

 

Thanks,

Mark

 

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom