-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for 'missing' RPCs #1
Comments
I'd gladly accept PRs adding support for new RPCs. |
|
Yes, you can use Roboguide for this. The FRVC it uses essentially runs the same software.
All the RPCs I've seen so far use simple Example:
There might be some RPCs which take an actual JSON request document via As to wireshark itself: you don't absolutely have to use it. You could use any HTTP-level traffic capture tool. Perhaps even your browser's developer tools. Then browse to the main website of your robot's controller (ie: At that point start using the interface (ie: iRProgrammer) and keep an eye on your sniffer. You should see the requests as they are generated. |
I've just added an overview of "all" (?) RPCs and whether they're supported already or not. See Supported RPCs in the readme. |
Hello @gavanderhoorn , I tried inspecting the RPCs via developer tools and found some more information about them. I have tested them for V9.30 and V9.40
|
Hi, thanks. I should perhaps have been clearer here: I believe we have all those RPCs in the readme: Lines 143 to 229 in dcb6747
What we need is for them to be supported by the library. Edit: looks like @anandmit93: if you could compare what you found with the table I linked, could you submit a PR adding the ones that are missing? Thanks. Could you also mention the system software versions you tested these against? You already wrote |
Sorry I forgot to mention the complete versions V9.30P/20 and V9.40P/35 & V9.40P/43. I guess only REMARKLIN seems to be missing in the list. Anyways, the support for these RPCs could be extended in this library. |
agreed. Using the existing implementation(s) as a template should make it not too difficult to get something working. If you'd be up for it, I'd be more than willing to review some PRs getting support for some of those in. Maybe start with |
Sure, I will give it a try! I will update you after some progress has been made. |
From your description of the arguments, perhaps comet_rpc/src/comet_rpc/comet.py Lines 775 to 817 in 15f3939
|
Hello @gavanderhoorn , I have just raised a PR for 3 RPC functions. Please have a look at it. |
Hello, @anandmit93 ! This is really great info. |
Would be great to add some of these which are currently unsupported to the library @ghltrdi567. |
Edit: for future readers: please check the main readme for information on which RPCs are already supported.
We're still looking for contributions to add support for the currently unsupported RPCs.
comet_rpc
currently only supports a subset of the RPCsCOMET
offers.Implementing the missing ones should not be too difficult:
messages.py
comet.py
The text was updated successfully, but these errors were encountered: