Skip to content

Functionalities of send_periodic() #1482

Open
@questberna

Description

@questberna

Hello!
Sorry if this has already been discussed somewhere else but: I need to send multiple periodic messages that also need to be modified in the long run, the trigger event is a user input in order to try and make test bench power up. In the docs I read:

The task will be active until one of the following conditions are met:
- the (optional) duration expires
- the Bus instance goes out of scope
- the Bus instance is shutdown
- :meth:stop_all_periodic_tasks is called
- the task's :meth:~can.broadcastmanager.CyclicTask.stop method is called.

Also when i perform a send_periodic() a new task is returned, just a clarification: does the task need to stay on scope or is it the can.interface.Bus instance? Should I keep a dictionary

{
  'can0': {
               arb_id: taks
  }
  'can1': {
               arb_id: taks
  }
}

And simply update the task data at occurance?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions