[etherlab-users] PDOs Mapping

Fri Feb 7 17:07:12 CET 2020

Dear all,

I wonder if the reason of my problem on multi PDO outputs mapping describe below could be because I use only one domain.
In which case should we use several domains ?

Best regards

Vincent BUSSIERES
Responsable Technique Logiciel

[1572337113342]
24 Avenue de Pasleck
16400 LA COURONNE
-----------------------------------
www.hemeria-group.com<https://webmail.nexeya.fr/owa/redir.aspx?C=GK_BqKCZef7LtPZnqnd_LGYr1NG9sz4Smy3iKIwO-pXqtJC7VgzXCA..&URL=http%3a%2f%2fwww.hemeria-group.com%2f>
P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité.
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.
This email and any files transmitted with it are confidential, intented solely for the unique use of the recipients and don't commit HEMERIA.

De : Gavin Lambert <gavin.lambert at tomra.com>
Envoyé : jeudi 6 février 2020 22:52
À : BUSSIERES Vincent <vincent.bussieres at hemeria-group.com>; etherlab-users at etherlab.org
Objet : RE: PDOs Mapping

I can't speak to the servo drive mapping itself, but as to the other question:

ecrt_slave_config_sdoX is to specify SDO values that should be set during the PREOP -> SAFEOP -> OP transition.  It is intended for any SDO configuration required to bring the device to the intended operational state, especially eg. If the device disconnects or is rebooted during operation.  It must never be used for PDOs - neither for values, nor for the PDO Assign/Config objects.

It is different from the sdo_download requests because the latter only occur once at the time the call is made, while the config_sdo is stored and executed on every later PREOP -> SAFEOP transition (until the master is deactivated).  (These should also never be used for PDOs.)

Gavin Lambert
Senior Software Developer

[cid:image002.png at 01D5DDD9.0148D610]
[TOMRA]<http://www.compacsort.com>[Facebook]<https://www.facebook.com/Compacsort>[Linkedin]<https://www.linkedin.com/company/compac-sorting-equipment/>[Youtube]<https://vimeo.com/compacsort>[twitter]<https://twitter.com/compacsort>[instagram]<https://www.instagram.com/compacsort/>

COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand
Switchboard: +64 96 34 00 88 | tomra.com<http://www.tomra.com>

The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication.

From: BUSSIERES Vincent
Sent: Friday, 7 February 2020 09:03
To: etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>
Subject: [etherlab-users] PDOs Mapping

Dear All,

I mapped the two RxPdo's objects below of my Elmo servodrive.
[cid:image013.jpg at 01D5DDD9.0148D610]

[cid:image014.jpg at 01D5DDD9.0148D610]

Mapping seems to be OK
[cid:image015.jpg at 01D5DDD9.0148D610]

But when I write in digital output PDO, nothing is sent. This PDO is peculiar because digital outputs are witten at subindex 1. I don't know if it's because of that reason.

[cid:image016.jpg at 01D5DDD9.0148D610]

6 is the value sent in the controlword of the PDO 0x1605 but nothing for digital outputs.

You can see my PDO mapping code in the attached file. I have noticed that some people use « ecrt_slave_config_sdoX » function to clear and define Pdo. Is it necessary and what is the difference between this function and sdo download function ?

Regards

Vincent BUSSIERES
Responsable Technique Logiciel

[1572337113342]
24 Avenue de Pasleck
16400 LA COURONNE
-----------------------------------
www.hemeria-group.com<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwebmail.nexeya.fr%2Fowa%2Fredir.aspx%3FC%3DGK_BqKCZef7LtPZnqnd_LGYr1NG9sz4Smy3iKIwO-pXqtJC7VgzXCA..%26URL%3Dhttp%253a%252f%252fwww.hemeria-group.com%252f&data=02%7C01%7Cgavin.lambert%40tomra.com%7C719bd3d34178497263fd08d7ab3f9fb5%7C4308d118edd143008a37cfeba8ad5898%7C0%7C0%7C637166162072223448&sdata=JacbktsaBi%2BI916MF%2F4cOwBsJgED8B10LC45dQpEdf0%3D&reserved=0>
P Afin de contribuer au respect de l'environnement, merci de n'imprimer ce courriel qu'en cas de nécessité.
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.
This email and any files transmitted with it are confidential, intented solely for the unique use of the recipients and don't commit HEMERIA.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5034 bytes
Desc: image001.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0032.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 11438 bytes
Desc: image002.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0033.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1629 bytes
Desc: image004.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0034.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1750 bytes
Desc: image006.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0035.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1855 bytes
Desc: image008.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0036.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1970 bytes
Desc: image010.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0037.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 20278 bytes
Desc: image011.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0038.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1506 bytes
Desc: image012.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0039.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.jpg
Type: image/jpeg
Size: 21730 bytes
Desc: image013.jpg
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0016.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.jpg
Type: image/jpeg
Size: 5340 bytes
Desc: image014.jpg
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0017.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.jpg
Type: image/jpeg
Size: 24839 bytes
Desc: image015.jpg
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0018.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.jpg
Type: image/jpeg
Size: 100801 bytes
Desc: image016.jpg
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200207/b1055611/attachment-0019.jpg>