{"action":"created","issue":{"url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/70","repository_url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK","labels_url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/70/labels{/name}","comments_url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/70/comments","events_url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/70/events","html_url":"https://github.com/ROBOTIS-GIT/DynamixelSDK/issues/70","id":220204232,"number":70,"title":"Wiki - 3.1 Source File: Folder tree diagram has protocol 2.0 misspelled as protocol 1.0 under example folder","user":{"login":"Shreeyak","id":12800185,"avatar_url":"https://avatars0.githubusercontent.com/u/12800185?v=3","gravatar_id":"","url":"https://api.github.com/users/Shreeyak","html_url":"https://github.com/Shreeyak","followers_url":"https://api.github.com/users/Shreeyak/followers","following_url":"https://api.github.com/users/Shreeyak/following{/other_user}","gists_url":"https://api.github.com/users/Shreeyak/gists{/gist_id}","starred_url":"https://api.github.com/users/Shreeyak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Shreeyak/subscriptions","organizations_url":"https://api.github.com/users/Shreeyak/orgs","repos_url":"https://api.github.com/users/Shreeyak/repos","events_url":"https://api.github.com/users/Shreeyak/events{/privacy}","received_events_url":"https://api.github.com/users/Shreeyak/received_events","type":"User","site_admin":false},"labels":[{"id":399621144,"url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/labels/in%20progress","name":"in progress","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-04-07T12:49:20Z","updated_at":"2017-04-23T02:29:34Z","closed_at":null,"body":"Under the example folder, protocol 2.0 misspelled:\r\n![image](https://cloud.githubusercontent.com/assets/12800185/24800636/7a09512c-1bbe-11e7-9344-40de94886744.png)\r\n"},"comment":{"url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/comments/296415011","html_url":"https://github.com/ROBOTIS-GIT/DynamixelSDK/issues/70#issuecomment-296415011","issue_url":"https://api.github.com/repos/ROBOTIS-GIT/DynamixelSDK/issues/70","id":296415011,"user":{"login":"Shreeyak","id":12800185,"avatar_url":"https://avatars0.githubusercontent.com/u/12800185?v=3","gravatar_id":"","url":"https://api.github.com/users/Shreeyak","html_url":"https://github.com/Shreeyak","followers_url":"https://api.github.com/users/Shreeyak/followers","following_url":"https://api.github.com/users/Shreeyak/following{/other_user}","gists_url":"https://api.github.com/users/Shreeyak/gists{/gist_id}","starred_url":"https://api.github.com/users/Shreeyak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Shreeyak/subscriptions","organizations_url":"https://api.github.com/users/Shreeyak/orgs","repos_url":"https://api.github.com/users/Shreeyak/repos","events_url":"https://api.github.com/users/Shreeyak/events{/privacy}","received_events_url":"https://api.github.com/users/Shreeyak/received_events","type":"User","site_admin":false},"created_at":"2017-04-23T02:29:34Z","updated_at":"2017-04-23T02:29:34Z","body":"Hi,\n1. I have managed to get the source code compiled with my Hardware. Having\nissues in my hardware in switching from read mode to write mode (we are\nusing a tri state buffer for half duplexing). I will get started on the\npoints you mentioned above once I have fully integrated the SDK into my\nbuild.\n\n2. I also now need to port the Dynamixel SDK onto a MCU. I am currently\nusing an STM32 Nucleo board for testing.\nI have built an interrupts-based half-duplex UART library with rx/tx ring\nbuffers for the STM. Now I think all I need to to create a new platform\ncheck (similar to _linux64) and write functions for setupport, readport,\nwriteport.\nCan you suggest the best way to get started on porting the SDK to the MCU?\nI would love to generate a generalized solution that can be merged into the\nSDK and can be used by others.\n\n3. Please do send the SDK management rules so I can write code that follows\nthe rules.\n\nThanks!\n\nOn Apr 21, 2017 7:21 AM, \"Leon\" <notifications@github.com> wrote:\n\nHi,\n\n - Yes, it's similar to the edison, in that it's an SoC, but it's not\none of the models available in the consumer market, like edison or\nyolo. It's a proprietary design, running a stripped down android.\n\nWell, I had tested the SDK in the Raspberry Pi under Snappy Ubuntu Core, so\nyour board must have work with it.\n\n - I'm still working on first getting this integrated into our build,\nso will start working on improving it once that is done. Before I make\nany changes, however, can you share the DynamixelSDK management rules?\nIt will be much easier to work on code keeping the rules in mind.\n\nIf you want to just comment on the source about what every functions mean,\ntheres no specific rules so show me an example source codes which has your\ncomments, and let's work in the rest of the codes as same as it showed\nafter my review.\n\nIf you want to change the APIs, you should show me every point to point,\nand will take time.\n\n - Some examples, for confusing naming, are as below:\nThe correlation between these functions is not clear at all and takes\na lot of digging to figure out. Also, seems conflicting, eg: what is\nreadTx1? If its only Tx, how can one read????\n\nreadTx does only Transmit the package with 'Read' instruction. It provides\nreadTxRx but also provides readTx and readRx separately because they can be\nused in thread process, but normally the users will readTxRx which waits\nthe returned package during designated time.\n\nand the number 1 means the protocol: Dynamixel, as you know, works under\ncommunication protocol 1 or 2 or both (but not the same time) depended on\nthe models.\n\nIf you mean that txPacket and readTx make confusion, actually readTxPacket\nlooks much better, but we thought that theres no needs for doing it.\n\nBut, we have been monitoring the needs and will follow if there are.\n\n—\nYou are receiving this because you were mentioned.\nReply to this email directly, view it on GitHub\n<https://github.com/ROBOTIS-GIT/DynamixelSDK/issues/70#issuecomment-296010678>,\nor mute the thread\n<https://github.com/notifications/unsubscribe-auth/AMNQucmdzOdS9-vimwvMiwvtcBZJCLkPks5ryAu5gaJpZM4M22vY>\n.\n"}}
{"actor":{"display_login":"Shreeyak"}}