Experimental Physics and
Industrial Control System

Peter Linardakis <[email protected]> · Fri, 13 Dec 2013 05:24:09 +0000

Hi Mark

Where/when should I expect the debug messages from the PM304 driver to appear?  I don't seem to see any on top of what we had?  It's late on a Friday afternoon mind you.

Regarding running on linux-arm, I'm actually running this on a sacrificial Raspberry Pi to avoid destroying our production environment.  The end goal is to get this cross compiled and onto all of our platforms.

Regards
Peter

-----Original Message-----
From: Mark Rivers [mailto:[email protected]] 
Sent: Friday, 13 December 2013 2:28 PM
To: Peter Linardakis; [email protected]; [email protected]
Subject: RE: Mclennan PM600 motor controller

Hi Peter,

OK, we're making progress.  It is crashing when drvPM304.cc::motor_init is called from device support.  That function attempts to figure out what model controller it is talking to, whether it is servo or stepper, etc. by querying the controller.  It calls send_recv_mess to talk to the device, and that in turn calls epicsStrtok_r, which is crashing.

Since it is crashing when the driver itself is intializing all controllers, it will crash before you can run dbior, as you discovered.

The next step is to turn on debugging in the PM304 driver.  You need to edit the motor/motorApp/MclennanSrc/Makefile and uncomment this line:

#USR_CXXFLAGS += -DDEBUG

Then rebuild that directory and your application.

In your startup script add the following line:

var drvPM304Debug 10

before the call to PM304Setup(1, 10)

Then we should get some debugging information when the driver initializes.

I see you are running on linux-arm.  Perhaps there is a problem with epicsStrtok_r (which I wrote a long time ago) on that architecture.  But let's hope it's something simpler!

Mark

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System