Announcement

Collapse
No announcement yet.

Looking for guidance

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Looking for guidance

    We opened a project in a P3-550 to be greeted with (the project was created in V1.10.0.11 (or earlier) and these errors are from 3.5.1.2.

    Click image for larger version  Name:	PAC Ver 1.10.11 WTF.  First Message.PNG Views:	0 Size:	8.7 KB ID:	128672
    and

    Click image for larger version  Name:	PAC Ver 1.10.11 WTF.  Next Message.PNG Views:	0 Size:	29.8 KB ID:	128673

    We opened a backup copy in V1.10.0.11 to check the timer struct Poll__Interval
    The timer struct setup was OK in 1.10.0.11.
    Click image for larger version  Name:	PAC Ver 1.10.11 WTF..PNG Views:	0 Size:	78.3 KB ID:	128674

    I am not asking for a fix/remedy, just a confirmation that something that was fixed in later version will stop this from happening in future versions.
    Release not history list of items that may be related:
    • 3.4.2.2 #3
    • 3.3.0.17 #1
    • 3.2.4.1 #1
    • 3.0.0.31 #9
    I cannot imagine what we could have done to cause this series of errors since the editor handles creating all struct members:
    -- we have a struct member named S32_000001
    -- we have a struct member name containing a period (the period is the struct's member access operator -- not an actual character of the member's tag name)

    This is the project in which we experience all of this!

    I tested this with the 'latest' version that I have. Still get this series of errors.

    [EDIT] We intend to recreate this project using the latest available SW version and a P1-540. I want to avoid any internal corruption that may be present in this project.

    [EDIT] changed target CPU to P1-540 from P1-550
    Last edited by kewakl; 02-26-2020, 08:41 AM.

  • #2
    Sent project to AD tech support

    Comment


    • #3
      Got back a 'repaired' project from tech support.
      It seems that they have a magic SW package that cleaned up whatever happened in our original project. Cool! Thanks.
      I cannot say for sure that it is 100% because we already have the project in a P1-540.

      Comment

      Working...
      X