From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error 74 occurred at Unflatten From String

Good afternoon

 

I'm having a TCP communication and I'm obteining this error, I always do it in this way and it never report error. Can it be because i'm trying communicate many datas??

 

Error 74 occurred at Unflatten From String

Possible reason(s):

LabVIEW: Memory or data structure corrupt.

0 Kudos
Message 1 of 18
(7,530 Views)

Hi Cristina,

 

don't you think adding some error handling to your VI will improve its performance (and user experience)?

UnflattenFromString also supports an error output!

 

Are you sure the received string is not damaged/malformed in any way?

 

Btw. why do you name your PNG-file as "jpg"?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 18
(7,529 Views)

The error is due to not wire the error in unflatten from string?

0 Kudos
Message 3 of 18
(7,518 Views)

Hi Cristina,

 

no, the error is due to a malformed received string (as written in the message) - but the error message box is shown due to missing error wires!

 

Again: are you sure the received string is correct in each bit and not malformed?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 4 of 18
(7,514 Views)

cristina.lopez wrote: Can it be because i'm trying communicate many datas??

Not likely.  Can you share where you send the data?  My first thought is that you are not sending that cluster that you have defined in your receiver.  It would help you if those were Type Defined clusters so you can make sure your sender and receiver are looking at the data the same way.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 5 of 18
(7,510 Views)

This is the way that I created the cluster that I'm trying to read then.

0 Kudos
Message 6 of 18
(7,504 Views)

Hi Cristina,

 

again I repeat my question:

Did you make sure the string is exactly the same both on transceiver and receiver?

 

Did you make sure all the components of the cluster are exactly the same?

Did you follow the other suggestion to typedefine your cluster (on both ends)?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 7 of 18
(7,466 Views)

As suggested, use type defs for your cluster. This will most likely resolve your issue. That way you know that both sides are using the same cluster definition. Any variation between your cluster definitions that you are now using will cause this error.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
0 Kudos
Message 8 of 18
(7,460 Views)

Yes, I make sure the string and all components  are the same , I have checked many times, but the error persists.

 

I don't know what may be happen

0 Kudos
Message 9 of 18
(7,443 Views)

1. Check if the connection is established.
2. Check if there are errors when receiving the message
3. Check the size of the received message (first reading) and compare it with the cluster size, based on which you decrypt the message.
4. Are you sure that the data is transmitted cyclically?
5. Identify the cluster as typed. Most likely, you are wrong with the dimensions

Labview 4.0, 5.0, 6.1, 8.6, 2009, 2011, 2012, 2014
If you do not know something, ask me.
0 Kudos
Message 10 of 18
(7,436 Views)