| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
332
|
26 Jan 2007 |
Carl Metelko | Forum | Front end electronics broadcast data over ethernet, can midas read this in | Hi,
the system I'm building will have data
read into the frontend nodes
|
|
|
352
|
26 Feb 2007 |
Stefan Ritt | Info | Fragmented polled events | Fragmented polled events have been implemented
in SVN revision 3625.
Fragmentation is a method of breaking down |
|
|
300
|
05 Sep 2006 |
Konstantin Olchanski | Forum | Forums moved from dasdevpc.triumf.ca to ladd00.triumf.ca | For the record, the MIDAS (& co) forums have
been physically moved from
dasdevpc.triumf.ca to our new server machine |
|
|
1799
|
29 Jan 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Hello!
As you know, the generic MIDAS frontend has
a class driver, device driver, bus driver
|
|
|
1802
|
02 Feb 2020 |
Konstantin Olchanski | Info | Force triggering of idle routine of a frontend | Hi, Giorgio - I think you encountered a fundamental
problem with what to do at the begin of
run. There are two ways of thinking about |
|
|
1805
|
02 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Konstantin,
thank you very much for the explanation.
I already have an idea of how to solve my |
|
|
1806
|
03 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | It is important to note that slow control
readout and sending of midas events are two
separate things. Readout is done as fast |
|
|
1808
|
04 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Stefan,
thank you very much for the clarification.
I knew about the DF_XXX flags and I am making |
|
|
1811
|
07 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | Dear Giorgio,
ok, now I'm slowly getting your point.
|
|
|
1812
|
07 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Stefan,
Thank you for the advice. I will try to modify
the driver as you say. As for the dynamical |
|
|
1813
|
09 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | You dirty hacks will probably work, but what
you REALLY want is to read out your HV always
as fast as possible, not only during run |
|
|
1816
|
10 Feb 2020 |
Konstantin Olchanski | Info | Force triggering of idle routine of a frontend | > We had a case where a detector produced
electrostatic discharges which only lasted
for a second or so
|
|
|
1821
|
12 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | I had a look again at the issue. If you sett
the event limit to zero in the EQUIPMENT
list, then the idle() routine of your class |
|
|
885
|
10 May 2013 |
Konstantin Olchanski | Bug Fix | Fixed: crash if alarm "write elog message" is enabled | If the MIDAS Alarm property "write elog message"
is enabled, an uninitialized variable "tag"
is passed to
|
|
|
948
|
15 Jan 2014 |
Konstantin Olchanski | Bug Fix | Fixed spurious symlinks to midas.log | In some experiments (i.e. DEAP), we see spurious
symlinks to midas.log scattered just about
everywhere. I
|
|
|
118
|
30 Oct 2003 |
Stefan Ritt | | Fixed several potential problems for ODB corruption | I just realized that db_set_value, db_set_data,
db_set_num_values and
db_merge_data do not check for num_values |
|
|
257
|
18 May 2006 |
Stefan Ritt | Bug Fix | Fixed problems with reload of custom pages | We had a problem with custom pages and reloading
of them. If they contain an ODB field which
is editable, one can change the ODB value |
|
|
573
|
07 May 2009 |
Konstantin Olchanski | Bug Fix | Fixed mlogger run start and stop | Fixed problems with mlogger starting and stopping
runs.
|
|
|
1319
|
02 Nov 2017 |
Konstantin Olchanski | Bug Fix | Fixed mlogger memory corruption, updated mxml | I the agdaq system I see memory corruption
in the mlogger. There were at least two bugs:
one
|
|
|
535
|
27 Nov 2008 |
Konstantin Olchanski | Info | Fixed mlogger crash, was Per-variable history implementation in the mlogger | > revision 4142+4143 are minor fixes, refactoring
(switch the code to use helper
> functions) and implementation of history |
|