ThomasGutzler Posted February 21, 2020 Report Share Posted February 21, 2020 Drop this vim on your block diagram and connect anything that isn't an I32 to the "Type" input and it'll break. Why? Quote Link to comment
JKSH Posted February 21, 2020 Report Share Posted February 21, 2020 (edited) Interesting. Looks like there's some type propagation issue when the Decimal String to Number node is combined with the Negate node: Remove the Negate node and the problem disappears. The issue seems to exist in the LV 2020 beta too. Would you like to post in the beta forum, for the attention of NI R&D enginners? http://www.ni.com/support/beta-program/ (I'm happy to post on your behalf, if you prefer) Edited February 21, 2020 by JKSH Quote Link to comment
Popular Post Francois Normandin Posted February 21, 2020 Popular Post Report Share Posted February 21, 2020 It is not a bug. It should break for any unsigned integers because that's how the "negate" method works. 4 Quote Link to comment
Jimmy Chretien Posted February 26, 2020 Report Share Posted February 26, 2020 (edited) You could use the Type Specialization Structure and perform conversion, U8->I16, U16->I32, U32->I64 and U64->EXT before your String to Number conversion. Edited February 26, 2020 by Jimmy Chretien Quote Link to comment
ThomasGutzler Posted February 26, 2020 Author Report Share Posted February 26, 2020 I'm happy for my vim to break when a uint is wired in. Just didn't realise that's the problem. Thanks for pointing that out Francois Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.