Append Intensity Chart to Report

Hello everybody
I am trying to append an intensity chart to word report generation VI, any ideas to do this? I am thinking about append front panel image to report vi. but it doesn't accept my chart reference.
The idea is to send the picture to report whenever defect is detected by the intensity chart during the test
thank you

You cannot have multiple copies of the Report Generation Toolkit installed to different LabVIEW versions. If you want to use the Report Generation Toolkit in LabVIEW 8.2, you will need to uninstall it from your previous LabVIEW version, then reinstall it to LabVIEW 8.2. If you really need the toolkit installed to multiple LabVIEW versions, there is a workaround outlined in this KnowledgeBase entry, although it's not a complete workaround for the Report Generation Toolkit, since this toolkit is one of the only ones that actually replaces shipping LabVIEW files.
We are currently investigating ways to alleviate the pain of using toolkits with multiple LabVIEW versions. Let me know if you have any other questions.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

Smartforms: Appending Spool o/p(report) to PDF generated by SSF

Dear Murugesh
I have attached the code for Appending Spool o/p(report) to PDF generated by SSF below
Please suggest as i will have 2 finish by this SAT.
(Hint : Under 1 SOrdr there may be several line items==>
The material with ref 2 every line-item either may be configurable(ZPL3) or nonconfigurable(ZA3C)) .
*ENCLOSER TO PACKING LIST
SELECT VBELN POSNR INTO CORRESPONDING FIELDS OF TABLE T_VBAP
                    FROM VBAP
                    WHERE VBELN = SSORD.
*For capturing the o/p pages from ZPL3 and consolidating into table
*T_OTF to get single PDF
LOOP AT T_VBAP INTO T_VBAP.
    ITNO = T_VBAP-POSNR.
SELECT SINGLE * FROM ZPP_PLCMH WHERE VBELN = SSORD
                                 AND   POSNR = ITNO.
   IF SY-SUBRC EQ 0.
     SET PARAMETER ID: 'AUN' FIELD SSORD ,
                        'APO' FIELD ITNO.
     CALL TRANSACTION 'ZPCE' AND SKIP FIRST SCREEN.
     IMPORT A = T_OTF2 FROM MEMORY ID 'MEMID'.
     LOOP AT T_OTF2 INTO T_OTF2.
       APPEND T_OTF2 TO T_OTF.
     ENDLOOP.
     REFRESH T_OTF2.
   ELSE.
*For capturing the o/p pages from ZA3C and Appending
*at the end of the PDF file just created by the above code
    SELECT SINGLE * FROM ZPLH WHERE VBELN = SSORD
                              AND   POSNR = ITNO.
     IF SY-SUBRC EQ 0.
       SET PARAMETER ID: 'AUN' FIELD SSORD,
                        : 'APO' FIELD ITNO.
       CALL TRANSACTION 'ZPNE' AND SKIP FIRST SCREEN.
       IMPORT B = SPOOL_ID FROM MEMORY ID 'MEMID2'.
       CALL FUNCTION 'CONVERT_ABAPSPOOLJOB_2_PDF'
         EXPORTING
           SRC_SPOOLID                    = SPOOL_ID
           NO_DIALOG                      = ''
           DST_DEVICE                     = E_DEVTYPE
          PDF_DESTINATION                = 'LOHP'
        IMPORTING
           PDF_BYTECOUNT                  = BTC
         PDF_SPOOLID                    =
         LIST_PAGECOUNT                 =
         BTC_JOBNAME                    =
         BTC_JOBCOUNT                   =
        TABLES
           PDF                            = T_SPOOL_2_PDF
       EXCEPTIONS
         ERR_NO_ABAP_SPOOLJOB           = 1
         ERR_NO_SPOOLJOB                = 2
         ERR_NO_PERMISSION              = 3
         ERR_CONV_NOT_POSSIBLE          = 4
         ERR_BAD_DESTDEVICE             = 5
         USER_CANCELLED                 = 6
         ERR_SPOOLERROR                 = 7
         ERR_TEMSEERROR                 = 8
         ERR_BTCJOB_OPEN_FAILED         = 9
         ERR_BTCJOB_SUBMIT_FAILED       = 10
         ERR_BTCJOB_CLOSE_FAILED        = 11
         OTHERS                         = 12
       IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
       ENDIF.
