<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi Vincent,</p>
<p><br>
</p>
<p>Some further thoughts:</p>
<p><br>
</p>
<p>- If your drive can handle splitting your input PDOs and your output PDOs into two different domains (i.e. put the drives inputs into your common domain and the drives outputs into its own domain that can be stopped) then you can still read your drives status
while not sending the outputs. The input domains watchdog can then probably also remain active and the drive can handle a communication loss.</p>
<p><br>
</p>
<p>- If you can map the operation mode request index/subindex (and maybe target velocity, updated from your actual velocity) into your drives output PDO as extra items, then you could continue all PDO communications (from a common domain) and swap the drive
into velocity mode and let the drives internal <span>controlled stop routine decelerate the motor. You then also shouldn't need a custom routine installed on the drive.</span></p>
<p><span><br>
</span></p>
<p><span>Of course none of these options are actually safety rated as they all rely on the EtherCAT master doing something. It might still be worth investigating further a drive logic only solution (maybe similar to the second option above, but where the slave
logic puts the drive into velocity mode, so the torque from the PDO may be ignored anyway).</span></p>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<br>
</div>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
Regards,</div>
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
Graeme.</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Etherlab-users <etherlab-users-bounces@etherlab.org> on behalf of BUSSIERES Vincent <vincent.bussieres@hemeria-group.com><br>
<b>Sent:</b> Friday, 18 September 2020 03:01<br>
<b>To:</b> Sebastien BLANCHET; etherlab-users@etherlab.org<br>
<b>Subject:</b> Re: [Etherlab-users] dynamic PDO unmapping</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear All,<br>
<br>
Thanks a lot for your help. I placed servo drive slave into its own domain. Obviously I needed to desactivate heartbeat.<br>
It may not be the best solution but it works....<br>
<br>
Regards<br>
<br>
Vincent BUSSIERES<br>
Responsable Technique Logiciel<br>
<br>
<br>
ZE Ma Campagne<br>
36, Impasse Félix Nadar<br>
16000 ANGOULEME<br>
Tel: 33 (0)9.72.40.35.08<br>
<a href="http://www.hemeria-group.com">www.hemeria-group.com</a> <br>
Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité.<br>
Ce message et les fichiers pouvant être attachés sont confidentiels, réservés à l'usage unique des destinataires et n'engagent HEMERIA sous aucune forme que ce soit.<br>
This email and any files transmitted with it are confidential, intented solely for the unique use of the recipients and don't commit HEMERIA.<br>
<br>
<br>
<br>
<br>
-----Message d'origine-----<br>
De : Etherlab-users <etherlab-users-bounces@etherlab.org> De la part de Sebastien BLANCHET<br>
Envoyé : jeudi 17 septembre 2020 12:29<br>
À : etherlab-users@etherlab.org<br>
Objet : Re: [Etherlab-users] dynamic PDO unmapping<br>
<br>
Hi,<br>
<br>
I think that it would be preferable to stop the drive without breaking/modifying the EtherCAT communication, so that you can continue to monitor the drive when it is stopping.<br>
<br>
Which servo drive do you have ?<br>
<br>
If you have a Kollmorgen AKD,<br>
<br>
- You can configure DRV.DISMODE to trigger a controlled stop when the drive is disabled. In this case you can stop the motion by disabling the drive with the ControlWorld Object (0x6040:0x0),<br>
<br>
- You can also trigger a MACRO with a digital input. In this case it opens many other possibilities.<br>
<br>
Regards,<br>
--<br>
Sebastien BLANCHET<br>
<br>
<br>
On 9/17/20 10:14 AM, BUSSIERES Vincent wrote:<br>
> Thank you for your answers. I'll try to place each slave into its own domain and I'll keep you informed of the result.<br>
> <br>
> To my mind, the best solution, would be the servo slave itself, when it detects a fault condition, should go into a state where it ignores whatever values the master is sending. I have already asked to the slave vendor, I'm still waiting for his answer. I
don't this it will be possible<br>
> <br>
> Best regards<br>
> <br>
> Vincent BUSSIERES<br>
> Responsable Technique Logiciel<br>
> <br>
> <br>
> ZE Ma Campagne<br>
> 36, Impasse Félix Nadar<br>
> 16000 ANGOULEME<br>
> Tel: 33 (0)9.72.40.35.08<br>
> <a href="http://www.hemeria-group.com">www.hemeria-group.com</a><br>
-- <br>
Etherlab-users mailing list<br>
Etherlab-users@etherlab.org<br>
<a href="http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-users">http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-users</a><br>
-- <br>
Etherlab-users mailing list<br>
Etherlab-users@etherlab.org<br>
<a href="http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-users">http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-users</a><br>
</div>
</span></font></div>
</div>
</body>
</html>