ID |
Date |
Author |
Topic |
Subject |
Text |
 |
2622
|
23 Oct 2023 |
Francesco Renga | Forum | Device with inputs and outputs | Dear all,
I'm writing a very simple device driver
starting from the nulldev.cxx
|
|
2623
|
24 Oct 2023 |
Stefan Ritt | Forum | Device with inputs and outputs | The "multi" class driver takes care of that.
It properly calls the SET and GET functions
|
|
2309
|
16 Dec 2021 |
Zaher Salman | Forum | Device driver for modbus | Dear all, does anyone have an example of for
a device driver using modbus or modbus tcp
to communicate with a device and willing |
|
2312
|
26 Jan 2022 |
Konstantin Olchanski | Forum | Device driver for modbus | > Dear all, does anyone have an example of
for a device driver using modbus or modbus
tcp to communicate with a device and willing |
|
2507
|
10 May 2023 |
Lukas Gerritzen | Suggestion | Desktop notifications for messages | It would be nice to have MIDAS notifications
pop up outside of the browser window.
|
|
2510
|
10 May 2023 |
Stefan Ritt | Suggestion | Desktop notifications for messages | [quote="Lukas Gerritzen"]It would be nice
to have MIDAS notifications pop up outside
of the browser window.[/quote]
|
|
2512
|
10 May 2023 |
Lukas Gerritzen | Suggestion | Desktop notifications for messages | [quote="Stefan Ritt"]
people using Edge/Chrome/Safari/Opera saying
"it's not working on my specific browser |
|
2513
|
11 May 2023 |
Stefan Ritt | Suggestion | Desktop notifications for messages | Ok, I implemented desktop notifications. In
the MIDAS config page, you can now enable
browser notifications for the different types |
|
1385
|
28 Aug 2018 |
Lukas Gerritzen | Bug Report | Deleting Links in ODB via mhttpd | Asume you have a variable foo and a link bar
-> foo. When you go to the ODB in
mhttpd, click "Delete" and select bar, it |
|
1387
|
28 Aug 2018 |
Konstantin Olchanski | Bug Report | Deleting Links in ODB via mhttpd | > Asume you have a variable foo and a link
bar -> foo. When you go to the ODB in
> mhttpd, click "Delete" and select bar, |
|
1392
|
29 Aug 2018 |
Stefan Ritt | Bug Report | Deleting Links in ODB via mhttpd | > > Asume you have a variable foo and a link
bar -> foo. When you go to the ODB in
> > mhttpd, click "Delete" and select bar, |
|
633
|
06 Sep 2009 |
Exaos Lee | Bug Report | Delete key "/A_Str" problem | Another problem while using odbedit.
I tried the batch mode of "odbedit". I created
a key as "/A_Str" by mistake and
|
|
639
|
06 Sep 2009 |
Exaos Lee | Bug Report | Delete key "/A_Str" problem | > Another problem while using odbedit.
> I tried the batch mode of "odbedit". I
created a key as "/A_Str" by mistake and |
|
2943
|
19 Feb 2025 |
Lukas Gerritzen | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | We have a frontend for slow control with a
lot of legacy code. I wanted to add a new
equipment using the
|
|
2944
|
24 Feb 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | The commit that introduced the write cache
size check is https://bitbucket.org/tmidas/midas/commits/3619ecc6ba1d29d74c16aa6571e40920018184c0
|
|
2972
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | I think I added the cache size correctly:
{"Trigger", /* equipment |
|
2973
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | the main purpose of the event buffer write
cache is to prevent high contention for the
|
|
2974
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > the main purpose of the event buffer write
cache
|
|
2975
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > > the main purpose of the event buffer write
cache
> how to control the write cache size:
|
|
2979
|
21 Mar 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > All this is kind of reasonable, as only
two settings of write cache size are useful:
0 to
|
|