ELSE.
       TEXT02 = ITNO.
       MESSAGE I014(ZQOTBANK) WITH TEXT02.
   ENDIF.
ENDIF.
ENDLOOP.
CALL FUNCTION 'CONVERT_OTF_2_PDF'
EXPORTING
    USE_OTF_MC_CMD               = 'X'
ARCHIVE_INDEX                =
IMPORTING
    BIN_FILESIZE                 = BIN_FILESIZE
TABLES
    OTF                          = T_OTF
    DOCTAB_ARCHIVE               = T_DOC
    LINES                        = T_LINES
EXCEPTIONS
   ERR_CONV_NOT_POSSIBLE        = 1
   ERR_OTF_MC_NOENDMARKER       = 2
   OTHERS                       = 3.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
    BIN_FILESIZE                    = BIN_FILESIZE
    FILENAME                        = 'C:\SD6.pdf'
    FILETYPE                        = 'BIN'
    APPEND                          = 'X'
WRITE_FIELD_SEPARATOR           = ' '
HEADER                          = '00'
TRUNC_TRAILING_BLANKS           = ' '
WRITE_LF                        = 'X'
COL_SELECT                      = ' '
COL_SELECT_MASK                 = ' '
DAT_MODE                        = ' '
CONFIRM_OVERWRITE               = ' '
NO_AUTH_CHECK                   = ' '
CODEPAGE                        = ' '
IGNORE_CERR                     = ABAP_TRUE
REPLACEMENT                     = '#'
WRITE_BOM                       = ' '
TRUNC_TRAILING_BLANKS_EOL       = 'X'
IMPORTING
    FILELENGTH                      = BIN_FILESIZE
TABLES
    DATA_TAB                        = T_LINES
FIELDNAMES                      =
EXCEPTIONS
FILE_WRITE_ERROR                = 1
NO_BATCH                        = 2
GUI_REFUSE_FILETRANSFER         = 3
INVALID_TYPE                    = 4
NO_AUTHORITY                    = 5
UNKNOWN_ERROR                   = 6
HEADER_NOT_ALLOWED              = 7
SEPARATOR_NOT_ALLOWED           = 8
FILESIZE_NOT_ALLOWED            = 9
HEADER_TOO_LONG                 = 10
DP_ERROR_CREATE                 = 11
DP_ERROR_SEND                   = 12
DP_ERROR_WRITE                  = 13
UNKNOWN_DP_ERROR                = 14
ACCESS_DENIED                   = 15
DP_OUT_OF_MEMORY                = 16
DISK_FULL                       = 17
DP_TIMEOUT                      = 18
FILE_NOT_FOUND                  = 19
DATAPROVIDER_EXCEPTION          = 20
CONTROL_FLUSH_ERROR             = 21
OTHERS                          = 22
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Thanx
Moni
Message was edited by: md monirujjaman

Hello,
Can you explain the problem in detail plz.
I do see that the logic which was proposed is implemented in code.
please check at various places, in run time the following points:
1. Spool ID exported into ABAP Memory.
2. Contents of the Main OTF IntTab.
3. Conversion of the Spool to PFD.Check whether SUBRC = 0. <b>Un-comment all the Exceptions in your FMs where-ever you make a call in your program.</b>
   If this conversion of Spool to PDF is successful, you can choose "Append" option from the popup.
Hope this helps you. Or if you have any specific query let me know.
Regards, Murugesh AS

Cluster not saved correctly in Append Control Image to Report VI

[LV8 with Windows XP]
I'm using the Append Control Image to Report VI to save the image of a control to Word (the same problem occurs if I save to Excel). This VI seems to work fine with all my controls except clusters. Not all of the contents of the cluster show up in the saved image. I have to expand the edges of the cluster way beyond the cluster contents in order for all the contents to show up in the saved image. Is this a bug? Is there a way to "realign" the contents of the cluster within the boundaries?
George

Hi,
just had a customer with the problem with this cluster picture function and I wrote a little VI that manually gets the picture, resizes it to the cluster and the rest is up to you. The only thing is, that you have to place the "zero point" of the frontpanel in the upper left corner to get the proper image.
For Users who want to upgrade: This issue is fixed with the next LabVIEW release.
Best Regards,
Andreas Pistek
~~~ Logic is a systematic method of coming to the wrong conclusion with confidence ~~~
Attachments:
better picture.vi ‏19 KB

