![]() |
|
Din Sync Clock input not working as expected - Printable Version +- XOR Userforum (https://forum.xor.eu) +-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3) +--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6) +---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17) +---- Thread: Din Sync Clock input not working as expected (/showthread.php?tid=268) |
Din Sync Clock input not working as expected - sizemologist - 12-31-2018 Hi, I've managed to slave the NerdSeq to my master clock (Pamela's new workout) using the 'Mod. Slave' mode with no problems (sending a x4 clock and /16 for the reset) and when I start stop the master clock the Nerdseq starts and stops as expected. When I put the Nerdseq in 'Mod. Slave24' mode and send it a x24 clock and a high constant gate for the 'run' signal into the reset and then start the master clock the Nerdseq looks to be permanently resetting. I was expecting the sequence to start running when it received a high run signal and when I press stop the Nerdseq to stop when the run signal went low, then when I restart the master clock the Nerdseq to reset to the 1st step and run again. If I remove the run signal from the reset input then the Nerdseq slaves to it but I then can't get it to start at the 1st step without then stopping all the patterns and the incoming clock and then arming a pattern to begin to play (it doesn't start until it receives the external x24 clock) and then finally starting the master clock again. In other words the 'Mod. slave24' seems to only listen to the clock input and not the reset input. Am I overlooking something? I couldn't find any further details in the manual regarding this. Thanks RE: Din Sync Clock input not working as expected - XORadmin - 12-31-2018 Hey you are correct. The Slave24 is not a DINsync 24 and so doesn't handle the reset input as a run signal. I will implement the DINsync24 mode at some point, for now you need to use without the /RUN/Reset. RE: Din Sync Clock input not working as expected - sizemologist - 12-31-2018 (12-31-2018, 09:41 AM)XORadmin Wrote: Hey you are correct. The Slave24 is not a DINsync 24 and so doesn't handle the reset input as a run signal. Ah ok, thanks for the clarification, I'll get around this for now but good to hear Dinsync24 will be implemented at some point. Happy new year to you! RE: Din Sync Clock input not working as expected - shledge - 01-04-2019 (12-31-2018, 09:57 AM)sizemologist Wrote:(12-31-2018, 09:41 AM)XORadmin Wrote: Hey you are correct. The Slave24 is not a DINsync 24 and so doesn't handle the reset input as a run signal. Invert the gate and it will work. |