Thread: Problems with VI after integrating into robot project.
View Single Post
  #3   Spotlight this post!  
Unread 15-02-2015, 08:50
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Problems with VI after integrating into robot project.
I'll be happy to look at the VI. You may just be able to post a picture of the diagram, but it may be better to PM me, I'll give an email, etc.

My guesses without seeing the VI is that the value going into the initializer is a huge number, and to allocate that much would truly fail. I just did it and received the same dialog. One of the things about RT is that the error handling is a bit different. We pipe most of the errors to the DS. So I suppose this could happen on RT and simply fail differently.

If you choose to debug it yourself, probe the dimension size(s) and see if they explain why the dialog is coming up. Then, of course you'll need to work backwards to see why this function is calculating or being given bogus inputs.

Greg McKaskle
Reply With Quote