Wire: Function Conflict, Static VI Reference

Hello Community,
Sorry if this has already been answered before, but I have spent an hour searching. I am trying to learn a little about using subVIs to clean up my code.
I'm trying to connect a static VI reference of a Gaussian function that I made to the Nonlinear Curve Fit.vi, but I get a broken wire which says "function conflict".
When I create constants for the output of my Gaussian VI and the input of the Nonlinear Curve Fit.vi, they are clearly different classes.
Could someone show me how to edit my Gaussian VI to match the class properly? I'd greatly appreciate it.
Thanks,
-Patrick
Solved!
Go to Solution.
Attachments:
pat_gaussian_fit.vi ‏24 KB
pat_gaussian_fit.vi ‏24 KB

Your model subvi needs a connector pattern that is identical to the template. Start with the template mentioned in the help and only modify the code, not the existing controls and indicators. Simply leave unused terminals disconnect, don't delete them.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

Dump while testing Function- Dynamic type conflict when assigning reference

Hi Gurus,
I have the following checked and activated-
- Function with 1 Ruleset
- The Ruleset containing couple of DBlookup expressions
- Value range
- Decision Table
- Decision tree,
- Procedure call
After I give test data while Simulating the function, I get this dump-
Short text
    Dynamic type conflict when assigning references
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_FDT_DB_LOOKUP==============CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Have I missed something? We are on SAPKA70207.

Hi Carsten,
I couldn't find an OSS note featuring-
"MOVE_CAST_ERROR" "CX_SY_MOVE_CAST_ERROR"
"CL_FDT_DB_LOOKUP==============CP" or "CL_FDT_DB_LOOKUP==============CM01K"
"BUILD_WHERE_CLAUSE_LIMIT"
Raised OSS note.

Unexplained "function conflict"

LV2013 SP1, Win 7
The basic question is... why is this wire broken, and what can I do to fix it?
See this JING: < http://www.screencast.com/t/U3h0MMGe >
I have a record, called an ADDON CONTROLLER RECORD.
The record contains a reference to a VI called an ADDON.
It also contains a reference to a VI called an ADDON CONTROLLER.
The ADDON vi has one terminal, which is an ADDON CONTROLLER RECORD.
My intent here is to open up a copy of the ADDON, and store the reference in the record, which seems to go OK.
I also want to open a copy of the ADDON CONTROLLER, and store the reference in the record, but that results in a broken wire.
The JING shows that, even if I create a new control for the VI RefNum, and paste it into the TypeDef, it still complains of a "function conflict".
Since I just created the refnum type, how can there be a conflict?
I suspect it has something to do with recursion: the VI has a terminal with a cluster, the cluster has a VI RefNum, the RefNum describes a VI with a terminal, the terminal has a cluster, the cluster has a VI Refnum, the RefNum describes a VI with a cluster, etc., etc., etc,
You can see that the help window is screwed up, showing several levels of this.
But how does that result in a "function conflict"?
Can I resolve this, or do I have to keep the Controller RefNums separately?
What are the rules?
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks

CoastalMaineBird wrote:
Can I resolve this, or do I have to keep the Controller RefNums separately?
What are the rules?
I wouldn't worry so much about the rules (I would have expected LV to either freeze or disallow it in the first place) and just avoid recursive data types. If this is the data type you need, keep the VI reference in a non-strict format and cast it to the strict type when you need it. I haven't tried this specifically, but a quick test indicates that you can't use To More Specific Class or Type Cast, but Variant to Data seems to work.
Try to take over the world!

How to access a property in a static vi reference

Hi,
I'm completely new to Labview and I'm working on a project that includes controlling CANalyzer from LabView by an ActiveX control.
In CANalyzer I have a CAPL function that I need to call from LV. The problem is that the function must be created in the onInit event when starting a canalyzer measurement. The only way I have found to create the function is to use a "reg event call back" and create the function in a "static vi reference". This works and I can call the funtion from that vi, but I'm not able to call the function from anywhere else but from the "static vi reference" and since it must be strictly typed I can not add any output connector where I can add a reference.
I've been trying to solve this for thee days now and it's starting to feel hope less.
In VB the complete code would look something like:
    Dim WithEvents gCANApp As CANalyzer.Application
    Dim WithEvents gMeasurement As CANalyzer.Measurement
    Dim gSendFunction As CANalyzer.CAPLFunction
    Dim Y
    Set gCANApp = New CANalyzer.Application
    gCANApp.Open ("C:\...xxxx.cfg")
    Set gMeasurement = gCANApp.Measurement
    gMeasurement.Start
    gSendFunction.Call
   'Measurement OnInit event handler
   Private Sub gMeasurement_OnInit()
       Set gSendFunction = gCANApp.CAPL.GetFunction("MyFunction")
   End Sub
