News:

  • August 18, 2026, 07:49:39 AM

Login with username, password and session length

Author Topic: Export Element Documention Bug  (Read 9363 times)

davidbgtx

  • Hero Member
  • *****
  • Posts: 215
  • Host be the Most
Export Element Documention Bug
« on: December 06, 2017, 07:00:27 AM »
If you export the element documentation and choose Do-More Driver Format with Struct Fields,
and then import to C-more the String tags don't come in. I found the work-around is to choose just the D0-More driver format (not with struct fields) and the strings import.
Maybe it's Do-More or maybe it's CMore. Just an FYI

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3843
    • Host Engineering
Re: Export Element Documention Bug
« Reply #1 on: December 06, 2017, 11:21:10 AM »
Which C-more driver are you using?  C-more's "Built-in" Do-more driver does NOT support the "with struct fields" import.  The "Symbolic" Do-more driver DOES support "with struct fields".

I believe you can utilize both drivers on the same project.

davidbgtx

  • Hero Member
  • *****
  • Posts: 215
  • Host be the Most
Re: Export Element Documention Bug
« Reply #2 on: December 06, 2017, 11:37:36 AM »
I am using built-in. Have to check this out. Thanks

davidbgtx

  • Hero Member
  • *****
  • Posts: 215
  • Host be the Most
Re: Export Element Documention Bug
« Reply #3 on: December 06, 2017, 11:54:32 AM »
I see why you would use both, stage bits in symbolic not built-in, timers in built-in not symbolic. I wonder if using both drivers will slow things down? Once again thanks

Controls Guy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 3626
  • Darth Ladder
Re: Export Element Documention Bug
« Reply #4 on: December 06, 2017, 12:18:14 PM »
Probably depends on what occurs on the same page and/or is being trended.  I assume the HMI just polls stuff that is either trended or on the current displayed page (why poll stuff you don't need).  If a given page is all one driver or the other, then there shouldn't be a hit.  If it has to use two drivers, then each will have it's own transactions, which will probably be slower than if one could do it all.
I retract my earlier statement that half of all politicians are crooks.  Half of all politicians are NOT crooks.  There.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3843
    • Host Engineering
Re: Export Element Documention Bug
« Reply #5 on: December 06, 2017, 12:52:16 PM »
The Symbolic driver is slower than the Built-In.

HOWEVER, it is "faster" to be smart and use both.  Built-In for all the basic blocks (C, V, D, R, X, Y, SS, SL, CT, T, ...).  But if you need access to structure members like Stages, PID, Drum, User Data Types, heap-items, even user data-blocks of simple types (e.g. your own Alarm block of bits), you have to use the Symbolic driver for those.

Before the Symbolic driver, you had to move any of your non-Built-in values into/out of the Built-In areas every PLC scan (e.g. PID .PV and .SP into/out of R).  But with the Symbolic driver, skip all that and just use MyPID.PV generated by Do-more's "Struct Fields" export, and import that into C-more project, and now you can use that tag in your C-more project.