I've been using the OOP features of LabVIEW for various projects lately and one thing that I struggle with is a clean method to save and recall objects. Most of my design schemes have consisted of a commanding objects which holds a collection of worker objects. Its a pretty simple model, but seems to work for some design problems. The commander and my interface talk to each other and the commander sends orders to his minions in order to get things done. For example, one parrent class might be called "Data Device Collection" and it has a property that is an array of "Data Device" objects. The Data Device object is a parent class and its children consist of various data devices such as "DAQmx Device", "O-Scope Device", "RS-232 Device", etc. When it comes to saving and loading data, the commanding class's "Save" or "Load" routine is called and at that time all of the minions' settings are saved or recalled from disk. My save routine is more-or-less straight forward, although it still requires an overwriting "Save" and "Load" vi. Here is an example: It isn't too bad in that it is pretty straight forward and simple and there also would be no changes to this if the data structure of the class changed at all. It also can save more generalized settings from it's parrent's class which is also a good feature. What I don't like is that it looks essentially the same for each child class, but I'm at a loss on an effective way to move the handling of the save routing into the parent class. The load routine is more problematic for me. Here is an example: Again, the desirability of moving this into the parent class would be awesome. But the biggest complaint here is that I can't maintain my dynamic dispatch input-output requirements because the object that I load is strictly typed. Instead I have to rely on reading the information from the loaded object and then writing that information to the object that exists on the dynamic dispatch wire. I also dislike that unlike my Save Routine, I will need to modify this VI if my data structure of my object changes. Anyway, any input and insight would be great. I'm really tired of writing these same VIs over-and-over-and-over again, and am after a better way to take care of this in the parent class by keeping the code generalized but still maintain the ability to bring back the saved parameters of each of the children classes. Thanks for your time.

Return to Home Page
Toggle navigation

Solutions

Industries

Academic and Research
Aerospace, Defense, and Government
Electronics
Energy
Industrial Machinery
Life Sciences
Semiconductor
Transportation

Product Life Cycles

Design and Prototype
Validation
Production

Focus Areas

5G and 6G Technology
ADAS and Autonomous Driving Testing
Electric Vehicle Test
Lifecycle Analytics
Radar and Electronic Warfare
Space Launch and Exploration
Validation Lab Innovations

See our approach to solutions

Get a Helping Hand

From troubleshooting technical issues and product recommendations, to quotes and orders, we’re here to help.

Products

Software

View All Software

LabVIEW
TestStand
FlexLogger
SystemLink
DIAdem
VeriStand
OptimalPlus GO

Software Suites

LabVIEW+ Suite
HIL and Real-Time Software Suite
Circuit Design Suite

SERVICES

View All Services

Repair Services
Calibration
Training Courses

HARDWARE

View All Hardware

Data Acquisition and Control

Learn About DAQ
CompactDAQ Bundles
Multifunction I/O
Voltage
Digital I/O
Temperature
Sound and Vibration
Current
Strain, Pressure, and Force
CompactDAQ Chassis

Electronic Test and Instrumentation
PXI Instrument Bundles
GPIB, Serial, and Ethernet
Switches
Oscilloscopes
Digital Multimeters
Source Measurement Units and LCR Meters

Wireless Design and Test

Software Defined Radios
RF Signal Generators
Vector Signal Transceivers

Application-Specific Systems

Semiconductor Test System
Power Electronics Test Systems

Accessories

Power Accessories
Connectors
Cables
Sensors

FEATURES

Entry-Level DAQ

RESOURCES

Advisors
Distributors

See all products

PC-Based Systems

Benchtop Measurement and Test

CompactRIO

Distributed Measurement and Control

PXI

High-Performance Test

Software

Systems Engineering Software

Perspectives

Perspectives showcases how NI sees what’s next in the world of test and technology.

View all articles

Charting the Course for Test Development with LabVIEW

LabVIEW remains key in test, promising speed, efficiency, and new features with NI’s investment in core tech, community, and integration.

Read our featured article

Support

Resources

View All Support Resources

Software Downloads
Register and Activate
Product Documentation
Release Notes
Online Training
KnowledgeBase
Code Examples

Request Support

You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required.

Open a service request

Popular Software Downloads

See all Software Product Downloads

LabVIEW

Multisim

Academic Volume License

Popular Driver Downloads

See all Driver Software Downloads

NI-DAQmx
Provides support for NI data acquisition and signal conditioning devices. 
NI-VISA
Provides support for Ethernet, GPIB, serial, USB, and other types of instruments. 
NI-488.2
Provides support for NI GPIB controllers and NI embedded controllers with GPIB ports.

Community

About

My Account

Account

Cart

Solutions
- Back
- Industries
- Academic and Research
- Aerospace, Defense, and Government
- Electronics
- Energy
- Industrial Machinery
- Life Sciences
- Semiconductor
- Transportation
- Product Life Cycles
- Design and Prototype
- Validation
- Production
- Focus Areas
- 5G and 6G Technology
- ADAS and Autonomous Driving Testing
- Electric Vehicle Test
- Lifecycle Analytics
- Radar and Electronic Warfare
- Space Launch and Exploration
- Validation Lab Innovations
- See our approach to solutions
Products
- Back
- Software
- View All Software
- LabVIEW
- TestStand
- FlexLogger
- SystemLink
- DIAdem
- VeriStand
- OptimalPlus GO
- Software Suites
- LabVIEW+ Suite
- HIL and Real-Time Software Suite
- Circuit Design Suite
- SERVICES
- View All Services
- Repair Services
- Calibration
- Training Courses
- HARDWARE
- View All Hardware
- Data Acquisition and Control
- Learn About DAQ
- CompactDAQ Bundles
- Multifunction I/O
- Voltage
- Digital I/O
- Temperature
- Sound and Vibration
- Current
- Strain, Pressure, and Force
- CompactDAQ Chassis
- Electronic Test and Instrumentation
- PXI Instrument Bundles
- GPIB, Serial, and Ethernet
- Switches
- Oscilloscopes
- Digital Multimeters
- Source Measurement Units and LCR Meters
- Wireless Design and Test
- Software Defined Radios
- RF Signal Generators
- Vector Signal Transceivers
- Accessories
- Power Accessories
- Connectors
- Cables
- Sensors
- FEATURES
- Entry-Level DAQ
- RESOURCES
- Advisors
- Distributors
- See all products
Perspectives
Support
- Back
- Resources
- View All Support Resources
- Software Downloads
- Register and Activate
- Product Documentation
- Release Notes
- Online Training
- KnowledgeBase
- Code Examples
- Popular Software Downloads
- See all Software Product Downloads
- LabVIEW
- Multisim
- Academic Volume License
- Popular Driver Downloads
- See all Driver Software Downloads
- NI-DAQmx
- NI-VISA
- NI-488.2
- Request Support
- You can request repair, RMA, schedule calibration, or get technical support. A valid service agreement may be required. Open a service request
Community
About
Contact Us
Account

Home Community Discussion Forums Most Active Software Boards LabVIEW Topic

LabVIEW

Register
·
Login
·
Help

cancel

Turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

Search instead for

Did you mean:

Topic Options

Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Float this Topic for Current User
Bookmark
Subscribe
Mute
Printer Friendly Page

All Forum Topics
Previous Topic
Next Topic

Previous
- 1
- 2
Next

Best practice for saving and recalling objects from disk?

Re: Best practice for saving and recalling objects from disk?

hecmar.arreola

Active Participant

Author

‎09-23-2014 03:22 PM

Options

Mark as New
Bookmark
Subscribe
Mute
Subscribe to RSS Feed
Permalink
Print
Report to a Moderator

I'm still trying to find a better solution for this.

The best solution (IMO) would be if my classes inherited the save and load routines from a parent "Saveable Objects" class that did not require overriding the "Save" and "Load" VIs, but they just "work".

Hmmm.....

0 Kudos

Message 11 of 11

(465 Views)

Previous
- 1
- 2
Next

All Forum Topics
Previous Topic
Next Topic

What do you need our team of experts to assist you with?

Request a quote Find the right product Place an order Get support on a product

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

Thanks!

We'll be in touch soon!