Jump to content

hooovahh

Moderators
  • Posts

    3,364
  • Joined

  • Last visited

  • Days Won

    268

Everything posted by hooovahh

  1. I have seen others on the forums state that this can be an issue. What are the symptoms of hitting this limit? Should I just set this value on all development machines just in case?
  2. There is an offline help option, but I would much prefer to the more straight forward CHM files. https://forums.ni.com/t5/LabVIEW/Offline-Help-window-in-LabVIEW-2022/m-p/4251163#M1236962 NI's website has many deficiencies that have been well known for years. So the effort to force things to go online, is crazy to me. Maybe trying to drive up network traffic to look better for investors or buyers?
  3. Sorry I can't get them to work either. Sometimes LAVA's servers will do weird things with compression or resizing, and in the process it might strip out the meta data that is the VI file. Once we noticed this, these settings were turned off but it is possible these were back when that was an issue.
  4. NI-XNet is newer then NI-CAN. I believe its first release supported LabVIEW 2010 or so. It really is a superior API with much more flexible features. I cover some of the differences in NI-CAN and NI-XNet in Part 3 of my CAN blog. Part 6 goes into XNet in more detail. Newer CAN hardware support either API, but some old stuff does need to use NI-CAN. One thing you didn't mention was if you installed NI-CAN 17 after installing LabVIEW or not. During the install it will detect versions of LabVIEW installed and add support for it. So if you install NI-CAN then LabVIEW, you won't see the supporting palettes. You can just run the NI-CAN installer again and it will add any missing components. This will add Example Finder examples from the Help >> Find Examples menu, and add the NI-CAN palette, I believe it goes under the Measurement I/O on the functions palette, but I don't have it installed at the moment.
  5. More information is needed. Is this a response to an ISO 15765 request? UDS, KWP2000, etc. Or is this periodically broadcasted frames? If it is UDS or something similar you'll need a CDD file to define how it should interpret the response. If it is a periodic message then a DBC file will define the structure of the data being sent, and what IDs belong to what data. I cover the Signal API and how bits can be interpreted in Part 5 of my CAN blog, and I talk about multi frame messaging in Part 8. If you are trying to reverse the CAN bus without this information, then I suspect you will have a very difficult time. There is an IEEE Float Data Type in the XNet Database editor which uses 4 bytes so it is possible this will do what you want. I'd make a database using the XNet Database editor specifying where in the frame the bits are and try using the conversion API with it. EDIT: Also I think Shaun is incorrect. 2 8 D5 0 0 0 0 B 5 70 I'm unsure what the 2 means but 8 means there are 8 bytes to read and the 8 bytes are D5 00 00 00 00 0B 05 70. 8 bytes is a common payload length for CAN. Double Edit: What are your expected values? I ran them through the IEEE conversion and tried Big/Little Endian but ended up with really large numbers both negative and positive.
  6. Write code that detects if the error is thrown, and if it is then close and reconnect. Honestly that shouldn't happen under normal use so I'm wondering if a reference is closed or lost somehow.
  7. I know right? I was looking for a 2D barcode generator not that long ago which is why I mentioned Darin's post that I found, which I presumed you had seen. I searched the forums a bunch and the only other code I found would send it to a website to get generated. I also saw a semi-hacky method using a Zebra printer API, but I never found that NI post either.
  8. Yeah sorry I haven't heard anything about a BBQ, and won't be attending.
  9. I've been using a few AIs in help for writing things. Professional sounding emails of sensitive subjects, work references, and a few other things to help get past a writing block. Image and animation stuff I see cool new things all the time, but haven't done much myself lately.
  10. Oh I get that you're welcome to post it here, I just wanted to link there so anyone here can see the conversation on the subject that has already taken place.
  11. Very cool stuff. I don't know much about 2D barcode encoding, but how does this differ from the code posted by Darin here? Yours looks more polished, but I didn't know if one encoding is better or if both are the same. My users generally don't care at all and just want something that if they scan types what is in the barcode and it seems my QR Code scanning app works with either.
  12. Thanks I figured the information I had was dated, or incomplete.
  13. If the data is accessible by the VI, I tend to stick with an unbundle. I heard that using a property node forces a switch to the UI thread, and it wasn't clear to me if that wasn't the case for class data or not, so I just avoid them if I can. That is one place that NXG did improve on the design of classes and clusters. A cluster was accessed with a property node like it was a class. This made the conversion from a cluster to a class easier, since the methods to access the data were the same.
  14. I posted my Image Manipulation code over on VIPM.IO https://www.vipm.io/package/hooovahh_image_manipulation/ Here is a video demonstrating some of its functionality, including loading an image into a picture box and manipulating it.
  15. Love it, thanks for the shoutout. There is plenty of room for improvement if you ever want to make this into a more polished API. I could see it reading the column width information, and working with the resizing of them. Thanks for sharing, I know I've seen a few requests for things like this in the past.
  16. I just moved it to Code In Development. I haven't tested this but native TIFF is pretty neat. When you feel development is in a good place you should post your package on VIPM.IO. Then it will show up in VIPM. The process for uploading packages is pretty straight forward, and you can link back to the Git for the source. In my Image Manipulation package there is a Load Image function which accepts TIFF. It also allows you to select which image from within the file if there are multiple in there. This all uses .Net image library and is less native, being restricted to Windows.
  17. Crap, it sure looks like it. I did lots of unit testing, but it didn't test for that apparently. Also note that if Indicies Ascending is true then it has the correct result. Version 3.0.1.15 has this fix on VIPM.IO. Thanks a lot for finding issues like this.
  18. I participated in the 2022 Q3 beta. And I see Christina mentioned preparing for the 2023 Public Beta on March 9th of 2023. Which is a bit odd since the mentioned release date of 2023 Q1 was January 2023, with the last update on the document being March 16th of 2023. I never saw a 2023 beta before it was released.
  19. This idea was implemented. https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Same-Height-of-Unbundle-by-Name-Terminal-Local-Variable/idi-p/1298608 Opening existing code will create bends in wires where there weren't any before.
  20. I just went to 2022Q3 64-bit about a month ago with a fairly basic program. USB cDAQ chassis with DAQmx and XNet on Windows 10. It had several classes, reentrant-ness, subpanels and data logging. I haven't seen any weirdness yet. My next step is to dive in upgrading our Linux RT remote controllers and our sequence editor, and report generation. This is a much larger project and one more likely to find issues.
  21. Thanks, that's it. I couldn't find it because I was searching for Completed ideas, but apparently it was declined. The Type Specialized Structure was in LabVIEW 2016, and was part of my NI Week demo that year. I frantically downloaded the Mac 2016 version, extracted the installer to get the VIM that contained the structure, so I could update my presentation and demo. When it was a Macro it was an XNode behind the scenes, and even the 2017 beta used XNodes. But in the official 2017 release it was its own technology. XNodes and Classes don't work well together, and locking libraries made editing them challenging so it was necessary to be their own thing.
  22. I do love how VIMs came to be. I'm having a real hard time finding it. But there was an idea on the Idea Exchange that there should be a function that can delay any data type, similar to the OpenG Wait which takes an error in and passes it out. Jeff K. posted on the thread saying something like "Oh yeah that is a thing, you just need to use a VIM, here is an example which uses XNodes." It blew my mind. Then in the next release of LabVIEW for the Mac, Jeff K. sneaked in a new VIM on the palette which some high up in R&D didn't know, which had the type specialized structure in it, which was also unreleased. I downloaded that version just to get the VIM and structure. I get the feeling the reason VIMs seemingly came out of nowhere, is that Jeff was pushing for it for years, and then when it was mostly stable he just put it out there to get the public's response. When everyone saw the potential that he also saw in it, R&D put efforts into getting it out there. This is just my speculation from the outside.
  23. I made a separate thread over here for array performance testing.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.