Experimental Physics and
Industrial Control System

"Shepherd, EL \(Emma\)" <[email protected]> · Mon, 11 Jun 2007 17:47:03 +0100

Hi Ron,

Thanks - I'm glad to hear someone is maintaining it :)

> CVS version 1.1.1.1.2.6 of drvIK320.c is the latest EPICS 
> R3.13.x version of the IK320 driver.
I'm actually running EPICS 3.14.8.2, I believe someone here ported the
3.13 version of IK320 last year and presumably never checked for your
updates.  Should the latest version R2-4-4 work under 3.14.8.2?  If so I
might as well download it and try it out.  But that at least explains
why my PVs can be so long.

> One question; is the VME CPU board a PPC or 68K?
It's a PPC (MVME5500).

> One suggestion; turn on driver diagnostics by setting 
> drvIK320Debug=2 at the IOC shell and send me the results.
I had already set this to 1 so I don't get much more output than before.
Here are the results from attempting to put an encoder into reference
mode:

BL06I-MO-IOC-02 -> filename="../drvIK320.c" line number=959
drvIK320: reference; set irq mask...
status = (1033,10) not in symbol table PV: BL06I-OP-PGM-01:MIR:ENC1:FUNC
ik320WriteFunct()

I actually made a mistake when interpreting the error codes in my
previous mail.  It seems that it is really a timeout caused by the call:

semTake(drv->sync,1)

This is line 962 in my version of the code.  I tried printing out the
semaphores afterwards (adding a printf on drv->sync to get the memory
locations and then doing semShow from the console on each one) but all
of them have zero counts:

BL06I-MO-IOC-02 -> semShow 0x1eaed490

Semaphore Id        : 0x1eaed490
Semaphore Type      : COUNTING
Task Queuing        : FIFO
Pended Tasks        : 0
Count               : 0
Options             : 0x0       SEM_Q_FIFO

Thanks for your help,

Emma

> -----Original Message-----
> From: Ronald L. Sluiter [mailto:[email protected]] 
> Sent: 11 June 2007 15:53
> To: Shepherd, EL (Emma)
> Cc: [email protected]
> Subject: Re: IK320 problem
> 
> 
> Hello Emma,
> 
> I have been maintaining Till Straumann's Heidenhain IK320 
> device driver within the confines of the VME support module 
> for some time;
> 
> http://www.aps.anl.gov/aod/bcda/synApps/vme/vme.html
> 
> CVS version 1.1.1.1.2.6 of drvIK320.c is the latest EPICS 
> R3.13.x version of the IK320 driver.
> 
> I think Juraj may be slightly off. In R3.13.x, the record 
> NAME field size is set to 29, which should yield 28 
> characters and a NULL terminator. I count 28 characters in 
> "BL06I-OP-PGM-01:MIR:ENC1:DIR".
> 
> You should still check to make sure that no other PV names in 
> the IOC exceed this limit.
> 
> One question; is the VME CPU board a PPC or 68K?
> 
> One suggestion; turn on driver diagnostics by setting 
> drvIK320Debug=2 at the IOC shell and send me the results.
> 
> Hope this helps,
> Ron Sluiter
> 
> Shepherd, EL (Emma) wrote:
> 
> >Hi everyone,
> >
> >I'm having problems with the IK320 support I am using for some 
> >Heidenhain encoders.  When I try to change their direction 
> or put them 
> >into homing/reference mode, the record goes into error state 
> and I get 
> >messages like the following on the IOC console:
> >
> >
> >===============================================================
> >BL06I-MO-IOC-02 -> filename="../devIK320.c" line number=797
> >ik320WriteMbboSync() entering...
> >
> >filename="../devIK320.c" line number=820
> >ik320WriteMbboSync() sending request (synchronous) failed...
> >
> >status = (1033,10) not in symbol table PV: 
> BL06I-OP-PGM-01:MIR:ENC1:DIR
> >ik320WriteMbboSync()
> >
> >status = 409000a 
> >===============================================================
> >
> >
> >>From a brief look at the code, the error status seems to be 
> "invalid 
> >>VME
> >function call" and "IK320 channel is deactivated".  (I am 
> using version 
> >1.1.1.1.2.6 of drvIK320.c)
> >
> >To give you the background - this has been working fine for months, 
> >including being able to find the reference marks successfully.  Last 
> >week we encountered a problem with the OMS card that was 
> causing one of 
> >the motors to drive in the wrong direction; simply taking 
> the card out 
> >and re-seating it firmly seems to have fixed that (for now 
> at least), 
> >but now I am having these problems with the encoders....
> >
> >Does anyone have any experience with IK320 they can use to shed some 
> >light on this?
> >
> >Thanks!
> >
> >Emma
> ><DIV><FONT size="1" color="gray">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 </FONT></DIV>
> >
> >  
> >
> 
> 
> 
<DIV><FONT size="1" color="gray">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
</FONT></DIV> 

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System