-
Notifications
You must be signed in to change notification settings - Fork 197
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
Support 29 bits COB-ID #148
Milestone
Comments
You are right that it does not support 29-bit identifiers yet. I was not sure if anyone actually used that. I can have a look and see if it is doable without too much work involved. |
Hey Christian
Thank a lot.
Hyun-Young
…-----Original-Nachricht-----
Betreff: Re: [christiansandberg/canopen] Support 29 bits COB-ID (#148)
Datum: 2019-03-14T19:33:56+0100
Von: "Christian Sandberg" <[email protected]>
An: "christiansandberg/canopen" <[email protected]>
You are right that it does not support 29-bit identifiers yet. I was not
sure if anyone actually used that.
I can have a look and see if it is doable without too much work involved.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#148 (comment)>
, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AuRcEP-T-kqBXHFO29fOaGv4abh0ibGHks5vWpYPgaJpZM4bz-Z9>
.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/christiansandberg/canopen","title":"christiansandberg/canopen","subtitle":"GitHub
repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open
in
GitHub","url":"https://github.com/christiansandberg/canopen"}},"updates":{"snippets":[{"icon":"PERSON","message":"@christiansandberg
in #148: You are right that it does not support 29-bit identifiers yet. I
was not sure if anyone actually used that.\r\n\r\nI can have a look and see
if it is doable without too much work involved."}],"action":{"name":"View
Issue","url":"#148 (comment)"}}}
[ { "@context": "http://schema.org", "@type": "EmailMessage",
"potentialAction": { "@type": "ViewAction", "target":
"#148 (comment)",
"url":
"#148 (comment)",
"name": "View Issue" }, "description": "View this Issue on GitHub",
"publisher": { "@type": "Organization", "name": "GitHub", "url":
"https://github.com" } } ]
|
I implemented a simple solution for now where IDs > 0x7FF will be sent as extended ID. |
Thank a lot! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Christian
Thank for your effort for developing CANopen stack for Python.
I have a device which uses four SDO server channels.
the first one is the standard SDO server: 0x600 /0x580 + node-id, defined in object 0x1200
the second one is the standard SDO server: 0x640 /0x5C0 + node-id, defined in object 0x1201
the third one is the standard SDO server: 0x1C000000 /0x18000000 + node-id, define in 0x1202
the last one is the standard SDO server: 0x1D000000 /0x19000000 + node-id, defined in 0x1203
But you are using just the standard SDO channel.
' self.sdo = SdoClient(0x600 + self.id, 0x580 + self.id, self.object_dictionary)'
I tried to change the fix-offset in source-code. I think, your stack doesn't support 29bits.
Are you going to change it?
kind regard Hyun-Young
The text was updated successfully, but these errors were encountered: