SerialPort DataReceived Event Read Byte ?

ibrahimayhans

Hello, I would like to ask you to share information on a subject, I am experiencing a problem related to data transmission and data retrieval on an Indicator device connected to a serial port on a project I am developing. Code I Write For Trial Purpose As Below, SerialPortTLB_DataReceived Event Overflow Should Not Send on Textbox as Byte, How can I print the incoming data as Bytes? I'm Waiting For You About This Issue, Good Work ...

using DevComponents.DotNetBar.Metro;
using System;
using System.Windows.Forms;

namespace VeriOkuma
{
public partial class VeriOkuma : MetroForm
{
public VeriOkuma()
{
InitializeComponent();
}

    private void BTNVeriGonder\_Click(object sender, EventArgs e)
    {
        if (!SerialPortTLB.IsOpen)
            SerialPortTLB.Open();
        SerialPortTLB.Write(System.Convert.ToChar(2).ToString() + System.Convert.ToChar(1).ToString() + "DNG" + System.Convert.ToChar(13).ToString());
    }

    private void VeriOkuma\_Load(object sender, EventArgs e)
    {
        if (SerialPortTLB.IsOpen)
        {
            SerialPortTLB.Close();
        }
    }

    private void SerialPortTLB\_DataReceived(object sender, System.IO.Ports.SerialDataReceivedEventArgs e)
    {
        if (!SerialPortTLB.IsOpen) SerialPortTLB.Open();
        TXBGelenVeri.Text = SerialPortTLB.ReadExisting();
        SerialPortTLB.Close();
    }
}

}

Lost User

It all depends on what format the data is in. You need to check the documentation for the device to see exactly what data is presented when you read from it.

ibrahimayhans

Hello, When we contact with the manufacturer company, we inform you as the status on the screen of the device after Char Characters we send. When the Status Letter arrives, the values are sent correctly. After this, SerialPort.Read as specified in the company's total length of 41 bytes is required. SerialPort.ReadExisting () Returns an Incomplete Result. Features SerialPort.Read Read.

Lost User

Assuming you even hooked up the "data received handler", that "handler" in invoked on an "open" port. The "open / close" logic in the handler (and elsewhere) implies that your whole approach is "faulty"; and that "printing a byte" is the least of your problems. You need to (re)read the VS docs for "Serial port". (Unless it's some weird "virtual" port; then you need to refer to those docs).

"(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal

OriginalGriff

ibrahimayhans wrote:

SerialPort.ReadExisting () Returns an Incomplete Result.

Well, yes. It will. Serial data is called that because data arrives one bit at a time - a serial stream of data. When seven or eight data bits have been received (together with all appropriate framing characters such as start, stop, and parity bits) the resulkting byte is passed to the input buffer, and the hardware notifies Windows that it is ready. Windows then reads the buffer content, adds it to an internal circular queue, and sends a message to your app which is translated into a DataReceived event. You handler then gets called and reads the data, however much of it there is. Subsequent bytes cause the same process to occur. You do not get a "I've got all the data" event, you get an "I've got at least one character for you" event instead. If you want to receive the whole message, then you need to buffer it yourself, and process it until you have a complete "message" built up in your buffer before you start looking at it.

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!

ibrahimayhans

I understand State But I am in contact with Producer Company in reply to the query sent in one time 41 byte length is required to be delivered in the value. What Should I Do to Receive 41 Bytes of Data at a Time? Also, SerialPort.Read (byte [] buffer, int, int); Can such an operation be done with this method?

OriginalGriff

You have to buffer them. You will get upto 41 events - you cannot guarantee exactly how many, it depends on what else is going on in your system.

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!

ibrahimayhans

I did not fully understand the Buffering Scheme or I could not. Can I send me the edit code on the code I share in the Read operation?

ibrahimayhans

The Producer Company Specially Says 41-Byte Data Future.

Lost User

So you just need to keep reading until you have all the data. As OriginalGriff points out below, the data does not all arrive at once.

OriginalGriff

No - we aren't here to do all your work for you. If you don't know what you are doing - and it doesn't sound like you have any idea about communications - then you need to start reading and learn, because this is the really easy stuff! If you don't understand what is happening here, nothing else about this job will make any sense, and I will end up doing it all for you. And trust me, I'd have to charge you for doing your work for you! :laugh:

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!

ibrahimayhans

Only the manufacturer of 41 bytes will deliver the future in a single time. If it does not come in one go as you have stated, how can I get it in the order of the results? So how do I get to 8 + 8 + 8 + 8 in order of incoming results?

ibrahimayhans

:) In this case you are right, I've searched too much But I did not do what I did, I believe that if I can at least understand the logic of this, I will be able to do so without any problem. On the Yinede You Are So Glad to Help Me in This Concern?

OriginalGriff

Stop "searching for the solution" and start reading up on how it all works - this is stuff you need to know in order to work with comms effectively.

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!

Lost User

Control.CheckForIllegalCrossThreadCalls = false; Why? :((

Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.

ibrahimayhans

I have used the Thread Function, and now Delete

Lost User

Serial devices present their data in "chunks", and each chunk may be anything from a single byte to a complete message. This is a feature of serial IO that the programmer needs to understand and deal with. Your input routine needs to capture however much data is presented each time, and build the message buffer by appending the latest 'chunk' to whatever has already been read in. When you are certain that you have all the available data you can go and process it. If the manufacturer tells you that you will receive 41 bytes, then you must keep reading until your message has received that number of bytes.

ibrahimayhans

The Problem I'm Having Problem With, What's The Value 8 Bytes Coming Up and How Can I Keep Reading the Restored Values? How Do I Write a Code?

OriginalGriff

Doesn't matter - the DataReceived event is never fired on the UI thread, so you will get an cross thread exception anyway. See what I mean about needing to know this stuff?

Bad command or file name. Bad, bad command! Sit! Stay! Staaaay... AntiTwitter: @DalekDave is now a follower!

Lost User

ibrahimayhans wrote:

How Do I Write a Code?

First you need to understand the problem.

Set an index to the start of your receive buffer
Do
Read some data using the index to position it at the correct point in the buffer
Add the count of bytes read to the offset index
While index < 41
// when the index reaches 41 you have all the data (bytes 0 to 40)