Re: No HomeStatus and No Motion with OMS MAXv : Motor 6.5.1 / VxWorks 6.8 / base 3.14.11

[Daron Chabot <daron.chabot@gmail.com>]

Ron,

Please consider incorporating something like the following in "motor.h", and do away with the #cpu(xxx) notation (which triggers _a lot_ of compiler warning/noise):

/* Define, from top to bottom, how bit fields are packed. */

/* This works for gnu, SunPro, MS Visual C. */

#if defined(_WIN32) || defined (_M_IX86) || defined (_X86_)

    #define LSB_First (TRUE)  /* LSB is packed first. */

#elif defined (__i386__) || defined(_armv4l_) || defined (_X86_64_) || defined(__ARMEL__)

    #define LSB_First (TRUE)  /* LSB is packed first. */

#elif defined(__sparc__) || defined(__m68k__) || defined (__PPC__) || defined(__ARMEB__)

    #define MSB_First (TRUE)  /* MSB is packed first. */

#else

#error unknown bit order!

#endif

IIRC, the compiler for vxWorks is gnu-based, so you should be able get a list of compiler-provided preprocessor definitions like this:

    djc@TooLBox--> touch /tmp/foo.c

    djc@TooLBox--> gcc -E -dM /tmp/foo.c | less

Thanks.

-- dc

On Mon, Oct 11, 2010 at 3:17 PM, Ron Sluiter <sluiter@aps.anl.gov> wrote:

Hello Jerome,

I had to make a change to the,
<motor>/motorApp/MotorSrc/motor.h
file in order to successfully compile it for a VxWorks 6.x
target architecture.  I am surprised that you are not getting
a compiler error.

I planned on releasing a minor version update (R6.5.2)
that includes the above change to the motor.h file,
but I have made the motor.h file change available here.

So let us see if that fixes the problems you are experiencing
before I make a new motor record release.

Ron

On 10/11/2010 10:08 AM, Jerome HOSSELET wrote:

Hi all,

I have some troubles with a motor driver v 6.5.1 and EPICS base 3.14.11 and VxWorks 6.8

VxWorks 6.8 : install ok
Base EPICS 3.14.11 : compilation ok
Support motor 6.5.1: compilation ok

I use a MAXv-4000 with a servo configuration (PSM configuration).

When i use a VxWorks 6.7 and motor 6.4.4 and base 3.14.8.2 => all it's ok
but when i move in last release all package it doesn't works.

The home status : ATHM always = 0
During the motion a message appear Motion = "Move"  &&  "Communication error"

When i check my analogic output for motor 1 (commande analogic to the servo) 

I probe always 10 V. 

It's not normal ......

Ron or other can i help me ?

Jerome HOSSELET
j.hosselet@orange.fr