why my project can't work? I'm using arduino and sim800l, the matlab gui can't send output to my phone, is there something wrong with my code?

function varargout = Program_Gui_Project(varargin)
% PROGRAM_GUI_PROJECT MATLAB code for Program_Gui_Project.fig
%      PROGRAM_GUI_PROJECT, by itself, creates a new PROGRAM_GUI_PROJECT or raises the existing
%      singleton*.
%
%      H = PROGRAM_GUI_PROJECT returns the handle to a new PROGRAM_GUI_PROJECT or the handle to
%      the existing singleton*.
%
%      PROGRAM_GUI_PROJECT('CALLBACK',hObject,eventData,handles,...) calls the local
%      function named CALLBACK in PROGRAM_GUI_PROJECT.M with the given input arguments.
%
%      PROGRAM_GUI_PROJECT('Property','Value',...) creates a new PROGRAM_GUI_PROJECT or raises the
%      existing singleton*.  Starting from the left, property value pairs are
%      applied to the GUI before Program_Gui_Project_OpeningFcn gets called.  An
%      unrecognized property name or invalid value makes property application
%      stop.  All inputs are passed to Program_Gui_Project_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 Program_Gui_Project

% Last Modified by GUIDE v2.5 18-Oct-2022 11:00:27

% Begin initialization code - DO NOT EDIT
gui_Singleton = 1;
gui_State = struct('gui_Name',       mfilename, ...
    'gui_Singleton',  gui_Singleton, ...
    'gui_OpeningFcn', @Program_Gui_Project_OpeningFcn, ...
    'gui_OutputFcn',  @Program_Gui_Project_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 Program_Gui_Project is made visible.
function Program_Gui_Project_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 Program_Gui_Project (see VARARGIN)

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

% Update handles structure
guidata(hObject, handles);
movegui(hObject,'center');

% UIWAIT makes Program_Gui_Project wait for user response (see UIRESUME)
% uiwait(handles.figure1);
clear all;
global a;
a = arduino('COM4','Uno');
configurePin(a,'D7','DigitalOutput');
configurePin(a,'D8','DigitalOutput');

% --- Outputs from this function are returned to the command line.
function varargout = Program_Gui_Project_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;


% --- 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)

% memanggil menu "browse file"
[nama_file, nama_folder] = uigetfile('*.jpg');

%jika ada nama file yang dipilih maka akan mengeksekusi perintah di bawah
%ini
if ~isequal(nama_file,0)
    % membaca file citra rgb
    Img = imread(fullfile(nama_folder,nama_file));
    % menampilkan citra rgb pada axes
    axes(handles.axes1)
    imshow(Img)
    title('Citra RGB')
    %menampilkan nama file pada edit text
    set(handles.edit1,'String',nama_file)
    
    %menyimpan variabel Img pada lokasi handles agar dapat dipanggil oleh
    %pushbutton yang lain
    handles.Img = Img;
    guidata(hObject, handles)
else
    % jika tidak ada nama file yang dipilih maka akan kembali
    return
end
% --- Executes on button press in pushbutton2.
function pushbutton2_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton2 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil variabel Img yg ada dilokasi handles
Img = handles.Img;

% melakukan konversi citra rgb menjadi citra grayscale
Img_gray = rgb2gray(Img);
%figure, imshow(Img_gray)
% melakukan konversi citra grayscale menjadi citra biner
bw = imbinarize(Img_gray);
% figure, imshow(bw)
% melakukan operasi komplemen
bw = imcomplement(bw);
% figure, imshow(bw)
% melakukan operasi morfologi filling holes
bw = imfill(bw,'holes');
%menampilkan citra biner pada axes
axes(handles.axes2)
imshow(bw)
title('Citra Biner')

%menyimpan variabel bw pada lokasi handles agar dapat dipanggil oleh
%pushbutton yang lain
handles.bw = bw;
guidata(hObject, handles)

% --- Executes on button press in pushbutton3.
function pushbutton3_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton3 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil variabel Img dan bw yang ada di lokasi handles
Img = handles.Img;
bw = handles.bw;

