About alink

alink · ‎09-16-2022

The issue is from somewere different, so topic can be closed

alink · ‎09-15-2022

Hello, I'd like to write the local output of an IndraDrive. Reading local input P-0-0302 works fine, but when wirting output P-0-0304 there's always an ACCESS_ERROR. --- VAR fbAIL_ECATSoeWrite: IL_ECATSoeWrite; iValueLocOutput: UDINT; bLocBit7: BOOL; END_VAR Code: IF NOT fbAIL_ECATSoeWrite.Done AND NOT fbAIL_ECATSoeWrite.Error THEN fbAIL_ECATSoeWrite(Execute:= TRUE,MasterName:= ADR('ethercatmaster'),AddressType:= 1004,Idn:=IL_ECATSOEIdnCoding(SOE_P_PARAM,0,304),Element:= SOE_ELEMENT_OPDATA,SizeOfValue:= SIZEOF(iValueLocOutput),ValueAdr:=ADR(iValueLocOutput) ,); ELSIF fbAIL_ECATSoeWrite.Done OR fbAIL_ECATSoeWrite.Error THEN fbAIL_ECATSoeWrite(Execute:= FALSE,MasterName:= ADR('ethercatmaster'),AddressType:= 1004,Idn:=IL_ECATSOEIdnCoding(SOE_P_PARAM,0,304),SizeOfValue:= SIZEOF(iValueLocOutput),ValueAdr:= ADR(iValueLocOutput) ,); END_IF iValueLocOutput.0 := bLocBit7; --- bLocBit7 is a BOOL which can be set with visu Local output is bit 0 of P-0-0304. Writing this with ctrlX-Drive is working directly is working. So the issue is with Ethercat, I think.

alink · ‎09-13-2022

Thanks for reply. Don't know what was wrong but today it is possible to clear errors. Because of this issue all these possibilities were tested. But how does ImcCtrl.Admin.ClearError work? It doesn't seem to have the effect like arAxisCtrl_gb[1].Admin.ClearError, isn't it? At the end, there was no noticeable effect of ImcCtrl.... I wonder, this is not arAxis[1.....10] specified, a command in general? No effect, but ImcStatus.Diag.ClearErrorAck is reporting TRUE.... Writing in DataLayer /diagnosis/confirm/all-erros seems more to clear a message in 'pendign diagnostic' but less to reset/clear an error in motion or at the drive, isn't it? And I am sorry for so many (simple) questions but it's a complete new technic and system (ctrlX and EtherCat) compared to MLD (with SERCOS) at which I was working the last 10 years. But with this new system the current application with MLD should be replaced, so there always will be an association to that....

alink · ‎09-12-2022

Maybe I'm off the track completely, but for example there's an error in the drive: F8079 In Motion APP / CtrlX there's an error as well In PLC, there are meanwhile 3 (!) commands to clear this error: BUT nothing helps. There's a bad "ACCESS_ERROR" when using ImcCtrl.Admin.ClearError. To clear error in all systems, so that it possible to go back to work, is: If possibility to have access to ctrlX: clear error in ctrlX / Motion APP If there is no access to ctrlX: turn off/on PLC. There has to be a better way, with a simple button on the VISU. The button is already implemented and is the command for clearing error. But clearing ALL errors doesn't work.

alink · ‎09-12-2022

One additional note: Not only modifying "callablePool", "programs":[{ "callables"[{...()]}]} has to be modifyed as well. Deleting the correspondent, complete entry of: "EXAMPLE" { "alias": "", "arguments": [ "distribution" ], "id": "1", "index": 3000, "name": "axisprofile", "sync": { "after": [], "before": [] }, "watchdog": "WDG_DEFAULT" }, Then, the "sequence" has to be modifyed with the right "id" Otherwise, there will be a new error, like "motion app not in run"

About alink

Re: Operating mode with IndraDrive MPB20

Writing local output on IndraDrive P-0-0304

Re: Resetting ALL KIND of error in Motion App

Re: Resetting ALL KIND of error in Motion App

Re: ctrlX Core scheduler error