This would work fine since I have a reference to gSendFunction in my main code.
My LV code looks like this:
and my static vi ref looks like this:
What I think I need is a reference to the data thread coming from "GetFunction"
If any one can help me solve this I would be very happy!
Best Regards
Henrik

Hi,
you could add another input to your static vi ref where you input the reference to a reference display element which sits in your other vi (upper image).
Then you could make a signaling value change to the reference display element from within your static vi ref.
In your other vi set up an event structure to detect the value change. In that event close the vi - this will let you have the desired reference as output of that vi.
Regards Florian

RFx Q&A dump SRM 7- Dynamic type conflict when assigning references Q&A

Hello,
We are on SRM 7.0 SP05. When adding a question via the Q&A 'chat' functionality on a published RFx the EP shows the following error: 'Dynamic type conflict when assigning references Q&A'.
Could somebody test if this issue is also occuring on their system?
Anybody has a clue what's causing this?
Kind regards,
Tim

Hello Jay,
Loggings show the following:
15:18:49 DIA 000 100 NLPURCOR AB 0 Run-time error "MOVE_CAST_ERROR" occurred
15:18:50 DIA 000 100 NLPURCOR AB 1 > Short dump "100324 151849 dmzsv719 b_SRM_00 " generated

Static vi reference read indicator values

The objective of my code is to open a separate VI when a certain boolean button is clicked, wait for action from the user, then close the separate VI, and return its values to the main function. I have put a static VI reference in my block diagram, and then two invoke nodes: "FP.Open" and "Run VI". That works fine, but I still haven't figured out how to obtain the values of the indicator from the reference. I thought I might use a Property Node, but I couldn't find the right property to select. Any help? Thanks!

And
if you still want to proceed with the idea of calling by reference, set the invoke node 'Run VI' to wait till complete as 'True'.
Then, place another invoke node after it, for Get Control Values. You will get an array of clusters, each cluster with the control/indicator name string and its value in variant data type.
Process that array of clusters.
Post your code if need further help.
i would support 'Christian's first option, of calling the vi as a sub vi and pass the indicator value as a terminal on the connctor pane.

Wire: class conflict in LABVIEW 7.0 Express

Hello all,
recently, we were upgrading from LABVIEW 6i to LABVIEW 7.0 .
Everything seems to be finde with one exception.
In a VI I use an intensity graph (three dimensional graph). The change
of its properties, in particular some values affecting the intensity
display, is done in a SubVI.
This SubVI gets a reference to the intensity graph as handle. The
corresponding terminal in the SubVI is a RefNum control.
In LABVIEW 6i this was working without any problems but in LABVIEW 7,
it does not work anymore.
I get a broken wire sign (red cross) and the error message
Wire: class conflict .
The online help did not bring much light into that situation. There is
only a somehow hidden hint that the options for the RefNum control
sh
ould be checked.
But what is really wrong there? Should I use anything else as terminal
in my SubVI or is there a particulkar option that needs to be set?
At the moment, the VI server class of the RefNum control is set to
Generic|Generic|Object|Control|Graph|IntensityGraph (copied from mind
at the moment).
Any hints would be greatly appreciated.
Thank you very much in advance and best regards
Gerd

Hi Gerd,
I have had problems in the past with passing control references into subVIs. I had these problems because the strict control reference is often incompatible with a non-strict refnum control, or a strict refnum control of the wrong type. For example, if you have a multi-selection listbox, but you try to wire that control reference to a listbox reference associated with a scalar datatype (single-selection), you will get a wiring error.
The easiest solution for these problems is to right-click on the control reference and choose Create > Control. Then, copy this control into your subVI and use it as the subVI input. I think this will solve your class conflict problems.
If this doesn't work right, let me know and we can talk further...attachi
ng a sample LLB that demonstrates the problem would be helpful.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Constrained optimization - function conflict and error 91?