% ekstraksi ciri
% melakukan konversi citra rgb menjadi citra hsv
HSV = rgb2hsv(Img);
% figure, imshow(HSV)
% mengekstrak komponen h, s, dan v pada citra hsv
H = HSV(:,:,1); %hue
S = HSV(:,:,2); % Saturation
V = HSV(:,:,3); % Value
% menambah nilai pixel background menjadi nol
H(~bw) = 0;
S(~bw) = 0;
% menghitung nilai rat2 h,s, danv
Hue = sum(sum(H))/sum(sum(bw));
Saturation = sum(sum(S))/sum(sum(bw));
Value = sum(sum(V))/sum(sum(bw));
% menghitung luas objek
Luas = sum(sum(bw));
% mengisi variabel ciri_latih dengan ciri hasil ekstraksi
ciri_uji(1,1) = Hue;
ciri_uji(1,2) = Saturation;
ciri_uji(1,3) = Value;
ciri_uji(1,4) = Luas;

% menampilkan ciri hasil ekstraksi pada tabel
ciri_tabel = cell(4,2);
ciri_tabel{1,1} = 'Hue';
ciri_tabel{2,1} = 'Saturation';
ciri_tabel{3,1} = 'Value';
ciri_tabel{4,1} = 'Luas';
ciri_tabel{1,2} = num2str(Hue);
ciri_tabel{2,2} = num2str(Saturation);
ciri_tabel{3,2} = num2str(Value);
ciri_tabel{4,2} = num2str(Luas);
set(handles.uitable1,'Data',ciri_tabel,'RowName',1:4)

%menyimpan variabel ciri_uji pada lokasi handles agar dapat dipanggil oleh
%pushbutton yang lain
handles.ciri_uji = ciri_uji;
guidata(hObject, handles)


% --- Executes on button press in pushbutton4.
function pushbutton4_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton4 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil ciri_uji yang ada di lokasi handles
ciri_uji = handles.ciri_uji;

% memanggil model naive bayes hasil pelatihan
load Mdl
% membaca kelas keluaran hasil pengujian
hasil_uji = predict(Mdl,ciri_uji);

% menampilkan kelas keluaran pengujian
set(handles.edit2,'String',hasil_uji{1})



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


% --- 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)

% Hints: get(hObject,'String') returns contents of edit2 as text
%        str2double(get(hObject,'String')) returns contents of edit2 as a double


% --- 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 pushbutton5.
function pushbutton5_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton5 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% mereset tampilan GUI
set(handles.edit1,'String',[])
set(handles.edit2,'String',[])

axes(handles.axes1)
cla reset
set(gca,'XTick',[])
set(gca,'YTick',[])

axes(handles.axes2)
cla reset
set(gca,'XTick',[])
set(gca,'YTick',[])

set(handles.uitable1,'Data',[],'RowName',{'' '' ''})


% --- Executes on button press in pushbutton6.
function pushbutton6_Callback(hObject, eventdata, handles)
global a;
writeDigitalPin(a, 'D7', 1);
writeDigitalPin(a, 'D8', 1);
% hObject    handle to pushbutton6 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)



% --- Executes on button press in pushbutton7.
function pushbutton7_Callback(hObject, eventdata, handles)
global a;
writeDigitalPin(a, 'D7', 0);
writeDigitalPin(a, 'D8', 0);
% hObject    handle to pushbutton7 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

Answer 1

[Walter Roberson]

clear all;

That command is like asking to blow up the bridge you are standing on. You should almost never "clear all" inside a program.

matlab gui can't send output to my phone

I do not see any commands to communicate with your phone.

It is not possible to deploy a GUI to your phone, so you cannot be talking about the GUI as a whole ?

[farhan]

I'm new to matlab, so I don't know much. can you help me regarding the gui?

" I do not see any commands to communicate with your phone."

communication with my phone is in the arduino serial code sir.

[farhan]

or in matlab gui i did wrong coding?

[farhan]

sorry to ask again can you tell me how to use sim800l with gui ?

[Walter Roberson]

communication with my phone is in the arduino serial code

You do not have any arduino serial code. You have code that sets digital two pins on the arduino to either 0 or 1, but there is no obvious connection between that and any phone (and no obvious reason to use two digital pins instead of just one digital pin.)

