crossrulz

Well, I'd say you've been lied to on the protocol. Interestingly, all of the bytes (except for the initial byte) are alpha-numeric. If I convert your hex values to ASCII I get: Write: 00P004SOL1 Read: 00D0010 This still means nothing to me. Just thought I would go through the exercise in case it sparks someone's thought process.

That manual also mentions "included cables". You might want to ohm out that cable to see where pins are actually going.

1. Make sure you are actually following the protocol of the UPS. What is the model? Do you have a link to the programming manual (might also be in the User Manual)? 2. If you send a binary string to the UPS, I almost guarantee it will not spit back "120.0V". It has a protocol defining the message format. Since you are getting no data back, I am left to assume you are sending an invalid command. Though, it is also possible the UPS is using a different pinout than you expect for the RS-232 connection.

Since it look like you are sending binary data, you really should turn off the termination character at the VISA Configure Serial Port (Boolean input on the top). Then you need to read using the protocol of the device. This should involve reading a start byte, message ID, data, a checksum of some type.

I'm also a TI guy. The TI-83 was the recommended calculated in high school, but I already had a TI-82. The only real difference was the handling of unreal numbers. I had to do some special programing to handle i in my Pythagorean Equation program. In college, it was the TI-89. I used to have all kinds of programs I wrote/distributed, including one I wrote that was to handle an entire exam for one class. I think they are long gone now. I still have both calculators, but I usually end up using the TI-89 emulator on my phone.

No. It is more like they just use the same library on the back end. But a Map is not going through a conversion to a variant first.

Those are the same as what is default in LabVIEW 20XX. They were chosen by Darren specifically to only have to type with the left hand. I remember being part of the discussion to remove it. I thought it was supposed to turn into a right-click option on the run arrow.

My understanding is that the Linx Toolkit will be available in the professional LabVIEW 2020. But that hasn't been released yet (hopefully mid-May).

Will this be recorded? I will attempt to attend, but have appointment that will likely cover the first half.

To be a little more obvious: LVOOP Interfaces

It is C# for now. There are talks for making G interfaces for scripting. It is just not a priority last I heard. Admittedly, it has been probably a year since I heard that discussion.

Interesting part to me is any mention of the virtual event they were planning in May as an initial NI Week replacement has been removed.

I have heard directly from NI that there are no plans to delay the releases that were planned for NI Week being in May. So I would expect the virtual event planned instead of NI Week in May will have all of the normal product announcements we would normally have in NI Week keynotes.

Your best bet is to put your request here: NI Forums - Version Conversion

I just set the display for my controls to something like "%#pHz". The %p sets the display mode to SI Notation, which uses the prefix.

So what I am gathering here is that the Assert Floating-Point Numeric Type.vim does not work with units. Otherwise, it does look like the timestamp case for the Scaler To String.vim is the first one that would work with a numeric, even with units (just feeds into a Format Into String). I'm so glad I gave up on using units ~13 years ago... EDIT: Daren posted right when I was about to hit "Submit".

Crosspost on the dark side: https://forums.ni.com/t5/LabVIEW/How-to-solve-this-kindly-help/m-p/4004765#M1144354

I often just use "x". Curious where that puts me...

When not doing TestStand, I tend to use something similar to a Queued Message Handler. Possible commands to a module/actor are the public interfaces in a library while the queue/event/etc are stored in a private Action Engine.

So you just want the missing elements?

You get that with any error. What I found is I had to make sure the installer was "Run As Administrator".

That's too complicated. Just wire the 3 to the Length and leave the Index unwired. Delete From Array will default to deleting from the end.

You are mixing definitions of "Hex String". It appears you need a raw/binary/flat data string. So replace the Number To Hexidecimal String with a Flatten Into String. The Number To Hex String converts into an ASCII text, which you do not want. Further, since you only want 4 hex character (ie 2 bytes), you need to add a U16 conversion bullet after the multiplication.

There also appears to be A LOT of interaction between things. If I disable the Value Property Node, the User Event gets into the same realm as the Notifier and Queue. Removing the channels makes it even more the similar. Maybe the Queue Status in every single VI is doing something?

You will likely need a write (to request the data) and a read (to get the data) for each slave.