On Mon, Jul 28, 2014 at 03:36:29PM +0300, Marius Alksnys wrote:
> I have no idea why, but in my config limit3 works wrong with certain
> maxv and maxa parameters.
I tried to reproduce the behavior you report, but I was not able to.
I tested using the 2.6 branch at 0bc4426 on a computer running 64-bit
Debian 7, compiled with --enable-simulator.
I tested by preparing a hal file with the following contents:
loadrt limit3 count=1
loadrt threads period1=200000
setp limit3.0.maxa 720
setp limit3.0.maxv 1500
addf limit3.0 thread1
start
loadusr halscope
and ran the file with "halrun -I" so that I got the interactive hal
prompt fater running these initial commands.
$ halrun -I marius.hal
In halscope, I selected 2 channels, with channel 0 as limit3.0.in and
channel 1 as limit3.0.out. I triggered on channel 1 falling below 100.
At the halcmd prompt, I first set the "in" pin to 160, waited a few
seconds for the signal to presumably "settle" at 160. Then I set the
"in" pin back to 0.
halcmd: setp limit3.0.in 160
[several seconds pass]
halcmd: setp limit3.0.in 0
At this point, I looked at the scope to see how the "out" signal
behaved. In my test setup, limit3.0.out decreased smoothly from 160 to
0 over about 950ms.
Does my testing procedure sound like your situation? For you, does the
problem occur if you follow my procedure? Perhaps there's some element
missing in my test, or perhaps the difference is due to something else
like Linux version, CPU architecture, or what have you.
Jeff
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
