industrialNETworX

HI AJ,

I use a CIF 50 PB Master card.

The profibus slave stack version is from 03/2008 V2.0. I use the slave demo from your CD.

The configuration in your demo is:

ptPck->tInitMs0Req.tData.fSyncSupported   = TRUE;
    ptPck->tInitMs0Req.tData.fFreezeSupported = TRUE;
    ptPck->tInitMs0Req.tData.fNoAddChg        = FALSE;
    ptPck->tInitMs0Req.tData.usIdentNumber    = (TLR_UINT16)ptRsc->tLoc.tMscy1s.uIdentNumber;
    /* Copy the configuration data bytes */
    ptPck->tInitMs0Req.tData.fFailSafeSupp    = TRUE;
    ptPck->tInitMs0Req.tData.fDpv1Enabled     = TRUE;
    ptPck->tInitMs0Req.tData.bSlaveAddr       = PROFIBUS_SLAVE_ADDRESS;
    ptPck->tInitMs0Req.tData.bDataRate        = PROFIBUS_FSPMS_DATA_RATE_1500;

The dataexchange time in your demo is 3 ms.

I did not find any watchdog configuration in your slave demo. The watchdog time in the master is set configured to 1000 ms. The datatranfer mode in the master is "gepuffert, anwendergesteuert". I make the slave configuration in the master over "Netzwerkstruktur einlesen".

Br,
Rainer

HI AJ,

My profibus slave stack version is 2.07xx.

I have received now version 2.010xx.

I got the same error with the new profibus slave demo that I received today per email.

Can you test it self :?:

Br,
Rainer

HI AJ,

Can you send me the master configuration :?:

Br,
Rainer

HI AJ,

Which GSD file do you use ?

Br,
Rainer

HI AJ,

I have tested the profibus slave on the NXSB100 Board, NXDB500-SYS Board and on our Board. All Boards makes the same.

In PbDemo_StateChanged_ind it toggled between state STOP and Operate. I set a breakpoint on the case Label RCX_COMM_STATE_STOP and the program stops here.

void FAR PbDemo_StateChanged_ind(PROFIBUS_DEMO_RSC_T FAR* ptRsc, PROFIBUS_DEMO_PACKET_T FAR* ptPck)
{
  if (ptPck->tStateChangedInd.tData.ulState != (-1))
  {
    /* Handle the new State */
    switch (ptPck->tStateChangedInd.tData.ulState)
    {
      case RCX_COMM_STATE_STOP:
        Mid_LedSetState(ptRsc->tRem.hErrorLed,   LED_MODE_ON, 500, 50);
        Mid_LedSetState(ptRsc->tRem.hReadyLed, LED_MODE_OFF, 0, 0);
        break;


      case RCX_COMM_STATE_IDLE:

        Mid_LedSetState(ptRsc->tRem.hErrorLed,   LED_MODE_ON, 0, 0);

        Mid_LedSetState(ptRsc->tRem.hReadyLed, LED_MODE_OFF, 0, 0);

        break;

      case RCX_COMM_STATE_OPERATE:

        Mid_LedSetState(ptRsc->tRem.hErrorLed,   LED_MODE_OFF, 0, 0);

        Mid_LedSetState(ptRsc->tRem.hReadyLed, LED_MODE_ON, 0, 0);

        break;

      default:

        break;

    }

  }

} /* PbDemo_StateChanged_ind */

Do you now why this can be happen or what do you hear about something :?:

Br,
Rainer

HI AJ,

The profibus slave is running and then i only set one breakpoint at runtime on the RCX_COMM_STATE_STOP case. Normally the programs never stops on this breakpoint :?:

Br,
Rainer

HI AJ,

Thank you for the information. The breakpoint was it. Now i send a string over USB when the data is change to zero. I have test it one hour and the data is OK.

Br,
Rainer

Hi, AJ.
And under what conditions the stack becomes the state RCX_COMM_STATE_STOP?