I'm new to matlab

The command clear all asks for MATLAB to remove all local variables, and to remove the connection between any input parameters and names within the executing function, and to forget any saved persistent variables, and to remove most data structures from memory. The things that clear all does not remove are:

• loaded mex routines
• anything that has been specifically locked into memory
• any local variable of a calling routine (but does remove local variables of the current function)
• any graphics objects -- will not close figures for example
• any global variable

Because of this, clear all should almost never be used inside a program. If you ever use clear all then it should either be at the command line (because you are getting ready to do something completely different, for example), or it should be in a very short script that you have written that helps you clean up the state of MATLAB because you want to effectively re-initialize it.

can you tell me how to use sim800l with gui

You need to send commands to the sim800l. There is an example at

https://www.teachmemicro.com/send-data-sim800-gprs-thingspeak/

[farhan]

sorry sir, i use this code for sim 800l. then I connect to matlab to be used in the gui.

#include <SoftwareSerial.h>

//SIM800 TX Terhubung Arduino D8

#define SIM800_TX_PIN 8

//SIM800 RX Terhubung Arduino D7

#define SIM800_RX_PIN 7

SoftwareSerial serialSIM800(SIM800_TX_PIN,SIM800_RX_PIN);

void setup() {

Serial.begin(9600);

while(!Serial);

//Memulai Komunikasi Serial Arduino dengan SIM800

serialSIM800.begin(9600);

delay(1000);

Serial.println("Program Kirim SMS...");

serialSIM800.write("AT+CMGF=1\r\n");

delay(1000);

//No tujuan SMS (Ganti dengan Nomor Penerima SMS)

serialSIM800.write("AT+CMGS=\"08*********\"\r\n");

delay(1000);

//Isi SMS

serialSIM800.write("Peringatan!!! Ada Manusia!!");

delay(1000);

serialSIM800.write((char)26);

delay(1000);

Serial.println("SMS Terkirim !");

}

void loop() {

}

[farhan]

so i use 2 pins. I was wrong to specify the 1 and 0

[Walter Roberson]

while(!Serial);

//Memulai Komunikasi Serial Arduino  dengan SIM800
serialSIM800.begin(9600);

In C the scope of a while is the first statement after the while, and that first statement might be a block with {}

So that code says to loop until the serial port is ready, and each time it should restart the SIM serial port. It is not at all obvious why you should need to continually restart the SIM serial port. Start once, sure, but repeatedly??

Furthermore, the serial port is considered to be automatically ready on arduino that do not have native USB, so on those devices you would not be readying the SIM at all.

You only use the main serial port to write out status messages, and do not listen to the port for anything coming from the host.

As long as this code is running on the arduino, the arduino will not be running the monitor that is listening for commands from the host, so the arduino would be ignoring any WriteDigitalPin()

Unfortunately due to a lack of comments we cannot tell what you are trying to do.

[farhan]

for now what should i do sir?

[Walter Roberson]

Alice: Would you tell me, please, which way I ought to go from here?

The Cheshire Cat: That depends a good deal on where you want to get to.

Alice: I don't much care where.

The Cheshire Cat: Then it doesn't much matter which way you go.

Alice: ...So long as I get somewhere.

The Cheshire Cat: Oh, you're sure to do that, if only you walk long enough.

...

Which is to say, we cannot advise you in how to achieve your goals until you decide what your goals are and can state them clearly to us. Your next step should be to document your requirements. What pieces of hardware will be involved? What are each of them intended to do? What communications technology is to be used between the pieces?

[farhan]

the hardware involved is arduino uno and sim800L. I want the GUI from Matlab to be able to communicate with sim800l so that the results from sim800l can be sent in the form of sms text

[farhan]

for the sim800l code I use 2 pins that I have shared in the previous comment. I don't know how to code in the Matlab GUI. all i do is just enter the pin

[Walter Roberson]

Where does your phone come into this? Where do the digital pins come into this?

When you use writeDigitalPin() on the MATLAB side, that implies that you are using the default control process on the Arduino that listens for commands from the MATLAB host and executes them on behalf of MATLAB and sends back any responses necessary. But if you are doing that, then you cannot be running your own C or C++ code on the arduino side that is controlling the sim800l .

