Jump to content
Sign in to follow this  
Taylorh140

Will statecharts survive to move to nxg?

Recommended Posts

I have to admit I've never gotten to use the state-chart module on a project, but I've always wanted too. I really enjoyed it when i evaluated it, but i worry it wont be available to nxg users... ever. Of course I can hope that it will be re-tooled and better than ever on nxg. What do you guys think will happen?

Share this post


Link to post
Share on other sites

We used it in a few projects, but the biggest one which had lots of state charts became really slow to deploy. This made our workflow quite inefficient, as each time we wanted to update and test some code on a cRIO we'd need to spend ages waiting for the state charts to deploy (even if we haven't changed anything in the state charts or their VIs). The module's implementation doesn't scale well.

From what I've seen, the State Chart module isn't that popular in Current-Gen LabVIEW. I think it's unlikely the module will migrate to NXG, not without being re-designed from scratch.

Share this post


Link to post
Share on other sites
9 hours ago, MarkCG said:

I actually think it has survived in a certain form--- it looks like statecharts are used in programming the new functional safety cRIO modules 

http://www.ni.com/white-paper/53844/en/

That looks nice! It makes the safety logic easier to implement and understand.

It's nothing like the LabVIEW State Chart Module, however: "With state diagrams featuring up to eight individual state machines per module, you can complete your programming. You can use AND, OR, and NOT logic along with programmable timers to determine when to transfer between the various states. In addition, you can assign up to 24 Boolean variables. After you download the safety logic onto the module, you can monitor AI, DI, DO, variables, and diagnostics in the LabVIEW Real-Time Module." There are no VIs involved at all.

Share this post


Link to post
Share on other sites
On 10/24/2017 at 10:56 AM, MarkCG said:

I actually think it has survived in a certain form--- it looks like statecharts are used in programming the new functional safety cRIO modules 

 

http://www.ni.com/white-paper/53844/en/

 

 

This is a really nice step in the right direction. It is notable that this kind of development seems easier for developers of nxg than traditional LabVIEW, perhaps they cut out a great deal of development overhead.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Similar Content

    • By Neil Pate
      As seen in the other thread, I am pretty negative about NXG. However I would like to temper this with some things I have seen in NXG which I do like
      Vector based GUI. I don't like the choice of colours, fonts, widgets or pretty much any of the iconography but I do think the switch to vectors is an absolute necessity for a modern application running in high DPI settings. Zoom! I was pleasantly surprised when I accidentally zoomed on the Front Panel. In current gen to get pixel perfect GUIs sometime I find myself resorting to the windows magnifier or dropping down to 1024x768, so being able to zoom is a welcome addition. The helper alignment hints when placing Front Panel controls. Anyone who has used any kind of vector drawing application in the last 5 years will be immediately familiar here. (I am not sure why this is not done when designing a typedef though). The placeholder location for controls and terminals when dropped from the "other" view. No more weird and random location for new controls and terminals! WebVIs. The WebModule is not ready for any heavy lifting, but for basic web pages it currently does the trick. As a LabVIEW developer I really do not want to ever have to learn JS or HTML5 and WebVIs are certainly many steps in this direction (now please port this to current gen!). Now that I know what I am doing I guess I could start from nothing and put together a simple web VI that communicates with something else via a REST API in a couple of hours. The build process turns the VI into a bunch of HTML and JS which you can serve up with any web server. This technology has potential! The panel on the right hand side which can stay open and give you quick access to the properties of controls. It currently pretty ugly and unfriendly to usability with all its greyness, but the concept is quite sound. It can be hidden away when not needed. I am so used to the current gen properties window that it takes me a while to find anything but I expect that to diminish with more use. The icon editor. The default size of the glyphs is much too large but in general this pane gets the job done. At a glance I can see the association of all the terminals. I am not so keen at having Inputs and Outputs as submenu items as this just slows things down a bit, but the concept of showing the user the "direction" of the control is welcome. I have not really used it to create banners and stuff like that yet so I cannot comment too much on that UX. The Build Queue lists about 10 of the last builds which although I did not need in my experimental project I can see how this might be useful. If the build version number could be included in the table this would be most welcome. These bottom pane things can all be collapsed away when not needed which is good. That is about it. My experiment only involved creating a WebVI, so it is possible I have missed some neat things that can be done when developing a traditional desktop application.
      Does anybody have any others to add to this list?
    • By drjdpowell
      If you use Variant handling using the Variant Parsing Library, or use any library that does, please see this conversation, where I learned from AQ that the name in a Variant is never to be supported in NXG, eliminating all sorts of advanced capability.
    • By AutoMeasure
      Hi wire-heads,
      Have any of you started using LabVIEW NXG for real projects?  How finished and stable do you find it?  Also, do you find that it can successfully co-exist with LabVIEW 2015-2017 on the same development machine?
      Thanks very much.   -Joe
    • By smarlow
      I just downloaded and installed LabVIEW NXG.  At first I thought I installed LEGO NXT by mistake...
      All kidding aside, I am just now poking around to see what is there, and there are definitely some things to be thankful for.  Other things...not so much.  Extremely radical changes to the graphics on the palettes and root functions, along with major palette restructuring.  Looks like navigation by sight will have to be learned all over again.
      I will post more thoughts on this thread when I get the chance.  Oh, and manual tool selection is gone, along with the tools palette, if I am not mistaken.


×
×
  • Create New...

Important Information

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