Dundas Chart for Reporting Services in SSRS 2012

We are in the process of upgrading our servers to 2012 and though I find many things about converting or upgrading dundas controls to 2008, I can't find anything about upgrading/converting to SSRS 2012. After converting the development machines to
SQL Server/SSRS 2012 the reports now simply show "The custom Report Item Type DundasChartControl is not installed". The only Dundas Chart installation I can find is for SSRS 2008. Does a 2012 version not exist? Am I supposed to
convert these into Microsoft charts?
Thanks in advance,
Robb Melancon

Hi Robb,
It seems that you are using Dundas Chart Control for SQL Server 2008 R2 Reporting Services not the Dundas Chart Control 2005 that Microsoft has purchased.
Microsoft purchased the license to use Dundas Chart Control 2005 in Reporting Services 2008 and above. Therefore the supported upgrade is from Reporting Services 2005 Dundas Charts to SSRS 2008 (R2) and SSRS 2012 Charts.
If you are using a particular component released by Dundas for SSRS 2008 R2, you won’t be able to upgrade Reporting Services 2008 R2 Reports with Dundas Charts to Reporting Services 2012 Charts.
To confirm this, please check the details of this assembly “DundasRSChart.dll” located under the /Report Server/bin directory.
If the Product Name is “Dundas Chart for Reporting Services 2008 R2”, it indicates that this is a new version of Dundas Chart for SSRS 2008 R2 (i.e. a third party control). If the Product Name is “Microsoft SQL Server”, it indicates that this is the version
that Microsoft has purchased.
In this condition, you have to migrate the DundasRSChart.dll to the SSRS 2012 instance and reference it as the custom assembly in the reports. Please make sure to rename the DLL file so that it won’t replace the native DundasRSChart.dll installed by SQL
Server 2012.
For more information about referencing custom assembly in a report, please see:
Using Custom Assemblies with Reports
Regards,
Mike Yin
If you have any feedback on our support, please click
here
Mike Yin
TechNet Community Support

I can't append control image to report on 1 page with appended text report

I am attempting to create a report which is simply header, experiment information, and two graphs of data. I am using a Easy Text Report and Append Control Image to Report. I have successfully printed out this report, but on two separate pages. The header info is on the first page, and the graphs on the second page. This doesn't seem to be a margins problem, as the header is very brief and the graphs aren't that large either. I would like to make this into a one page report. Any help is greatly appreciated.
Message Edited by csmrunman on 01-15-2010 10:18 AM

Nevermind. I neglected to see the Append Report Text.vi. That solved everything.

Need custom column widths in Append Text Table to Report

