string
-
char cReceivedChar; is not working (other type expected)
BOOL CSerialPort::Read(void* lpBuf, DWORD dwCount, OVERLAPPED& overlapped, DWORD* pBytesRead)Thanks, MarkHow are you calling the
Read()method?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
How are you calling the
Read()method?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
The first parameter is supposed to be a pointer.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
The first parameter is supposed to be a pointer.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
char *cReceivedChar; while(port.Read(cReceivedChar, 1, overlapped, &dwBytesRead))Thanks, MarkBut then you'd have to allocate one byte of memory from the heap (i.e.,
cReceivedChar = new char). Why not just use this instead:char cReceivedChar;
while(port.Read(&cReceivedChar, 1, overlapped, &dwBytesRead))
...
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
But then you'd have to allocate one byte of memory from the heap (i.e.,
cReceivedChar = new char). Why not just use this instead:char cReceivedChar;
while(port.Read(&cReceivedChar, 1, overlapped, &dwBytesRead))
...
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
yep, it seems to be better to use a reference. with this procedure my string output is only "0.1922" remember incoming: 924.09,-4.06,676.26,0.156488,-0.653856,-0.714853,-0.192273 It looks like that the first values running through the digits in the dialog..mmh?? Is this so complicate to give out the full string? Thanks, Mark
-
yep, it seems to be better to use a reference. with this procedure my string output is only "0.1922" remember incoming: 924.09,-4.06,676.26,0.156488,-0.653856,-0.714853,-0.192273 It looks like that the first values running through the digits in the dialog..mmh?? Is this so complicate to give out the full string? Thanks, Mark
macmac38 wrote: yep, it seems to be better to use a reference. My example was not a reference. It was a pointer, exactly what the
Read()method is expecting. Had it wanted a reference, the signature would look like:BOOL Read(void& lpBuf, ...);
You mentioned that 924.09,-4.06,676.26,0.156488,-0.653856,-0.714853,-0.192273 is arriving at the serial port. How are you verifying this?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
macmac38 wrote: yep, it seems to be better to use a reference. My example was not a reference. It was a pointer, exactly what the
Read()method is expecting. Had it wanted a reference, the signature would look like:BOOL Read(void& lpBuf, ...);
You mentioned that 924.09,-4.06,676.26,0.156488,-0.653856,-0.714853,-0.192273 is arriving at the serial port. How are you verifying this?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
This is the position string from a robot arm and every time the same format. x,y,z shift and quaternion 1-4 I have to extract them later from the string in float variables Thanks, Mark
That's all well and good, but in your original post, you indicated that "This arrives at my serial port," implying that the data is indeed there. That's why I asked how you were verifying it. In the
whileloop that you are using to read the incoming data, how many times does the loop execute? After each call toRead(), what is the value ofdwBytesRead? If the incoming data is always in the same format and is always less than X bytes, you might could use this instead:char received[X];
port.Read(received, sizeof(received), overlapped, &dwBytesRead);
received[dwBytesRead] = '\0';
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
That's all well and good, but in your original post, you indicated that "This arrives at my serial port," implying that the data is indeed there. That's why I asked how you were verifying it. In the
whileloop that you are using to read the incoming data, how many times does the loop execute? After each call toRead(), what is the value ofdwBytesRead? If the incoming data is always in the same format and is always less than X bytes, you might could use this instead:char received[X];
port.Read(received, sizeof(received), overlapped, &dwBytesRead);
received[dwBytesRead] = '\0';
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
received[dwBytesRead] = '\0';what does this line mean? I have "access violation" with this line. Thanks, Markmacmac38 wrote: what does this line mean? It appends a
\0character to the end of the string. macmac38 wrote: I have "access violation" with this line. How big is thereceivedarray, and what is the value ofdwBytesRead?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
macmac38 wrote: what does this line mean? It appends a
\0character to the end of the string. macmac38 wrote: I have "access violation" with this line. How big is thereceivedarray, and what is the value ofdwBytesRead?
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
char received[40]; port.Read(received, sizeof(received), overlapped, &dwBytesRead); TRACE( "Bytes read: %d",dwBytesRead); received[dwBytesRead] = '\0'; SetDlgItemText(IDC_SHIFT_X, received);Bytes read: 1Bytes read: -858993460Bytes read: -858993460Bytes read: -858993460 Thanks, Mark -
char received[40]; port.Read(received, sizeof(received), overlapped, &dwBytesRead); TRACE( "Bytes read: %d",dwBytesRead); received[dwBytesRead] = '\0'; SetDlgItemText(IDC_SHIFT_X, received);Bytes read: 1Bytes read: -858993460Bytes read: -858993460Bytes read: -858993460 Thanks, Markmacmac38 wrote: TRACE( "Bytes read: %d",dwBytesRead); Since
dwBytesReadis aDWORD, you'll need to use the%luformat. Nonetheless, ifreceived[]is only 40 bytes, trying to access the -858993460th position, or any value outside of 0-39, is obviously wrong. Check the return value ofRead()beforehand. In your original post, you indicated that 58 characters were being sent to the serial port. You'll need room for that plus one more soreceived[]should be 59 not 40. This is not the root of the problem, however, but will eventually need to be addressed.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
macmac38 wrote: TRACE( "Bytes read: %d",dwBytesRead); Since
dwBytesReadis aDWORD, you'll need to use the%luformat. Nonetheless, ifreceived[]is only 40 bytes, trying to access the -858993460th position, or any value outside of 0-39, is obviously wrong. Check the return value ofRead()beforehand. In your original post, you indicated that 58 characters were being sent to the serial port. You'll need room for that plus one more soreceived[]should be 59 not 40. This is not the root of the problem, however, but will eventually need to be addressed.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
char received[59]; port.Read(received, sizeof(received), overlapped, &dwBytesRead); TRACE( "Bytes read: %lu",dwBytesRead); received[dwBytesRead] = '\0'; SetDlgItemText(IDC_SHIFT_X, received);Bytes read: 1 I donn't know where's the problem? Normaly it seems easy..? Like to solve it today ;-) Thanks, Mark -
char received[59]; port.Read(received, sizeof(received), overlapped, &dwBytesRead); TRACE( "Bytes read: %lu",dwBytesRead); received[dwBytesRead] = '\0'; SetDlgItemText(IDC_SHIFT_X, received);Bytes read: 1 I donn't know where's the problem? Normaly it seems easy..? Like to solve it today ;-) Thanks, Markmacmac38 wrote: I donn't know where's the problem? Are you sure a problem exists? Maybe there was only one byte available to read.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
macmac38 wrote: I donn't know where's the problem? Are you sure a problem exists? Maybe there was only one byte available to read.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
But this Byte output like: j which means no character in it? But the full string is arriving.. if i don't use this line: received[dwBytesRead] = '\0'; the output is: -0.714853,-0.192273jjjjjjjjjjjjjjjjj Thanks, Mark
macmac38 wrote: But the full string is arriving.. How are you verifying this claim? Whct class does the
Read()method belong to? I'm curious if the fourth parameter is being used correctly. If more than one byte is being read, yetdwBytesReadequals 1, something is awfully wrong. It might also be the third parameter, but I've never used theOVERLAPPEDstructure before so I can't say for sure.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)