Announcement

Collapse
No announcement yet.

PAC CopyChar Not copying all characters

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


  • PAC CopyChar Not copying all characters

    S/W 1.7.1(1)
    CPU P3-550 / P3-RS / P3-RS
    F/W 1.1.13.24 / 1.1.13.17 / 1.1.13.17

    I am using CPI/CPO to comm with TDK/Lambda power supply.
    The CPC instruction is NOT copying all characters from the integer array.
    Code:
    CPC 
    (o) Integer Array to String
    Source [PSU_RECV_CHAR]    Destination [PSU_Reply_RETSTRING]
    PSU_RECV_CHAR is AR1US8, 1 Row, 30 Columns
    PSU_Reply_RETSTRING is STR 30 Characters

    In dataview, PSU_RECV_CHAR has 17 contiguous NONZERO characters:
    Code:
    76,65,77,66,68,65,44,71,69,78,54,48,48,45,56,46,53
    which *should* equate to
    LAMBDA,GEN600-8.5
    PSU_Reply_RETSTRING contains
    LAMBDA,GEN600-8
    It is missing the .5 part of the model number.

    I have duplicated the logic used in 4 other PACs with same CPU and FW. They do not exhibit this behavior.
    The only differences that I can think of are:
    [1]The other programs were developed in an earlier version. All of this program was entered using S/W 1.7.1(1)
    [2]This PAC has two P3-RS modules attached.


  • #2
    The only way I have been able to duplicate this is to set the string which I am copying to at 15 characters. This is the default character count, so make sure your PSU_Reply_RESTRING is set to at least 17 characters. Tested with multiple sw versions and the last two firmware versions.

    Comment



    • #3
      Originally posted by techme View Post
      make sure your PSU_Reply_RESTRING is set to at least 17 characters. Tested with multiple sw versions and the last two firmware versions.
      As noted in original post:
      PSU_RECV_CHAR is AR1US8, 1 Row, 30 Columns
      PSU_Reply_RETSTRING is STR 30 Characters
      I have performed stop-mode transfer, gone to stop, then run, changed PSU_Reply_RETSTRING to 31 characters. No luck.

      I will try with a new string tag and a power cycle tomorrow.

      techme, thanks for giving it a try!

      Comment



      • #4
        Restarted PAC. String tag is still truncated.

        Created new string. All characters are copied using new string tag.
        Old string tag is still truncated.(I think that the tag was *created* as a 15 character tag and will not honor the resize to 31)
        Old tag sized to 31 characters, new tag sized to 30 characters.
        Tag database and rung screenshots attached.

        @techme:
        Please humor me a bit.
        Using the noted firmware as original post, create new string tag with 10 characters. Use CPC to attempt to copy 15 characters. It should fail.
        RESIZE the string to the size of the buffer array. It *SHOULD* work.
        Mine fails. It seems that the firmware does NOT resize larger than the original allocated size.
        Last edited by kewakl; 10-08-2013, 08:54 AM.

        Comment



        • #5
          This is actually a display issue in the GUI. It looks like it has already been reported and will be fixed in the next sw release. You can prove it is just a display issue by using a CMPS(Compare String) instruction to compare your tag to the "LAMBDAGEN,600-8.5" to see when they are equal. You will see that the instruction equal bit will be true even though the display only shows LAMBDA,GEN for the string tag you have in the CPC instruction. You can delete the value(53) in the last integer location and initiate the CPC and you will see it go false then put 53 back in and see it go back equal. So it is actually increasing the string tag in the database when it is modified, it is just not displaying correctly.

          Comment



          • #6
            It actually works correctly in the current sw release 1.8.2.1.

            Comment



            • #7
              Thank you for your time and effort!

              On a related issue:
              I am testing on another P3-550 SW 1.7.1(1) FW 1.1.13.17.
              The CPC instruction is bunching the last couple numbers of the integer array
              Inside the CPC block I see
              [65,66,67,68,69,70,71,72,73,74,75,767...
              I would think that this is also a GUI issue.
              Last edited by kewakl; 10-08-2013, 03:28 PM.

              Comment



              • #8
                Cannot duplicate in 1.8.2.1(current release revision) and 1.1.13.24 ( current fw revision).

                Comment



                • #9
                  I have some issues with v1.8.
                  I lose all dataview tabs when opening a program from a previous version.
                  This program is a new development and I have about 18 well populated tabs in the dataview.
                  The initial save results in a fail message -- what really happens is the save of the dataview tabs fails, but the program seems to be ok.

                  Comment



                  • #10
                    Loss of Dataview Tabs

                    Can you send in your project that you are losing Dataview tabs into tech support? I tried to duplicate this using 1.6 & 1.7 that each have 30 Dataview tabs with several tags each, then open with 1.8, save the project and can not reproduce the issue.

                    Would like to reproduce here so we can get the issue fixed in our next release.
                    Last edited by P3K_ADC_Eng; 10-09-2013, 12:13 PM.
                    If you have an urgent issue, please contact AutomationDirect's Technical Support team.

                    AutomationDirect.com Technical Support: 1(800) 633-0405 or (770) 844-4200 Email Tech Support

                    Comment



                    • #11
                      AD developers have duplicated the 'lost tabs' issue.
                      ADC asked for a sample project that would exhibit this behavior.
                      I sent a project to AD tech support. They duplicated the issue.


                      On the GUI issue...
                      I restarted my laptop, now the original offending tag shows the full string length. I also read the v1.8.0.19 release notes(items 1 and 14) -- It is mentioned there.

                      The other issue:
                      CPC instruction combining the last couple visible array values...
                      [65,66,67,68,69,70,71,72,73,74,75,767...
                      This happens in other instructions that display array data.
                      I have verified in V1.8.2(1) CPA, SRA, FLA, STA

                      Comment

                      Working...
                      X