Halscope captures by placing its capture function in a hal thread. In
the halscope gui, you are given no choice; from my read of the source
it's always added at position -1 in the thread which means "at the very
end".
If you want it in a different position, explicitly load the realtime
portion of scope and add it to a thread before loading halscope, as I
did here:
$ halrun
halcmd: loadrt threads
halcmd: loadrt siggen
halcmd: loadrt scope_rt
halcmd: addf scope.sample thread1
halcmd: addf siggen.0.update thread1
halcmd: show thread
Realtime Threads:
Period FP Name ( Time, Max-Time )
1000000 YES thread1 ( 0, 0 )
1 scope.sample
2 siggen.0.update
halcmd: start
halcmd: loadusr halscope
Jeff
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
