Experimental Physics and
Industrial Control System

"Jim Chen" <[email protected]> · Thu, 21 Apr 2011 11:39:30 +0100

Thanks for all the comments. 

I have a configuration which takes 14 arguments to the shell command and
here is the start up printouts:

# For VME/VxWorks
IPAC3 = ipacAddHy8002("3,2")
new symbol "IPAC3" added to symbol table.
IPAC3 = 0x1ed56080: value = 0 = 0x0

#int Hy8417AsynInit(char *portName, int vmeSlotNum, int ipSlotNum, int
vectorNum,
#                                       int samples, int average, int mode,
int offset, int clockRate,
#                   int extClock, int fastADC, int range, int ChannelNo, int
ChannelBit)
# Settings are:
#       vmeslot=0, ipslot=5, vector=10, samples=1000, average=1,
mode=1(trigger), offset=0,
#   clockrate=9(1kHz), extclock=0(no), fastADC=0(slow mca & EPID),
range=0(+/-10V),
#       ChannelNo=16, ChannelBit=16
Hy8417AsynInit("ADC8417", IPAC3, 1, 10, 1000, 1, 1, 0, 9, 0, 0, 0, 16, 16)
too many arguments to functions.

Done executing startup script /localhome/local/st.cmd
->

It complains about "too many arguments to functions."

Interestingly, it doesn't complain in my Linux box.

I remember few years ago we had similar situation with about 18 arguments in
a configuration routine, we ended up splitting them into two with the first
one taking 12 and it works fine since.

The test environment: VxWorks 5.5, processor board MVME5500, EPICS 3.14.8.2.
Any ideas please?

Jim
Hytec Electronics Ltd.
Tel: +44 (0) 118 975 7770
Fax: +44 (0) 118 975 7566
Web: www.hytec-electronics.co.uk
Incorporated in England No 1246940
VAT NO GB 285 2479 27
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

> -----Original Message-----
> From: [email protected] [mailto:tech-talk-
> [email protected]] On Behalf Of Andrew Johnson
> Sent: 20 April 2011 18:18
> To: [email protected]
> Cc: Eric Norum
> Subject: Re: shell command arguments limitation?
> 
> On Wednesday 20 April 2011 12:02:31 Eric Norum wrote:
> > The ioc shell doesn't call its registered functions with individual
> >  arguments so the limit you're describing does not exist.  iocsh
> handler
> >  functions are called with a single argument -- a pointer to an array
> of
> >  argument unions.  The only limit that I can see is the amount of
> memory
> >  available to hold this array.
> 
> There may be a limit to the length of the command line buffer which
> would
> restrict the number of arguments, but that probably depends on the
> underlying
> OS and what the EPICS_READLINE setting is.
> 
> Jim may have been remembering the arguments to the vxWorks taskSpawn()
> function, which is limited to 10 arguments.  I'm not aware of a limit
> in the
> vxWorks shell either, but there may be one that I haven't come across
> yet.
> 
> - Andrew
> --
> An error is only a mistake if you don't learn from it.
> When you learn something from it, it becomes a lesson.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System