About your question on how to use resets on other modules, the easiest way is to send a clock signal every x divisions of the clock.
For example, let the clock run and on every 4 or 8 clock ticks you send a reset signal as well. Both clock and reset can are the same sort of signals, a trigger (short pulse) or gate (longer pulse) will do.
Depending on the module, the reset input can cause different behavior. This is in my experience often not documented and up to you to figure out.
Some modules like Mutable Instruments Grids (which is a drum sequencer) have the reset input tell the module that the NEXT clock pulse is going to be back on the first step. A typical use-case will be that you send a reset signal when you stop your Beatstep Pro. When it starts again, the module starts on the first step as well. You can also send a reset signal while the clock is running, it will always play nice with the clock as it will tell the module to wait for the next clock and then go back to the first step. I hope this explanation makes sense.
Another way that modules, for example the TipTop Z8000 (a CV sequencer), interpret a reset signal is that the reset input tells the module to set back to the first step AS SOON as the reset gets a signal. This means that if you use the above use-case (send a reset signal when you stop your Beatstep and then start the Beatstep again), the "stop" reset signal will move the module to the first step, and the first hit of the started clock will advance the module to the second step. This basically skips the first step.
Let's say you have a 8-step CV sequencer module (like the sequencer on the DFAM) that uses this type of implementation for the reset in. You don't want a sequence of 8 steps, but instead 4. So you send it a clock and as a reset every 4 clock ticks. What could happen is that it resets to step 1, but because the clock is hitting as the same time as the reset, it will immediately move to step two on the same clock tick.
Your 4-step sequence will not run from step 1 till step 4, but from step 2 to step 5. Highly frustrating.
To test what reset implementation your module has, send a very slow clock and reset to it and see if it skips steps. If it does, Pams has a solution built in to fix this. Head over to the channel that sends the clock to the module, and go the logic option. Select the ^ symbol (stands for Exclusive OR) of the Pams channel that sends out the reset. This will create a clock output that gets muted when the clock channel puts out a signal, effectively skipping the step that hits on the reset.