What is your workflow when integrating your Do-more project with C-more project?

[franji1]

Please keep this in mind as well, something we discussed on the AD forum last year. Creating a dummy code block full of MEMCLEAR instructions just to get the export of relatively referenced UDT to work.
https://community.automationdirect.com/s/question/0D5Dp00000VZybGKAT/cmore-import-all-tags-from-brx

I just posted a reply on that Community topic with a feature we added in 2.10.  It does not addresses all the work flow issues, but it helps with this one.

[rlp122]

I'm sure that we would all like longer tag names but that isn't a C-more problem. As far as the integration between Do-more and C-more, it works good enough for me that any improvement to it wouldn't have been on my radar...

One alternative in Do-more is to use User Data Types with well named structure members.  Then create well-named heap-items or good 16 character nicknames for the block/ID element.  Then you can get things like CurrentBatch.CookTimer.Done as a tag name in C-more where you have a BatchStruct UDT with a .CookerTimer TIMER member, and a block of BatchStruct called Batch, with CurrentBatch nickname assigned to Batch0.  Beats the 16 character limit.

This works except if you are using Cmore Micros.  Those don't do UDT's.

[FAHOutdoors]

Q1 Do you utilize Do-more Designer's File->Export->Element Documentation C-more utility, then import them into your C-more project?

100% of the time

Q2 If so, do you do it incrementally as you program your PLC with Do-more Designer and import them incrementally using C-more software
OR do you wait until all the PLC development is done, then have Designer export all the tags all at once, then start working on your C-more HMI by doing a big C-more import?

The process is so iterative for me I'm constantly updating tags incrementally. And I work backwards on a new project, I make the UI in CMore first and then make the PLC logic after, so I'm just giving everything internal tags until I finally get to the point to do the first of many export/imports.

Q3 Is Designer's C-more Export mechanism useful?

INCREDIBLY useful

Q4 What would make the integration between Designer and C-more better?
I like what others have added, though I don't mind updating 2000 tags if I only use a handful like another said
some structures don't seem to import well, the other day I couldn't get SS tags on the CMORE software so I just added them manually. the same thing happens with SDTXX.Week tags. not a big deal but I had to manually input about 45 SDTXX.Week/month/day/second/etc tags. I don't mind having to do that many but I never seem to input them all correctly so I have to go back and troubleshoot and fix things.

[franji1]

Q4 What would make the integration between Designer and C-more better?
I like what others have added, though I don't mind updating 2000 tags if I only use a handful like another said
some structures don't seem to import well, the other day I couldn't get SS tags on the CMORE software so I just added them manually. the same thing happens with SDTXX.Week tags. not a big deal but I had to manually input about 45 SDTXX.Week/month/day/second/etc tags. I don't mind having to do that many but I never seem to input them all correctly so I have to go back and troubleshoot and fix things.

Which C-more driver do you use - the Do-more Built-In or the Do-more Symbolic driver?  If you use both, do you happen to see this issue on just one of the drivers (e.g. it works on Symbolic but not on Built-in)?

[FAHOutdoors]

Q4 What would make the integration between Designer and C-more better?
I like what others have added, though I don't mind updating 2000 tags if I only use a handful like another said
some structures don't seem to import well, the other day I couldn't get SS tags on the CMORE software so I just added them manually. the same thing happens with SDTXX.Week tags. not a big deal but I had to manually input about 45 SDTXX.Week/month/day/second/etc tags. I don't mind having to do that many but I never seem to input them all correctly so I have to go back and troubleshoot and fix things.

Which C-more driver do you use - the Do-more Built-In or the Do-more Symbolic driver?  If you use both, do you happen to see this issue on just one of the drivers (e.g. it works on Symbolic but not on Built-in)?

Always use the one that just says "Do-More Driver Format:" Guess I've never even tried any others now that I think about it.