With some research, I see that AT+CMGF=1 turns on SMS mode, and AT+CMGS=\"08*********\" sets the phone number to 08********* and the writing something followed by char(26) (control-Z) should cause that text to be sent. But one place I find an example, the char(26) is followed by another delay and then by println() to the SIM. The lack of the println() could potentially explain why the phone did not receive an SMS.

[farhan]

so on Gui I don't need to type writedigitalpin?

[Walter Roberson]

I want the GUI from Matlab to be able to communicate with sim800l so that the results from sim800l can be sent in the form of sms text

In order to do that, you would have to figure out the device address of the sim800l on the arduino, and you would have to have the MATLAB host use appropriate commands, probably using https://www.mathworks.com/help/supportpkg/arduinoio/ref/matlabshared.serial.device.html device() and https://www.mathworks.com/help/supportpkg/arduinoio/ref/matlabshared.serial.device.write.html write() .

In that configuration, you would not run a sketch on the arduino: you would use the default device monitor installed by MATLAB, and your MATLAB code would tell the arduino what to do -- "tell the arduino to tell the sim800l to output AT+CMGF=1 " kind of thing.

A non-trivial difficulty with that kind of configuration is that you have very weak control over the delays, so on configurations where delays are significant, the communications might not work properly. And there is no way, in such a configuration, to say "tell the arduino to tell the sim800l to output AT+CMGF=1 and then wait 1 microsecond and then output AT+CMGS=\"08*********\" " -- you can only send one command at a time.

It can be done, except for the problem of getting the timing right. It just is not what would be recommended in such a situation.

What would be recommended in this kind of situation would be to run a sketch fairly similar to what you have now, but have the sketch listen for input from the MATLAB host -- possibly one that contains the text to be transmitted. Then have the arduino sketch talk to the sim800l and then have the arduino send the host an "Okay, did that" kind of response. In this kind of situation you would probably open the arduino with a serial() call rather than an arduino() call.

Answer 2

[farhan]

[farhan]

if the serial port problem is closed, what is the solution sir?

[Walter Roberson]

It is not a problem that instrfind() is reporting some closed serial ports, as it is showing that you have an open serial port for COM28.

It can be a problem if the serial port is already open for other purposes. In that case you can use techniques such as

