Skip to content
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

Establishing an upstream link between HUB and PC #16

Open
Nurech opened this issue Jan 22, 2022 · 1 comment
Open

Establishing an upstream link between HUB and PC #16

Nurech opened this issue Jan 22, 2022 · 1 comment

Comments

@Nurech
Copy link

Nurech commented Jan 22, 2022

Hello.

I am having trouble establishing an link for upstream/downstream data link. Could you please elaborate, perhaps with some examples, how to establish a 2-way data link between HUB <-> PC or is that something that is not possible with this tool?

The only option that I see, is possibility of activating different slots, but we can not call a function with variables passed down within a program, on a slot - am I correct?

@Nurech Nurech changed the title Establishing and upstream link between HUB and PC Establishing an upstream link between HUB and PC Jan 22, 2022
@smr99
Copy link
Owner

smr99 commented Jan 23, 2022

The example program "hubcontrol.py" demonstrates a bidirectional link -- in that you can send commands to start/stop a program on the hub and receive telemetry data (e.g. position variables).

But I think you are asking for something more. Are you asking how to send data to your program running on the hub? I don't know the answer to that question. You can see in HubClient.py and run_command.py a short list of commands that I learned from https://github.com/nutki/spike-tools. None of these will send data to a running program. But clearly it ought to be possible -- as the Mindstorms IDE has programs that run in "remote control" mode.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants