WaitMonitor trigger

[Ximo Sun]

Hi everyone,

I am testing the function of wait in labscript, my pseudoclock object is a PineBlaster. My code compiles well but always gets stuck at the wait() fucntion being called. No timeout trigger ever being sent. So I try to test all the trigger signal that supposed to send out from the parents device. So my connection table is :

WaitMonitor(

    name="wait_monitor",

    ## Flag that pulses after a wait

    parent_device=pxie_6363, connection="port0/line0",

    ## Counter that monitors the times the above flags goes high

    acquisition_device=pxie_6363, acquisition_connection="ctr0",

    ## Software timed output that retriggers the master pseudolock if the wait hits the timeout

    timeout_device=pxie_6363, timeout_connection="pfi2"

    )

 By defining this waitmonitor, I think I should be able to see a trigger rising signal from port0/line0 everytime we call the function trigger_all_pseudoclocks(), therefore I was expecting to see at least a rising signal at wait() function. But I was able to see any. 

If there any possibility that this is happening? Thanks for all possible suggestions on this problem.

Best,

Ximo

[Ximo Sun]

I have more progress on this, I have successfully get to see the timeout signal, but I really don't know which port I should send to retrigger the master pseudoclock. 

I am using a Pineblaster oject that is based on Digilent Max32.  

Basically I just need to know that is the Ext, Trig part connection for the PineBlaster based master clock to be retriggered. 

[Philip Starkey]

Hi Ximo,

I believe the hardware trigger is INT0, which looks to be mapped to pin 3 of the board. The labelling on the board is pretty bad, so there may be multiple headers that look like they're labelled pin 3. The correct pin 3 is on header J14. See https://digilent.com/reference/microprocessor/max32/reference-manual for more help.

I'd also like to take the opportunity to encourage you to upgrade to the PrawnBlaster: https://github.com/labscript-suite/PrawnBlaster

It is cheaper ($5), has better specs, and has an internal wait monitor meaning you don't need an NI card or a timeout line for retriggering. Given the MAX32 is out of production, we should probably archive the pineblaster and mark it as deprecated.

Let us know how you go!

Cheers,

Phil

[Ximo Sun]

Hi Philip,

That is great information!  The product's manual is a bit messy to read. We tried several ports and it didn't work out. 

We are definitely happy to go with this upgrade soon. 

Thanks for your help!

Best,

Ximo

--
You received this message because you are subscribed to a topic in the Google Groups "the labscript suite" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/labscriptsuite/mnJ8hlZDv10/unsubscribe.
To unsubscribe from this group and all its topics, send an email to labscriptsuit...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/labscriptsuite/3041ed82-c5f6-4b93-9c63-436c248fa9d5n%40googlegroups.com.