• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Activating Distributed Clock - EtherCAT (Slave-side)
Well I don't know if it helps much but we have product called netPI, which includes a netX51 chip (it is the same chip die as netX52 used on netHAT and just has connectivity to external RAM additionally as only difference) that is programmed with the very same packets and for this netPI we have made programming examples public on github.

Here is the sourcode link to a file including a SetConfiguration packet: https://github.com/HilscherAutomation/ne...ndlerECS.c

There is one more thing to know: netHAT is a device that is automatically configured to fixed 32bytes input and 32 byte output data after the installed firmware (*.deb file) has been loaded into netHAT's flash during first start of your application program. This makes it very simple to customers to get it operative and they mustn't care about configuration settings like you do right now.

The 32Byte IO configuration is held in a file named config.nxd that you find in the folder \opt\cifx\deviceconfig\FW\channel0\ next to the firmware file named (X070F00X.nxf for EtherCAT slave in your case) after you installed the *.deb file. So now once you start any application using the driver ... this driver checks whether or not the installed firmware on Linux side is the same as loaded into netHATs FLASH memory. If it is not then it loads it ... but not only the *.nxf file but also the config.nxd file. And then the device is preconfigured by the FLASH contents rather than through an appliction program you have in mind. I am not sure if a post-configuration through "SetConfiguration" packet would be accepted by netHAT if it was already configure through the FLASH memory.

You never fail until you stop trying.“, Albert Einstein (1879 - 1955)


Messages In This Thread
RE: Activating Distributed Clock - EtherCAT (Slave-side) - by Armin@netPI - August-8th-2019, 06:59 AM

Forum Jump:

Users browsing this thread: 1 Guest(s)