DeviceNet Demo Test on CIF50-DNM
HI,
I want to test DeviceNet Slave Demo from your Download page on an NXDB100 board.
The Master is an CIF50-DNM PCI card.
I have include the EDS file on the PC where the CIF50-DNM card is installed.
When I start the Online/Livelist, only the master card is detected, but no slave.
The slave diagnose shows "No answer" wait for allocation response, device missing, timeout.
Br,
Rainer
Hi AJ,
Sorry i use an NXSB100 board.
Br,
Rainer
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Hi,
have you also connected the +24V to the DeviceNET connector of the NXSB100 board?
Hi AJ,
Can i test the demo on an NXDB500-SYS board too ?
Must i change the configure on the Master ?
I have tested the cable and the master with an another DeviceNet slave and it works.
What i make wrong with the NXSB100 board ?
Br,
Rainer
HI AJ,
I have connected the 24 V on the NXSB100 board.
Br,
Rainer
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Can i test the demo on an NXDB500-SYS board too ?
Must i change the configure on the Master ?
NOTE: This example is limited to 4 Byte I/O Data exchange and to the slave address 32.
What i make wrong with the NXSB100 board ?
HI AJ,
Following diagnose shows in Sycon:
The slave diagnose shows "No answer" wait for allocation response, device missing, timeout
What does it mean ?
Br,
Rainer
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
That the slave is not answering. Maybe the slave is not recognized.
BTW: The project is running on the NXSB100 board?
HI AJ,
Yes its running on NXSB100.
I have downloaded the project with HITOP.
Br,
Rainer
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
And it is running. No errors or exceptions?!
Please download the CAN-HAL from the Hilscher web page, there is a DeviceNET cable schematic included and check this with your cable.
HI AJ,
There is no error and exception!
The Process Task is running !
The cable is OK. I have check it with the DeviceNet / CAN cable pdf file.
I have tested with an another device.
Br,
Rainer
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Hi Rainer,
very strange behavior! I tested the project this morning by my self. Sometimes it worked and sometimes not. :?
I added the following "bug-fix" into my config.c file:
/* *************************************************************************** * Enter Kernel parameter *************************************************************************** */ . . . };extern char _heap_start; /* Defined by the linker */
/*
***************************************************************************
* Enters the RX-kernel mode forever
***************************************************************************
*/
INT main (void)
{
volatile RX_FATAL erXFat; /* Fatal Error value, in case funtion would return *//* Bug-Fix */
/* Clear 1st MB of heap */
memset(&_heap_start, 0, 0x00100000);
/* Initialize and boot the Kernel, with all Peripherals listed in "atrXCfgPre" */
erXFat = rX_SysEnterKernelExt(&trXEnterKernelParam);
.
.
.
Herewith it worked always.
Andreas Jacob
Hilscher Gesellschaft fuer Systemautomation mbH
Hi Rainer,
I think I know, why it is not working. The example was written for a NXSB100 board and you are using the example on a different board - NXEB100-NET (I guess).
The DeviceNET connector is not connected to the same communication channel on booth boards.
NXSB100 uses the communication channel3 and the NXEB100-NET uses the communication channel2.
This could be figured out with the help of the schematics.