hardbyte / hardbyte/python-can
Functionalities of send_periodic()
- Langage dominant
- Python
- Étoiles
- 1.6k
- Forks
- 697
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
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?
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.