[Emc-developers] notes from Developer Meeting Sunday 2026-06-07 10:00 CEST

[Robert S. <rm...@un...>]

On Sa, 2026-06-06 at 17:35 +0200, Robert Schöftner wrote:

> Hi,
> 
> it's been another two weeks and I wanted to send the reminder /
> invitation
> 
> 
> According to our bi-weekly schedule alternating between "early" and
> "late", next video meeting is this sunday at 10:00 CEST.
> 
> [https://greenlight.bbb.uni-rostock.de/b/ste-c4d-brs-3k6](https://greenlight.bbb.uni-rostock.de/b/ste-c4d-brs-3k6)
> Access code: 869782
> 
> [https://www.timeanddate.com/worldclock/meetingdetails.html?year=2026&month=6&day=07&hour=8&min=0&sec=0&p1=319&p2=236&p3=240&p4=136](https://www.timeanddate.com/worldclock/meetingdetails.html?year=2026&month=6&day=07&hour=8&min=0&sec=0&p1=319&p2=236&p3=240&p4=136)
> 
> see you there and then
> 
>


Some notes:

we discussed:

*   how are docs generated and uploaded? →get rid of buildbot, get docs out of github CI
*   apt sources file for trixie, missing key?
*   translations?

## Pull Requests

*   UI smoke tests
    *   generate differences of screen shots
*   merge #4128 AC coupling
*   merge #4127
*   #4126: not ready yet
*   #4123: not ready yet
*   merge #4117
*   merge #4116
*   #4113: changes look of documentation, big improvement. conflict needs resolving.
*   merge #4112
*   merge #4111
*   #4110: conflict
*   merge #4109: relocate man pages
*   merge #4108
*   merge #4106
*   #4099 getter/setter
    *   discussion about hal types: maybe replace everything with double?
    *   hal.hh module: pybind11 branch vs. master
    *   clearly needs more discussion
*   merge #4098
*   #4009: not ready yet. maybe too complicated?
*   #3930: conflicts relating to weblate


#4099 was discussed ore broadly, it was suggested to replace the underlying storage type with double (except maybe for hal_port).

All datatypes available in 2.9 would fit into a double, and there seem to be no real use cases that would require HAL pins with 64bit integers. Even fast counting encoders would fit easily into the 52bit mantissa of a double (i.e. it would take 5 days spinning a 24bit encoder with 36000rpm to lose one bit of precision).

STMBL was given as an example of a similar HAL system that works completely with float, running of 72MHz resp. 168MHz Arm Cortex-M4 Microcontrollers (32bit, 16/32bit thumb instructions, FPU) and doing motor control loops with up to 15kHz.

Going for one datatype would make some things much easier and get rid of cruft like n*(n-1) conversion functions (which are error-prone to use).


As there was no consensus reached and cleary further discussion is needed it was decided to postpone the PR.


I didn't catch the last 10 minutes due to audio problems

-- 

```
Robert Schöftner <rm...@un...>
```