I am a fresh hand on Labview. I tried to use the constrained optimization approach for curve fitting, which unformately leads to the following errors.
1. "error 91".
I build the objective function (subvi1.vi) using "cno_objective function template.vit". When I tried to run it, an error message "error 91" pups up.
2. "function conflict"
When I tried to link the objective function (subvi1.vi) to the constrained nonlinear optimization block, the link is always broken, saying "function conflict".
Any help and comments are appreciated. Thanks!
Attachments:
subvi1.vi ‏21 KB
main1.vi ‏24 KB

Hey guest,
I checked your VIs and might have a few suggestions for you in using the constrained optimization. First of all error 91 is usually a variant error. It has the following text: "The data type of the variant is not compatible with the data type wired to the type input." I believe you get this error since you don't have any data in the variant in the subVI, so it doesn't know how to translate that into a cluster.
The broken wire you are seeing is due to there not being any connections made on the Connector Pane. To link inputs and outputs of subVIs you need to first configure the Connector Pane by right-clicking on the icon and selecting Show Connector and then wiring the controls and indicators to terminals there. I would suggest checking out the example for this VI, which you can then use for your application. If you open the context help (Ctrl+H) and then hover over the VI you want and then click the detailed help link. This will bring up the help file for this VI. At the bottom there should be a button for Open Example. You could also find it in the Example Finder (Help >> Find Examples)
You mentioned that you are fairly new at LabVIEW, so I wanted to point you toward a good tutorial for beginners called Learn LabVIEW in 6 Hours. This should give you a good general overview of what LabVIEW can do. Please let me know if you have any further questions!
Thanks!
Andy F.
National Instruments

Function issue of Cross-Reference

Hi,
thanks for your attention on this topic.
there is function issue of Cross-Reference.
when click the Cross-Reference after re-installed the software (adobe Framemaker 7.10), the function is not working. please kindly check the screenshots below:
Error message below:
Please help to check this issue.
software: Adobe Framemaker 7.10
System: windows xp sp3
thanks in advance for your support .
Message was edited by: Lu Steven

Fire the error log off to the e-mail address indicated in the error message and then contact Adobe Support.

Error Dynamic type conflict when assigning references in EHP4

Hi Experts,
We are facing problem while customizing application wizard in EHP4.
Based on our requirement, we need to create one more tab named "Notes" to add instructions for applicants while applying for Job. It contains only instruction. To achieve this, we have done below set up.
1. We have created new WD component (WD window), OTR Alias
2. Created one more additional steps in T77RCF_RM_STEP called "Notes" and maintained step 1 information
3. In table T77RCF_RM_SEQ, under Application wizard (employee), we have added notes in sequence 1.
Now our new tab "Notes" is reflecting in application wizard. But while cliking on send application, we are getting error "The following error text was processed in the system GEG : Dynamic type conflict when assigning references".
Error Details:-
u2022     The following error text was processed in the system GEG : Dynamic type conflict when assigning references
u2022     The error occurred on the application server sapgeg_GEG_59 and in the work process 0 .
u2022     The termination type was: RABAX_STATE
u2022     The ABAP call stack was:
Can anybody guide what we are doing wrong?
It would be great help.
Regards,
purnima

Hi Rajasekhar,
     Facing the same issue, can you please let me know how you solved the above issue.
Best Regards,
Laxman

SC BRF WF Dynamic type conflict when assigning references