I need to print reports with tables of different column widths specified for each column, as the contained fields vary in width from just 3 characters in one column to 40 characters in another. Also we are trying to match the reports generated by a non-labview routine. In the past I have been able to achieve this by editing the Append Table to Report vi, working my way through the inner hierarchy to replace the DBL numeric COLUMN WIDTH control with a DBL numeric array. The innermost vi, Set Table Column Width, assigns the numeric to a property node in a for loop, so the change is simple: replace the scalor with an array and enable indexing on the for loop. Of course, after each Labview upgrade, I've had to go back in and repeat these edits on the overwritten upgraded vi's. This time there is a problem. The new version of this toolkit is object oriented, and disturbing these vi's wrecks the class methods in a way I don't understand (mostly because I've had no dealings with object oriented programming) and which cannot be undone. I recently tried this and after not being able to fix the problem even with phone support, I had to spend the next two days unistalling and reinstalling Labview! I desperately need a way to achieve this functionality without killing the toolkit, which is used (in its original functionality) by another absolutely critical program. PLEASE HELP!
The hierarchy is as follows:
NI report.lvclass:Append Table to Report (wrap)
NI report.lvclass:Append Table to Report
NI Standard report.lvclass:Append Text Table to Report
NI Standard report.lvclass:tables
NI Report Generation Core.lvlibet Table Column Width

There is a highly relevant thread under discussion here:
http://forums.ni.com/ni/board/message?board.id=features&thread.id=429
You may wish to read it and chime in as it is a discussion of LabVIEW's policy (and possible change in policy for the future) concerning the handling of non-palette VIs between LV versions.
Rob Hingle wrote:
> Is that to say NI will not be helping me with this? Pretty disappointing lack of support, seems
> like a terrible idea to go to object oriented if even your own application engineers can't figure
> out such a simple fix. Gotta give NI a huge thumbs down on this one, thanks for nothing.
I doubt that it is a simple fix -- our AEs are generally top notch at figuring out solutions for customers -- if it were simple, my bet is they'd have solved it. Asking an AE to work around a bug is different from asking them to rearchitect the toolkit. You are asking them to add a feature that the new version of the toolkit is not
designed to support. The difficulty in doing this is completely independent of the decision to use LabVIEW classes to implement the toolkit. If any piece of software is not designed with a particular use case in mind, what may be a simple tweak under one design may become a very hard problem under another design.
In your case, the solution is very straightforward: Use the older version of the toolkit. Any time you create a custom modification of the VIs that ship with LV or one of its toolkits, you should make your own copy and have your VIs link against the copy. LabVIEW promises to maintain all the public functionality version over version. Usually we succeed at that. What we do not promise is to maintain our private implementation of that functionality. It is impossible for LabVIEW (or any other software library) to maintain all of its private internal operations while still continuing any development. Using a copy of the original VIs shields you from having to recode your changes every version (something you've already mentioned is a chore) and it guarantees that functionality that you relie upon does not disappear.
I hope you are willing to be understanding of this situation and not hold it against the AEs working on this. They try hard to provide excellent customer service, and spend lots of time inventing custom solutions for our users. This happens to be a situation where the correct fix is not to modify the new toolkit version to do something it wasn't designed to do but to modify your development process so that the problem is solved now and into the future.

Append Control Image to Report stops Source Distribution from working

I have a top level built executeable that calls various external vi's using the "Call by Reference Node" function. This seems to work ok, to a point. An additional point here is this is code that I had running well in LV8.2 and am now trying to get running in LV2010 as there have been some significant changes in LV that have impacted on this project and this has forced me to change things.
The external vi that is called is stored in a "Source Distribution" directory structure, which has been generated via its own project specifications. An examination of the directories and vi's stored at the destination looks like everything should be there.
When it comes to running the vi in the source distribution directory (from the top level built executeable) I get the following error message "Error 1003 occurred at Open VI Reference in Run HTML Report Generation VI LV10.vi->Generate Reports.vi", with the additional suggestion " The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.". So it looks like there is something missing in the "Source Distribution" directories.
Doing as suggested, opening the vi in the "Source Distribution" with the development environment, shows that it has no broken arrow. My suspicion is the development environment is supplying whatever it is missing.
Using the built top level application, using trial and error and using the diagram disable structure, I have narrowed down the location of the problem to an "Append Control Image to Report" sub vi (its from the NI Report menus). Disabling this vi at the level it is called, allows the "Source Distribution" vi to run.  "Append Control Image to Report" is part of a class structure and I must say I have not used class structures so my understanding of their implications is very limited.
If I instead dive into "Append Control Image to Report" vi and disable the vast majority of its diagram (everything in the "No Error" case), the original error pops up again. Bit strange considering there are only controls and indicators and a case statement left.
I would appreciate any suggestions, as this has got me stumped. Hopefully I have made myself clear enough as it is all a bit complicated. Let me know if I haven't. Thanks.
Herbert Niesler

    Hi Caleb,
      "When the VI displays the broken arrow and displays that error in the dialog, does it take you to a particular diagram component? Does the diagram have any broken arrows or something?"...      it doesn't take me to a particular diagram. Is this possible in the RTE? If it is how do I enable it?
   I can follow the chain of broken arrows (front panel only) down to my vi that calls the NIreport vi that is causing the problem. However I am unable to open the NIreport vi's in the RTE, so cannot chase this any further down the call chain.
I have tried opening the offending top level vi (on a network drive) and it opens ok. When I close it, it wants to save some changes which i think might point at where the problem is. The attached file shows the screen shots of the "Explain Changes" window. Hopefully they mean something to you.
       Cheers
                Herbert
Herbert Niesler
Attachments:
Explain Changes.jpg ‏46 KB

Bug in Append Control Image to Report in 8.5?

I am now at an end with this. I seem to have some sort of problem when using the Append Control Image to Report. I have a program that creates two reports. One is a condensed version, the other detailed. Both reports contain JPG images of some front panel displays. For the most part it seems to work except what ever it is doing appears very unstable. The problem seems to center around me trying to include a Multicoulmn Listbox. I create a Reference of it and then run that to my Append Control Image, just like any other image I want to include. If I probe the Reference, it appears to be correct, i.e. the name, etc. all seem right. However, what the image that gets included is a whole different graphic. Some times I will get the listbox, other times nothing at all. If I look in the directory and bring up the images, indeed, if it prints the wrong graphics, it also has created two of the ne that it includes.
Running the same program unmodifed seems to do the same thing, i.e. it always will print the wrong graphic. As I have tried different things to try and skirt the problem, I get different effects.
I have seen the same problem with other graphics as well, not just the listbox, but I can't come up with any hint as to why it does what it does.
Attachments:
LABVIEW_err.jpg ‏18 KB

I have dug into this a little further and it appears this bug has to do with creating two reports at the same time. If I only generate a single report, everything works flawless.
I placed the sections of the code that append data to the reports into a sequence so they would not happen at the same time. This seemed to have some effect, but the reports were still incorrect.
Is LabView just not able to create two reports within a single progeam?
I can work around this by creating just the detailed report for now, but it would sure be nice if there were a way to make it work.

How do I format 1D waveform array to output to intensity chart?

I've tried to modify the "Cont Acq&Graph Voltage-Int Clk.vi" example vi to output to an intensity chart. The problem is the chart only accepts a 2D array of input data, while the DAQmx vis are giving me a 1D array of waveform data. How do I fix this?
Thanks in advance...

Thanks! Here's an example of the first few samples of the data I'm getting, plus the header:
Channels 1
Samples 1000
Date 2006/07/24
Time 13:41:57.315999
Y_Unit_Label Volts
X_Dimension Time
X0 0.0000000000000000E+0
Delta_X 0.000100
***End_of_Header***
X_Value Dev1/ai0 Comment
0.068936
0.028033
0.038671
0.047368
0.053086
0.052326
0.039342

Charts in Report Designer - choosing columns and rows for categories

Hi,
I am trying to create a pie chart in report designer from a data provider which has 4 rows and 4 columns. As a default the chart created is using the 1st row for data and the four columns as categories.I want the pie chart to use the first column for categories and 2nd column for data. How do I change the default chart behaviour?
Best regards,
Jai

Hi Jai,
take a look at:
"Class 1 Chart Types" in http://help.sap.com/saphelp_nw04s/helpdata/en/c9/08533b97037963e10000000a114084/frameset.htm
Link is regarding WAD web item but editing is the same in Report Designer.
Here you will get information with example query for editing pie charts and what is possible or not.
like:
Structure of the Data Provider for a Pie Chart
In a pie chart, the underlying table has only one row. The values in the columns form the pie segments.
If the table contains more than one row, the additional rows are ignored when the table is converted into a chart. However, you can define which row is to be used (see below).
Additional the link describes how to build the query for your requirement.
Regards
Andreas

How can i specify pixels in the intensity chart ?

Hi,
I want to specify the number of pixels in the intensity chart . I have 56 values that want to be displayed . How can i do that? .
Solved!
Go to Solution.

Hi jerryvdk,
By specifying the Number of Pixels, do you mean allowing only a specific Plot Area Size for the chart itself?
You can modify this through the use of a Property Node.
Steps to Change the Plot Area Size:
Right click on the Intensity Chart.
Scroll through Create » Property Node » Plot Area » Size » All Elements.
This will create a Property Node which will allow you to change the draw area property of the Intensity Chart.
By specifying a draw area of 56x1, this would allow a 56px draw area size. Is this what you meant?
Alex Thomas, University of Manchester School of EEE LabVIEW Ambassador (CLAD)

Invert Axis in a Chart with Report designer

Hi Gurus
Do you know the proccess or option to change (invert) the axis in a chart with Report Designer or in a table with Query Designer?
Regards
Jose

Hi Jose,
I guess this will help you...
Check here.....
Rotating Charts
Use
You can change the angle of the first segment of a pie chart, doughnut, polar chart, radar chart or split pie chart, thus rotating the chart clockwise.
Procedure
1. Select the property ® Starting angle.
2. Enter the number of degrees by which you want to rotate the circle or rings clockwise.
The first category at the top of the diagram begins with zero degrees, and the one at the bottom begins with 180 degrees.
Regards,
Vijay.

Intensity Chart confused when changing number of samples

My application uses an Intensity Chart in strip chart fashion, adding one column of data points per cycle. Sometimes the user, while configuring an experiment, may change the number of data points per cycle. This of course changes the Y scale on the chart. Autoscale handles that without difficulty. But the intensity chart display sometimes doesn't. Let's say the user changed the number of data points per cycle from A to B, B > A. Some fraction of the time, after the change, the intensity chart will display only A many points in the column, leaving the upper portion of the column black.
It seems to be a "bad state" thing. While the chart is in a good state,you can change the number of data points and things keep on working fine. But once it gets in a bad state, it stays that way, and the number of data points it will actually display is the smallest number of data points per cycle that it has ever dealt with, once it got in the bad state. Clearing the data history will not get it out of the bad state. Only stopping and restarting the program will.
Is this issue known? Has anyone found a way to work around it?
Thanks,
Ken

Hi Ken,
Thanks for using the NI Forums. Intermittent issues are always the fun ones! In order to help me fully understand the issue, would you be able to post some screen shots of what you are seeing (maybe one when it is working properly and one when it didn't)? That will just help me frame the issue so we can figure this out!
Looking forward to hearing back from you!
Dan T.
Dan T.
National Instruments

Appending orbit plots to report

Hey everyone,
I have been having issues appending images of orbit plots and polar plots to excel reports that I am generating using the Report Generation Toolkit. Within the report there are multiple orbit plots that I am generating, and the first one is always blank. It seems like no matter what I do I can't get that first one to show any data. If I change the axis label that will show up, but never any data. Only for the first plot though, the rest show up just fine. Also if I append just a generic plot that seems to work just fine, so I don't think it's any issues with the front panel not loading.
Has anybody else ran into this problem? Were you able to fix it?
Thanks and Best Regards,
Ryan
Attachments:
polar_plot.jpg ‏220 KB

Hey Travis,
I am using the Append Control Image to Report block to generate these pictures. So I am sending a reference of the control to the block and the block then puts the image of the control in the excel report. The reason I'm doing it this way is because the plots make it easy to look at only certain orders of the signal, which would be a lot harder to do within excel.
I have an inkling of a feeling that it has to do with the way the plots are set up, they allow you to calculate many different orders and then select which order you want to look at. Well since my report generation process is automated I don't really need to select which plot I want to look at because I will only be sending one plot at a time to the report. What I think is happening is the data gets calculated correctly, but when it gets plotted the one order that I want to send to my report never gets selected, so the plot remains blank. I can't really explain to you why its only happening to the first one though.
I am using Labview 2010 with Excel 2007.
Thanks for the help,
Ryan
Attachments:
polar_plot_code.jpg ‏88 KB

Label Frequencies in Octave Intensity Chart

Hi, I show some octave spectrum in an intensity chart. All is fine, but I can not label the y-axis ticks correct with the frequencies. The Y-axis shows only the index.
In the array left I show the correct text for the y-axis.
How can I replace the 0,1,..,10 with "31,5","63",..."16000" ?
Peter
I can not attach a vi? I get the errormessage:
Correct the highlighted errors and try again.
The attachment's IntensityOctave.vi content type (application/force-download) does not match its file extension and has been removed.
Attachments:
IntensityOctave.zip ‏8 KB

Do you mean
But I get only:
I understand MarkerVals[], that at this values of the axis a marker should drawn. But the y axis range is from 0..10 (column index).
I need instead a property MarkerText[] (as string array) to assign the text for the markers.
vi attachment: there are many posts with vi files as attachments.
And if I want drag the snippet back to Labview in a block diagram I get only a text with the link.
And the Snippet Tool changed the Reference "intensity chart" to a control "Intensity Chart 2".

Append Intensity Chart to Report

Similar Messages

Maybe you are looking for