Jump to content

Search the Community

Showing results for tags 'gds'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 3 results

  1. I started a topic on the NI GOOP forums today about running out of memory when running the GOOP2 to GOOP3 conversion tool. I pared back my ambitions and got it to finish. However my code is all quite broken so I must not be taking the right approach. Background: We have been developing electronic test systems for radio astronomy receivers and their sub-assemblies since 2005. We started on LabVIEW 7.1 and settled on 8.6.1 with Endevo GOOP 3.0.5 as the production development environment. We did not want to change platforms until the project was through its construction phase. Now it is in operations/maintenance phase and we must, for obvious reasons, move to Windows 7 and therefore a more modern LabVIEW environment. We chose LV2013 as a recent standard to build on. I have 20-30 classes which are shared infrastructure for the different test systems, plus dozens more which implement specific devices or measurement sequences. So I am loathe to rewrite all of this from first principles. Does anyone here have experience with upgrading this scale of project to the latest / best tools to run under LV2013? What is the path of least resistance to get this done as painlessly as possible? What are the gotchas I should look out for along the way? Are there good resources I may have overlooked to help me understand the underlying architectural changes? I've been reading everythign I can find on this forum and the NI GOOP forum for the last few days but I'm still not clear what the implications for my code are with regard to, for example, GOOP2 object references becoming their GOOP3 equivalent. I can add specific examples of what I've found broken if that will help. Thanks so much for reading.
  2. We have released GOOP Development Suite 4.7 The main things are: [*]LabVIEW 2013 support [*]The creation of Property Node methods. [*]UML Modeller fixes for analysing Actor Framework classes Download it from www.symbio.com/goop ...or here: GDS 4.7 LV2010 GDS 4.7 LV2010-64 GDS 4.7 LV2011 GDS 4.7 LV2011-64 GDS 4.7 LV2012 GDS 4.7 LV2012-64 GDS 4.7 LV2013 GDS 4.7 LV2013-64 And here are some videos: GDS(4.5) Features Video Other Videos Contatct goop@symbio.com for questions. Thanks, Lars Persson and Mikael Holmström Symbio Sweden
  3. We have released GOOP Developmente Suite v4.5. Most important feature are: - Support for Actor Framework. Download installers for LV 2010 up to LV2012 and read more : www.symbio.com/goop Contatct goop@symbio.com for questions. Thanks, Stefan Davidsson and Mikael Holmström Symbio Sweden
×
×
  • Create New...

Important Information

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