delete(instrfind(serial'))

[farhan]

[farhan]

now this problem sir, what solution?

[farhan]

I have a new sir problem when the program is running the sms from the dongle modem is not sent. but on the command window sheet "ok".

[Walter Roberson]

I would need to see your new matlab code and any arduino code you have.

[farhan]

function varargout = Program_Gui_Project(varargin)
% PROGRAM_GUI_PROJECT MATLAB code for Program_Gui_Project.fig
%      PROGRAM_GUI_PROJECT, by itself, creates a new PROGRAM_GUI_PROJECT or raises the existing
%      singleton*.
%
%      H = PROGRAM_GUI_PROJECT returns the handle to a new PROGRAM_GUI_PROJECT or the handle to
%      the existing singleton*.
%
%      PROGRAM_GUI_PROJECT('CALLBACK',hObject,eventData,handles,...) calls the local
%      function named CALLBACK in PROGRAM_GUI_PROJECT.M with the given input arguments.
%
%      PROGRAM_GUI_PROJECT('Property','Value',...) creates a new PROGRAM_GUI_PROJECT or raises the
%      existing singleton*.  Starting from the left, property value pairs are
%      applied to the GUI before Program_Gui_Project_OpeningFcn gets called.  An
%      unrecognized property name or invalid value makes property application
%      stop.  All inputs are passed to Program_Gui_Project_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 Program_Gui_Project

% Last Modified by GUIDE v2.5 18-Oct-2022 11:00:27

% Begin initialization code - DO NOT EDIT
gui_Singleton = 1;
gui_State = struct('gui_Name',       mfilename, ...
    'gui_Singleton',  gui_Singleton, ...
    'gui_OpeningFcn', @Program_Gui_Project_OpeningFcn, ...
    'gui_OutputFcn',  @Program_Gui_Project_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 Program_Gui_Project is made visible.
function Program_Gui_Project_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 Program_Gui_Project (see VARARGIN)

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

% Update handles structure
guidata(hObject, handles);
movegui(hObject,'center');

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


% --- Outputs from this function are returned to the command line.
function varargout = Program_Gui_Project_OutputFcn(~, 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;


% --- 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)

% memanggil menu "browse file"
[nama_file, nama_folder] = uigetfile('*.jpg');

%jika ada nama file yang dipilih maka akan mengeksekusi perintah di bawah
%ini
if ~isequal(nama_file,0)
    % membaca file citra rgb
    Img = imread(fullfile(nama_folder,nama_file));
    % menampilkan citra rgb pada axes
    axes(handles.axes1)
    imshow(Img)
    title('Citra RGB')
    %menampilkan nama file pada edit text
    set(handles.edit1,'String',nama_file)
    
    %menyimpan variabel Img pada lokasi handles agar dapat dipanggil oleh
    %pushbutton yang lain
    handles.Img = Img;
    guidata(hObject, handles)
else
    % jika tidak ada nama file yang dipilih maka akan kembali
    return
end
% --- Executes on button press in pushbutton2.
function pushbutton2_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton2 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil variabel Img yg ada dilokasi handles
Img = handles.Img;

% melakukan konversi citra rgb menjadi citra grayscale
Img_gray = rgb2gray(Img);
%figure, imshow(Img_gray)
% melakukan konversi citra grayscale menjadi citra biner
bw = imbinarize(Img_gray);
% figure, imshow(bw)
% melakukan operasi komplemen
bw = imcomplement(bw);
% figure, imshow(bw)
% melakukan operasi morfologi filling holes
bw = imfill(bw,'holes');
%menampilkan citra biner pada axes
axes(handles.axes2)
imshow(bw)
title('Citra Biner')

%menyimpan variabel bw pada lokasi handles agar dapat dipanggil oleh
%pushbutton yang lain
handles.bw = bw;
guidata(hObject, handles)

% --- Executes on button press in pushbutton3.
function pushbutton3_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton3 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil variabel Img dan bw yang ada di lokasi handles
Img = handles.Img;
bw = handles.bw;

% ekstraksi ciri
% melakukan konversi citra rgb menjadi citra hsv
HSV = rgb2hsv(Img);
% figure, imshow(HSV)
% mengekstrak komponen h, s, dan v pada citra hsv
H = HSV(:,:,1); %hue
S = HSV(:,:,2); % Saturation
V = HSV(:,:,3); % Value
% menambah nilai pixel background menjadi nol
H(~bw) = 0;
S(~bw) = 0;
% menghitung nilai rat2 h,s, danv
Hue = sum(sum(H))/sum(sum(bw));
Saturation = sum(sum(S))/sum(sum(bw));
Value = sum(sum(V))/sum(sum(bw));
% menghitung luas objek
Luas = sum(sum(bw));
% mengisi variabel ciri_latih dengan ciri hasil ekstraksi
ciri_uji(1,1) = Hue;
ciri_uji(1,2) = Saturation;
ciri_uji(1,3) = Value;
ciri_uji(1,4) = Luas;

% menampilkan ciri hasil ekstraksi pada tabel
ciri_tabel = cell(4,2);
ciri_tabel{1,1} = 'Hue';
ciri_tabel{2,1} = 'Saturation';
ciri_tabel{3,1} = 'Value';
ciri_tabel{4,1} = 'Luas';
ciri_tabel{1,2} = num2str(Hue);
ciri_tabel{2,2} = num2str(Saturation);
ciri_tabel{3,2} = num2str(Value);
ciri_tabel{4,2} = num2str(Luas);
set(handles.uitable1,'Data',ciri_tabel,'RowName',1:4)

%menyimpan variabel ciri_uji pada lokasi handles agar dapat dipanggil oleh
%pushbutton yang lain
handles.ciri_uji = ciri_uji;
guidata(hObject, handles)


% --- Executes on button press in pushbutton4.
function pushbutton4_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton4 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% memanggil ciri_uji yang ada di lokasi handles
ciri_uji = handles.ciri_uji;

% memanggil model naive bayes hasil pelatihan
load Mdl
% membaca kelas keluaran hasil pengujian
hasil_uji = predict(Mdl,ciri_uji);

% menampilkan kelas keluaran pengujian
set(handles.edit2,'String',hasil_uji{1})



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


% --- 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)

% Hints: get(hObject,'String') returns contents of edit2 as text
%        str2double(get(hObject,'String')) returns contents of edit2 as a double


% --- 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 pushbutton5.
function pushbutton5_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton5 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% mereset tampilan GUI
set(handles.edit1,'String',[])
set(handles.edit2,'String',[])

axes(handles.axes1)
cla reset
set(gca,'XTick',[])
set(gca,'YTick',[])

axes(handles.axes2)
cla reset
set(gca,'XTick',[])
set(gca,'YTick',[])

set(handles.uitable1,'Data',[],'RowName',{'' '' ''})


% --- Executes on button press in pushbutton6.
function pushbutton6_Callback(hObject, eventdata, handles)
global BytesAvail;
global A;
global B;
tx ='ATI';
tx1=char(13);
tx2=char(26);

tx3='AT+CMGS="+6281******';  %You have to replace this with the Receiver's Phone number
tx4='Peringatan!!!Ada Manusia!!';     %This is the msg body
msgbox('Kirim SMS?');
tx5='AT+CMGF=1';
s = serial('COM28', 'BaudRate', 9600); % You have to replace this with your 3G modem's COMport number
fopen(s);
s.Terminator = 'CR';
fprintf(s,'%s', tx); 
fprintf(s,'%s', tx1); 
BytesAvail=s.BytesAvailable;
if(BytesAvail > 0), A=fread(s,BytesAvail,'char'); end
A;
sprintf('%c', A)
%%%%%%%%%%%%%%%Send SMS%%%%%%%%%%%%
fprintf(s,'%s', tx5);
fprintf(s,'%s', tx1); 
fprintf(s,'%s', tx3);
fprintf(s,'%s', tx1); 
fprintf(s,'%s', tx4);
fprintf(s,'%s', tx2);
BytesAvail=s.BytesAvailable;
if(BytesAvail > 0), B=fread(s,BytesAvail,'char'); end
B;
fclose(s)


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



% --- Executes on button press in pushbutton7.
function pushbutton7_Callback(hObject, eventdata, handles)
global a;
clear all;
a = arduino();
playTone(a,'D6',660,.1);
pause(.15);
playTone(a,'D6',660,.1);
pause(.300);
playTone(a,'D6',660,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',660,.1);
pause(.550);
playTone(a,'D6',560,.1);
pause(.550);
playTone(a,'D6',660,.1);
pause(.570);
playTone(a,'D6',380,.1);
pause(.550);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',330,.1);
pause(.300);
playTone(a,'D6',770,.1);
pause(.300);
playTone(a,'D6',660,.1);
pause(.550);
playTone(a,'D6',660,.1);
pause(.550);
playTone(a,'D6',660,.1);
pause(.550);
% hObject    handle to pushbutton7 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

[farhan]

this sir.

[Walter Roberson]

If I understand correctly, you no longer have the sim800l attached to the arduino, and instead have it connected through a USB connector directly to the MATLAB host? And you are no longer running a sketch on the arduino, and are instead using the default arduino monitor installed with the Hardware Support Package ?

If that is correct, then pay attention to the fact that when you communicate with the modem (COM28) you do not have any pauses. I suspect that the pauses are significant. (The pauses were, after-all, the basis for the patent for the Hayes AT command set that is being used by the modem.)

[farhan]

Yes sir, I don't use Arduino, but switch to using a dongle modem

[Walter Roberson]

Okay, then you probably need to put in pause() statements.

[farhan]

How to insert a pause() statement sir?

[Walter Roberson]

fprintf(s,'%s', tx);
delay(1000);
fprintf(s,'%s', tx1);
delay(1000);


function delay(milliseconds)
   pause(milliseconds/1000);
end

[farhan]

no errors, sir, but the sms is not received by the destination number... does the use of the modem affect it, sir? I'm using a 4g modem