How can I import a data to constant block that into the different simulink model?

I have a simulink model that its name is gui. And I want to send two data from gui to simulink model'S constant block. How can I do this?

Answer 1

[Birdman]

You should use set_param command as follows:

set_param('gui/Constant','Value','i')
set_param('gui/Constant1','Value','j')

[bayram özmen]

yes ıt worked but scope showed the wrong answer. the constant block is equal to i and j. but scope shows like in figure.Also I want to see scope value when ı pushed the botton in GUI. How can I do this?

[Birdman]

Do this, add a Simulation Pace block to your model to make your model run close to real time clock. Then run the simulation and while the simulation is running, click the button to set the parameters of the constant blocks.

[bayram özmen]

Yes ı did but ıt gave an error like this. Error in S-function 'gui/Simulation Pace': Unable to acquire handle to MATLAB function 'saeroclockpacer'

[Birdman]

Well, can you send me your GUI with its code and your model(export to r2017a)?

[bayram özmen]

function varargout = guide(varargin) % GUIDE MATLAB code for guide.fig % GUIDE, by itself, creates a new GUIDE or raises the existing % singleton*. % % H = GUIDE returns the handle to a new GUIDE or the handle to % the existing singleton*. % % GUIDE('CALLBACK',hObject,eventData,handles,...) calls the local % function named CALLBACK in GUIDE.M with the given input arguments. % % GUIDE('Property','Value',...) creates a new GUIDE or raises the % existing singleton*. Starting from the left, property value pairs are % applied to the GUI before guide_OpeningFcn gets called. An % unrecognized property name or invalid value makes property application % stop. All inputs are passed to guide_OpeningFcn via varargin. % % *See GUI Options on GUIDE's Tools menu. Choose "GUI allows only one % instance to run (singleton)". % % See also: GUIDE, GUIDATA, GUIHANDLES

% Edit the above text to modify the response to help guide

% Last Modified by GUIDE v2.5 30-Nov-2017 16:09:56

% Begin initialization code - DO NOT EDIT gui_Singleton = 1; gui_State = struct('gui_Name', mfilename, ... 'gui_Singleton', gui_Singleton, ... 'gui_OpeningFcn', @guide_OpeningFcn, ... 'gui_OutputFcn', @guide_OutputFcn, ... 'gui_LayoutFcn', [] , ... 'gui_Callback', []); if nargin && ischar(varargin{1}) gui_State.gui_Callback = str2func(varargin{1}); end

if nargout [varargout{1:nargout}] = gui_mainfcn(gui_State, varargin{:}); else gui_mainfcn(gui_State, varargin{:}); end % End initialization code - DO NOT EDIT

% --- Executes just before guide is made visible. function guide_OpeningFcn(hObject, eventdata, handles, varargin) % This function has no output args, see OutputFcn. % hObject handle to figure % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA) % varargin command line arguments to guide (see VARARGIN)

% Choose default command line output for guide handles.output = hObject;

% Update handles structure guidata(hObject, handles);

% UIWAIT makes guide wait for user response (see UIRESUME) % uiwait(handles.figure1);

% --- Outputs from this function are returned to the command line. function varargout = guide_OutputFcn(hObject, eventdata, handles) % varargout cell array for returning output args (see VARARGOUT); % hObject handle to figure % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Get default command line output from handles structure varargout{1} = handles.output;

function edit1_Callback(hObject, eventdata, handles) % hObject handle to edit1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit1 as text % str2double(get(hObject,'String')) returns contents of edit1 as a double input = str2num(get(hObject,'String')); if (isempty(input)) set(hObject,'String','0') end guidata(hObject, handles); % --- Executes during object creation, after setting all properties. function edit1_CreateFcn(hObject, eventdata, handles) % hObject handle to edit1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

function edit2_Callback(hObject, eventdata, handles) % hObject handle to edit2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA) input = str2num(get(hObject,'String')); % Hints: get(hObject,'String') returns contents of edit2 as text % str2double(get(hObject,'String')) returns contents of edit2 as a double if (isempty(input)) set(hObject,'String','0') end guidata(hObject, handles);

% --- Executes during object creation, after setting all properties. function edit2_CreateFcn(hObject, eventdata, handles) % hObject handle to edit2 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows. % See ISPC and COMPUTER. if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor')) set(hObject,'BackgroundColor','white'); end

% --- Executes on button press in pushbutton1. function pushbutton1_Callback(hObject, eventdata, handles) % hObject handle to pushbutton1 (see GCBO) % eventdata reserved - to be defined in a future version of MATLAB % handles structure with handles and user data (see GUIDATA) input1 = get(handles.edit1,'String'); input2 = get(handles.edit2,'String'); i=str2num(input1); j=str2num(input2); set_param('gui/Constant','Value','i'); set_param('gui/Constant1','Value','j'); %plot(ScopeData.time,ScopeData.signals.values);

[Birdman]

Edit the code by {} Code

[bayram özmen]

Sorry, ı did not understand. How?

[Birdman]

On the right top of your comment, there is a pencil symbol. Click on it and you will be able to edit your comment. Then select all of your code and while it is selected, click on {} Code to transform it into a code format.

[bayram özmen]

I will not be able to do,i have to go lesson. can i send tomorrow? Thank you so much for your interest.

[Birdman]

Yeah sure. Have a nice lesson.