-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
how send_processdata()
and receive_processdata()
work?
#41
Comments
send_processdata()
and receive_processdata()
work?send_processdata()
and receive_processdata()
work?
send_processdata()
and receive_processdata()
work?send_processdata()
and receive_processdata()
work?
Hi @zthcool,
But let's start with SDO communication. You already used SDO communication to access objects within the object dictionary. The objects are addressed via index and subindex. SDO communication is based on the CoE protocol which is defined on top of the EtherCAT protocol. SDO stands for service data object, what means it is mainly used for setup and configuration. Sounds all complicated but once you get it, it is not that complicated at all. |
@bnjmnp thank you very much about the explanation,I really appreciate.Here is my understanding and application. `
` the code in the
It seems like the PDO is not working,all the output is failed,the |
Here is the code I am trying
When I set the
|
I'm a little bit lost with all your replies. |
Hi @bnjmnp :
This is my first time contact with pysoem and soem,In the past few days,I have built communication with the driver (Panasonic),and make it run to a position successful with
sdo_read()
andsdo_write()
.But thebasic_example.py
and orther issues is all aboutsend_processdata()
andreceive_processdata()
.and I found the command is inwhile
cycle,how do I communicate with driver when the cycle began?and what's the different betweensdo_read()
、sdo_write()
written only andsend_processdata()
、receive_processdata()
used?Maybe my question is junior,but it's helpful for me.
Thank you for taking your time.
The text was updated successfully, but these errors were encountered: