Hypertherm XPR woes

I am trying to connect linuxcnc to a Hypertherm XPR plasma via EtherCAT but am having issues.  I don't have Twincat or EtherCAT Configurator to produce an xml file, so, I have attempted to make one on my own.  The xml seems to load correctly and I can see the lcec hal component, however, the XPR plasma will not get past PREOP.  It complains with:

ERROR 0-0: Timeout while waiting for SDO entry 0x3000:3 description response.

A capture of the sdos indicates that 0x3000:3 and above don't exist.  Why is that address being interrogated?  Did I miss something in the xml?

All applicable project and capture files are in the attached zip file.

Any help would be greatly appreciated.  I have a limited window of time to fiddle with this before we stick an Edge Connect on it and send it on its way.

Thanks,

Butch

The hypertherm docs show quite a number of 3000:xx SDO's
Try this
www.hypertherm.com/Download?fileId=HYP182148&zip=False

Thanks Rod.  I have that document already and have examined it thoroughly.   And, yes, there are several 3000:xx SDOs that are used, plus some 3100, etc.  Here is an ESI file for the XPR from off an Edge Connect control.  Hypertherm has an EtherCAT Studio that reads this and generates the ENI xml file for their EtherCAT Master to use.  Notice the datatype DT3000 lists all applicable SDO entries I need.  However, when I query the XPR with EtherLab's EtherCAT Master, I get something different.  The attached file 'XPR sdos (captured).txt' is what I get from the query and it tells a different story than the ESI file provided for the XPR, (stops at 3000:02).

I have tried using bits and pieces of Hypetherm's generated ENI file, (attached: ethercat-config-xpr.xml), but EtherLab's master chokes on most of it.

I don't have access to TwinCat or EtherCAT Configurator from Beckhoff at this time but have sent a request to our Sales Rep to order the Configurator.  Apparently, he has to refer me to a "special group" at Beckhoff corporate.  I figure that may be my next best step on generating an ENI file with components I can use.

I'm afraid I'm going to run out of time to mess with the XPR before I get the Configurator and we have to ship out the XPR.

Have you, (or anyone), seen a similar situation where an ESI file is different than what you get by interrogating a device?