Issue about MXA.

[richypipi55]

Hello Everybody.
So I am working with MXA and am having a hard time getting it to run consistently.
I often get the following errors and I am not sure what is triggering them or how to solve them:
any advice on what these mean and potential causes?I know that is a broad questions sorry. and thanks. E

[MXA] 783 เว็บแทงบอล
UDP connection timeout 3000 ms triggered

Robot stopped by SoftPLC (MXA_SYN)
Originator KS

MXA414: TIMEOUT HEARTBEAT FROM PLC

KSS00108 Dynamic Braking Active

[Johannes @ Robots in Architecture]

Hello,

Are you using it with KUKA|prc or another software?
In any case, the error message tells you that there wasn't any communication happening for over 3 seconds.
Reasons for that may be a bad/overloaded connection (e.g. via WiFi), or possibly problems with the network cable or network adapter.
You could also take a look at the Task Manager if e.g. your PC's load is very high.

You could increase the timeout value in the mxA configuration, however 3 seconds is already very long, so I wouldn't really recommend that.

Best,
Johannes

[singline]

When attempting to connect via mxA the robot doesn't initialise, could it be a library error?

Code: [Select]

Progress:
Robot Online: True
Robot Initialized: False
mxA Program Active: False
mxA Buffer: 0 | previous 0 at 12:41
mxA Heartbeat: 254
mxA Average Response: 4 (Submit) / 3 (ProConOS)
Error Robot Interpreter: 0 | (0)
Error Submit Interpreter: 0 | (414 at 12:38)
Error PLC: 0 | (503 at 12:26)
Error KUKA: 83 | (83 at 12:41)
Error PCOS: 783 | (783 at 12:41)

ERROR: No statements can be executed, as the connection has not been initialized.
ERROR: Error messages of the robot controller are active. The $STOPMESS signal of the Automatic External interface is active.
ERROR: The robot program is not active. The $PRO_ACT signal of the Automatic External interface is not active..
mxA Submit Interpreter Error 0 -

Axis Position: A1 0, A2 0, A3 0, A4 0, A5 0, A6 0, E1 0, E2 0, E3 0, E4 0

Am I missing something? The OV updates with a slider..

[Johannes @ Robots in Architecture]

Usually if the OV updates but nothing is received then the firewall is blocking the robot, i.e. your PC is sending data packages just fine but not receiving any.
Try disabling the Windows firewall on your PC!

Also, the robot should be in EXT mode and depending on the setup you might need to press the Reset input (Boolean toggle on the mxA component) a tiny bit longer.

Best,
Johannes

[singline]

Unfortunately, no change. KUKA suggested it may be a library issue, the KUKA has mxA 3 installed.

[Johannes @ Robots in Architecture]

Did you test it with the KUKA supplied test program? That would be a good first step.
I haven't tested it with mxA 3 yet, but was assured that mxA 3 doesn't contain any breaking changes.

Best,
Johannes

[singline]

We did, but with another laptop. Its more than likely my laptop..

[Johannes @ Robots in Architecture]

It might still be on my end, unfortunately I cannot test it at the moment.
I first need to find the time to update my robots to KSS 8.5 and then to mxA 3.

Best,
Johannes

[guptaandrew]

sorry to bring up such issue again as i am having this issue recently but from here could not reach to any conclusion mcdvoice

[Johannes @ Robots in Architecture]

Hello,

What issue are you having?

Best,
Johannes