| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1573
|
26 Jun 2019 |
Konstantin Olchanski | Forum | Problem transferring fetest data from the remote frontend to the backend | > Hi again, we now have Midas installed on
the Rpi (remote frontend machine) and
> have managed to run Fetest on it. Now we |
|
|
1485
|
12 Mar 2019 |
Francesco Renga | Forum | Problem stopping every second run | Dear all,
I'm running a DAQ frontend and it
works well if one single run is
|
|
|
1489
|
13 Mar 2019 |
Konstantin Olchanski | Forum | Problem stopping every second run | > I'm running a DAQ frontend and
it works well if one single run is
> taken. If I try to take a second run right |
|
|
336
|
02 Feb 2007 |
Exaos Lee | Bug Fix | Problem solved by Re-define _syscall0(...) | OK, I searched and found that my kernel doesn't
support "_syscall0" any more. So I patched
the system.c as the following (from line |
|
|
340
|
06 Feb 2007 |
Stefan Ritt | Bug Fix | Problem solved by Re-define _syscall0(...) | [quote="Exaos Lee"]Maybe it's not the perfect
way, but it works. :-)[/quote]
|
|
|
1021
|
14 Oct 2014 |
Konstantin Olchanski | Bug Report | Problem in mfe multithread equipments | In the ALPHA experiment at CERN I found a
problem in mfe.c handling of multithreaded
equipments. This problem was in
|
|
|
1023
|
14 Oct 2014 |
Konstantin Olchanski | Bug Report | Problem in mfe multithread equipments | For my reference:
good version: https://bitbucket.org/tmidas/midas/src/6899b96a4f8177d4af92035cd84aadf5a7cbc875/src/mfe.c?at=develop
first breakage: https://bitbucket.org/tmidas/midas/src/c60259d9a244bdcd296a8c5c6ab0b91de27f9905/src/mfe.c?at=develop
|
|
|
1026
|
15 Oct 2014 |
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | You are absolutely correct, the code is certainly
wrong. It looks to me like the
|
|
|
1027
|
15 Oct 2014 |
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | Please disregard my previous posting, you
don't need the while loop, since it's already
in the scheduler (around lines 2160 under |
|
|
1030
|
16 Oct 2014 |
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | > while (1)
> wait 10 ms for an event
> process event, loop back
|
|
|
1941
|
09 Jun 2020 |
Isaac Labrie Boulay | Info | Preparing the VME hardware - VME address jumpers. | Hey folks,
I'm currently working on setting up a MIDAS |
|
|
1943
|
10 Jun 2020 |
Konstantin Olchanski | Info | Preparing the VME hardware - VME address jumpers. | Hi, if you are not using any VME hardware,
then you have no VME address jumpers to
set. https://en.wikipedia.org/wiki/VMEbus
|
|
|
1947
|
12 Jun 2020 |
Isaac Labrie Boulay | Info | Preparing the VME hardware - VME address jumpers. | > Hi, if you are not using any VME hardware,
then you have no VME address jumpers to
> set. https://en.wikipedia.org/wiki/VMEbus
|
|
|
1640
|
05 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | Today I fixed a long-annoying problem. We
have in each front-end an equipment structure
|
|
|
1642
|
06 Aug 2019 |
Thomas Lindner | Info | Precedence of equipment/common structure | Hi Stefan,
This change does not sound like a good idea |
|
|
1643
|
06 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | Hi Thomas,
the change only affects Eqipment/<name>/common |
|
|
1644
|
06 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | After some internal discussion, I decided
to undo my previous change again, in order
not to break existing habits. Instead, I |
|
|
1656
|
09 Aug 2019 |
Konstantin Olchanski | Info | Precedence of equipment/common structure | > Today I fixed a long-annoying problem. ...
> /Equipment/<name>/Common
> In the past, the ODB setting took precedence |
|
|
1661
|
13 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | > Lacking any ideas for improvements, I vote
for the status quo. (plus a review of the
documentation to ensure we have clearly
|
|
|
500
|
18 Sep 2008 |
Stefan Ritt | Info | Potential problems in multi-threaded slow control front-end | We had recently some problems at our experiment
which I would like to share
with the community. This affects however |
|