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

Nepo4Arduino: Interrupt desired #1710

Open
Lexa2000 opened this issue Dec 4, 2024 · 0 comments
Open

Nepo4Arduino: Interrupt desired #1710

Lexa2000 opened this issue Dec 4, 2024 · 0 comments

Comments

@Lexa2000
Copy link

Lexa2000 commented Dec 4, 2024

Unfortunately it is not yet possible to use the Arduino interrupt pins in NEPO, unless you adapt the source code manually.

Is this perhaps already planned?

An idea for the implementation:

So that the interrupt pins must also be used appropriately in NEPO and are not accidentally used for polling, I would define a separate category for interrupts for the Arduino interrupts. This would allow other interrupt types of the Arduino controller to be made available later.

ROBOT CONFIGURATION:

In the interrupt category, there is a separate block for each interrupt (corresponding to the board selection for Nano, Uno, Mega or Nano33).

The PIN cannot be selected, it is fixed.

However, the corresponding IRQ function name must be specified.

In addition, the selection option for a return value of the IRQ function (analogous to the two function block types) should be available.

PROGRAM:

There is now an Interrupt category under the Expert blocks. Only the IRQ functions that have been configured and given an IRQ function name can be found there. All other non-configured interrupts are not available (analogous to the functions).

The help should point out that the IRQ functions should be kept as short as possible.

Perhaps the interrupts can be implemented in one of the next releases.

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

1 participant