Experimental Physics and
Industrial Control System

Marty Kraimer <[email protected]> · Wed, 24 Mar 1999 08:00:35 -0600

[email protected] wrote:
> 
> Dear colleague,
> I had put two VME CPUs in one crate, one 147 and one 167. I am running a
> VME canbus program inthe 167 and some Wavetek RS232 connections program in
> 147. Each one works perfectly when they are alone.
> But whenI put them together, aftre the canbus program finish loading, the
> Wavetek program will be interruptted by the message like this:
> logTask: 144 log messages lost.
> interrupt: drvAb: Interrupt but fl_lock not locked
> logTask: 1 log messages lost.
> interrupt: drvAb: Interrupt but fl_lock not locked
> logTask: 44 log messages lost.
> interrupt: drvAb: Interrupt but fl_lock not locked
> logTask: 105 log messages lost.
> 
> Ihave played alot with switching around the Master and slave jumper, the
> sysIntEnable function bu t no luck yet.
> Somehow, Ihave a feeling that the canbus program is sending out the
> interrupt messages to allthe VME crates that are in the dessy chain to
> read all the information like temperature, fan speed and control the
> power, etc.But the CPU that is sending out these messages isn't affected
> by these messages. I don't know if my understanding is in the wrong way or
> not.
> Hope someone can help me in this case.
> 
> Best,
> Jie Lin

Here is a guess.

On both CPUs you are initializing drvAb

On 3.13.x this means the following appears in some xxxInclude.dbd file

driver(drvAb)

Before 3.13 the only way to exclude drvAb is to provide a modified
module_types.c file.

To check this issue the command

dbior "drvAb"

on both systems.

This is a general problem trying to use multiple cpus in the same VME crate.
You MUST ensure that there are no conflicts in using VME address space or
interrupt vectors.

Marty Kraimer

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System