I have activated the process controlled workflow framework and
activated the SAP provided SC BC set. When I try to create shoppping
cart(while save or check) I get the following short dump.
The URL
https://usil0c20.ca.com:8343/sap/bc/webdynpro/sapsrm/wda_l_fpm_gaf was
not called due to an error.
Note
The following error text was processed in the system CS2 : Dynamic type
conflict when assigning references
The error occurred on the application server usil0c20_CS2_00 and in the
work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: INIT_BRF_TRACE of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: CONSTRUCTOR of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: INITIALIZE_BRF_MSG of program /SAPSRM/CL_WF_BRF_MSG=========CP
Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of
program /SAPSRM/CL_WF_BRF_CONNECTOR===CP
Method: /SAPSRM/IF_WF_RULE_CONNECTOR~EVALUATE of
program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
Method: GET_SCHEME of program /SAPSRM/CL_WF_SCHEME_PROVIDER=CP
Method: GET_PROCESS_SCHEME of program /SAPSRM/CL_WF_CONFIGURATION===CP
Method: CREATE_PROCESS_LEVEL_SEQUENCE of
program /SAPSRM/CL_WF_CONFIGURATION===CP
Method: CREATE_PROCESS_INSTANCE of
program /SAPSRM/CL_WF_PROCESS_MANAGER=CP
Method: CREATE_PROCESS_FORECAST of
program /SAPSRM/CL_WF_APV_FACADE======C

Hi,
The dump either happens because the BRF Object SRM_WF is missing in the system or
in the object SRM_WF at BRF the correct trace class /SAPSRM/CL_WF_BRF_TRACE is not used on it.
thus please check.
Thanks,
Melina

ErroruFF1A Dynamic type conflict when assigning references

hi all,
I have one node ,name is :forloop
under this node ,there is a attribute ,its type is string ,its name is attf
now ,I write code as below in action,but it show a error" Dynamic type conflict when assigning references "
someone can tell me the reason?thanks
data :
        for_loop type ref to if_wd_context_node,
        t_var type standard table of string.
    append 'a' to t_var.
    append 'b' to t_var.
    append 'c' to t_var.
    for_loop = wd_context->get_child_node( name = wd_this->wdctx_forloop ).
   for_loop->bind_elements( t_var ).
thanks

Hi,
   The problem is the internal table you are using is not match with the attribute u created.
Node name : forloop
         Cardinality : 0-n.
         selection   : 0-1
attr name   : attf
Use the below code.
DATA forloop TYPE REF TO if_wd_context_node.
DATA t_var TYPE table of wd_this->element_forloop.
data : wa_tar like line of t_var.
wa_tar-attf = 'a'.
append wa_tar to t_var.
wa_tar-attf = 'b'.
append wa_tar to t_var.
    wa_tar-attf = 'c'.
