LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Not enough memory to complete this operation

Hi,

 


@mcduff wrote:

For the hours measurement you need to add a Quotient and Remainder Function before the case structure, otherwise 12 AM and 12 pm will be incorrect.


That's one (of many) reason(s) I prefer the 24 hour (or military) format for any timestamp-string formatting…

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Message 31 of 33
(810 Views)

@GerdW wrote:

Hi,

 


@mcduff wrote:

For the hours measurement you need to add a Quotient and Remainder Function before the case structure, otherwise 12 AM and 12 pm will be incorrect.


That's one (of many) reason(s) I prefer the 24 hour (or military) format for any timestamp-string formatting…


GMT as well.  Then no issues with Daylight Saving time.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 32 of 33
(798 Views)

You have at least 1 for loops that gets it's N from a converted double.

 

If a double is +Inf or NaN for whatever reason, the N (a I32) becomes 2147483647. That will (probably, haven't tested) give you an out of memory on a 32 bit LabVIEW if there's at least 1 auto indexing output.

 

LabVIEW 64 bit will gladly stall your system for minutes to comply, and sometimes succeeds.

0 Kudos
Message 33 of 33
(789 Views)