-
The hardware module fs20 and rfm12 do not only controll the hardware but also implement the application protocol which leads to
- complex modules
- code duplication
- conflicts
The existing modules …
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…
-
```
All hardware-related classes currently live in one module and are 'hacked-in'
by CPyrit's __init__-function. This is ugly.
Separate the scheduler-code from the hardware-code. The available hardw…