append wa_tar to t_var.
navigate from <CONTEXT> to <FORLOOP> via lead selection*
forloop = wd_context->get_child_node( name = wd_this->wdctx_forloop ).
forloop->bind_elements( EXPORTING
    new_items            = t_var
Regards.
Ragu.
Edited by: Ragu Prasad on Feb 6, 2009 10:39 AM

Dynamic type conflict when assigning references - Dump

Hi All,
I am getting the dump "Dynamic type conflict when assigning references". In my application I have used a table control inside which I have input field, text view and text edit.
I guess the text edit is creating the issue. The error analysis report is below :
If anyone have any idea about the issue, please help.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_MOVE_CAST_ERROR', was not
     caught in
    procedure "IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", nor was it
     propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    It was tried to assign a reference to a rereference variable using the
    'CAST' operation ('?=' or 'MOVE ?TO').
    However, the current content of the source variable does not fit into
    the target variable.
    source type: "\CLASS-POOL=/1WDA/L0STANDARD\CLASS=CL_TEXT_EDIT"
    target type: "\INTERFACE=/1WDA/VTABLE_CELL_EDITOR"
Information on where terminated
    Termination occurred in the ABAP program "/1WDA/L3STANDARD==============CP" -
     in "IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT".
    The main program was "SAPMHTTP ".
    In the source code you have the termination point in line 2290
    of the (Include) program "/1WDA/L3STANDARD==============CCIMP".
    The termination is caused because exception "CX_SY_MOVE_CAST_ERROR" occurred in
    procedure "IF_WDR_VIEW_ELEMENT_ADAPTER~SET_CONTENT" "(METHOD)", but it was
     neither handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "/1WDA/L3STANDARD==============CP "; its source
     code begins in line
    2034 of the (Include program "/1WDA/L3STANDARD==============CCIMP ".
2265       if va__CONTENT_READONLY is bound and
2266          va__CONTENT_READONLY->IFUR_NW5__CONTROL~_IID <> ifur_nw5_invisible=>_iid_invisible.
2267         IFUR_NW5_SAPTABLECELL~HASCONTENT = abap_true.
2268       else.
2269         IFUR_NW5_SAPTABLECELL~HASCONTENT = abap_false.
2270       endif.
2271     endif.
2272
2273 *    >> ProvideCONTENT
2274
2275     IF mv_CONTENT_READONLY <> va__CONTENT_READONLY.
2276       finalize_adapter( mv_CONTENT_READONLY ).
2277       mv_CONTENT_READONLY ?= va__CONTENT_READONLY.
2278     ENDIF.
2279
2280 *   >> property-Aggregation mv_CONTENT_EDITABLE
2281     DATA va__CONTENT_EDITABLE TYPE REF TO /1WDA/VTABLE_CELL_EDITOR. "#EC NEEDED
2282 *   >> UCA STANDARD|TABLE_CELL|CONTENT_EDITABLE
2283     data adp_uielement type ref to /1WDA/VUIELEMENT. "#EC NEEDED
2284     if mv_CONTENT_READONLY is not bound and
2285        mv_WD_TABLE_CELL_EDITOR is bound.
2286           va__CONTENT_EDITABLE ?= mv_CONTENT_EDITABLE.
2287     IF va__CONTENT_EDITABLE is bound and va__CONTENT_EDITABLE->m_view_element = mv_WD_TABLE_
2288     ELSE.
2289
>>>>>     va__CONTENT_EDITABLE ?= create_by_view_element(
2291                          view_element = mv_WD_TABLE_CELL_EDITOR
2292                          parent       = me
2293     ).

Hi Everyone,
Thanks for your replies.
We raised an OSS call for the same and got the below response.
Dear Customer,
I've analized your actual problem and found out that you are using a notallowed combination of text edit as cell editor within table for
clasical Web Dynpro ABAP rendering. The text edit as cell editor work in701 releases when the lightspeed rendering is enabled. However in case
that you want to used
lightspeed rendering, I would suggest to upgrade on a higher
SP level than SP4 as for technical reason we can only deliver
corrections for Unified Rendering first from SP04.

The DELETE statement conflicted with the REFERENCE constraint "FK_Equipment_Assets". The conflict occurred in database "WorkOrderSystem", table "dbo.Equipment", column 'AssetCode'........can someone give me a solution for this Error.

The DELETE statement conflicted with the REFERENCE constraint "FK_Equipment_Assets". The conflict occurred in database "WorkOrderSystem", table "dbo.Equipment", column 'AssetCode'

ya that's true row is referenced by another table.....but i want the row to referred by another table ,I don't know how to fix it
Actually this is not a C# issue. It is a T-SQl issue.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=transactsql
The above link should be posted.
Per my understanding, first you should
delete the record from the Foreign Table and then after you have to delete the record from the Primary Key table
Hope it helps you.
Best regards,
Kristin
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Static VI reference

When do people actually use the static VI reference? It seems to me that it is only useful if you want to hardcode a vi reference with its location into the code. I can only use it with the call by reference node. Is the static VI reference useful elsewhere? I know how to use it with the call by referene node when it is stictly typed, but when it is not strictly type, I don't know when to use it.
Kudos and Accepted as Solution are welcome!

tst wrote:
I use it for two additional things:
If I want to place a free running subVI into a subpanel or otherwise control it programmatically.
If I want to generate reentrant copies of a VI. The static reference ensure that the VI is in memory (included in the build) and you can then use its name or path property to open the new reference.
Number 2 for me as well. This makes reentrant calls to dynamically called VIs work nicely in EXEs as well. If I just reference a VI by name I need to be sure that that VI is in memory. This use to mean include it in the build in an EXE, and then build the path to it (my.exe\reentrant.vi) and call it. But this means I need to remember to add this to a build ever time I use this VI that calls the reentrant VI. With the static reference, the calling VI knows that the reentrant VI is needed and a dependency so it will be included by the application builder. Then when I need to call it I can get the name from the static reference it self, so again I don't even need to know the name of the VI.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Wire: Function Conflict, Static VI Reference

Similar Messages

Maybe you are looking for