FYI - I purchased a DoMore CPU, should be here next week. I hope it is as easy as you say it is.
With Do-more you'll want to use Axis mode. No CtrioWB, module is configured through the SysConfig (go to the module config tab), and very little configuration is required there. For what you are doing, you mostly just need to set the pulse output mode...it's very similar to the way workbench works. Once the pulse output is configured, the CTAXCFG instruction will set up the axis, then CTAXTRAP to run a profile. No need to create or load profiles from the WB. Really easy. You'll be glad you did, not only for making CTRIO2 easier, but Do-more is so much easier to use than DL.
You're using Stage, which is a great thing in Do-more. Each program block has its own group of stages, starting with the first stage in the module. You can take a motion sequence and put it in its own program, and then RUN it from $Main (the top level program block). Device-centric instructions like CTRIO instructions have built-in stage transition logic, where you can set them to jump to the next stage in your sequence when they complete. When your sequence is complete, add an EXIT instruction to terminate the program.
It will take you just a little bit to start thinking in Do-more, but once you do, you will really like it. We've seen it over and over.
One more small teaser: The new platform we are developing now has tons of CTRIO2 type functionality built into the bricks...and even far more capable, with true motion functions like axis following, gearing, camming, etc., in addition to basic trapezoid, velocity, jog, home search functions. If you like Do-more with CTRIO2, you're really gonna like the new stuff.
In the mean time, anything else I should try?
Greg, can you offer any more ideas?