Activity for ahdelta
-
ahdelta posted a comment on discussion Engineering 🇬🇧
I have sent a link to the file in "my question" thanks.
-
I have an esi (xml) file for a Drive with EOE description. When trying to install, I become an error: Unable to import device description file: InnerException: For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method. I don't know if the "DtdProcessing" can be set in CodeSys ? or if the problem is when generating the xml file? The drive supplier, says the xml...
-
Thank you - working now.
-
pic2: where I can read the value from program
-
pic1:
-
When I am offline, I cannot see the parameters, see attachment. I can read the actual value from the program, but when I try to write it fails during compile. I use v3.5 SP18 Patch3, PLC: Janztec empc-aimx6 target 4.6.0.0
-
If I call MC_HOME, it keeps being busy. I Then found that if I change "DSP402_StateMachine._bCheckBit10PostHoming" to FALSE, it seems to work. My problem is that I cannot figure out how to set this to FALSE from my code. I can change it in the "SM_DRIVE_ETC_GenericDSO402 IEC objects", but it defaults to TRUE after restart. So how can I access this parameter from the code? Thanks.
-
When I look at the "Task configuration monitor", I see jitter on the task, controlling Ethercat, to be around +/-160us. I have a servodrive attached, and in this drive I see a PDO min/max cycle time to vary 1us, which is much better than shown in CodeSys. So the question is does the jitter in the "Task configuration monitor" reflect the actual timing of the telegrams sent to the drives? or is the measurement in the drive way off? Thanks in advance
-
When I look at the "Task configuration monitor", I see jitter on the task, controlling Ethercat, to be around +/-60us. I have a servodrive attached, and in this drive I see a PDO min/max cycle time to vary 1us, which is much better than shown in CodeSys. So the question is does the jitter in the "Task configuration monitor" reflect the actual timing of the telegrams sent to the drives? or is the measurement in the drive way off? Thanks in advance