Jump to content

sib592

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by sib592

  1. I have an application that has two nodes. One is a windows node and the other runs on a cRIO. There is alot of shared code but also code that will run base on the OS conditional disable. The customer now wants to create a training system so that they can train their employees on the system in the office. They do not want to have a a controller with every training system so we need to run both apps on a windows machine. The problem is we to build the rt code as a windows runnable executable with the OS==VxWorks condition. When I change the OS condition to VxWorks under the My Computer target it changes itself back to win. Does anyone have any suggestions on how to do this?
  2. I am using client server tcp between two laptops. They connection is created properly and data is written and read properly at first. Eventually I get an error 56 and error 57 when trying to write to data to the client. This may start happening after 5 minutes or it may start happening after 5 hours. It is very unpredictable and hard to test. When there is no response for 4.6 seconds the connection is terminated and attempts to create a new connection. They are on a dedicated network with static ip addresses. Does anyone have any ides??
  3. Thanks for the response. To answer your questions. Yes it is the main vi within an llb that I'm trying to read. The code is being launched from an rtexe located on the 9012 crio. This same code is used in an exe and has never had a problem. The llb is located in the same directory as the rtexe. The path is passed into Open VI Reference as you show above and this is where the error 1124 shows up. Is there something different that needs to be done for the rt build? I couldn't find the VILinkerErr property you have shown.
  4. I am currently having this problem on the 9012 crio and am running Vista. Does anyone know if this issue has been resolved or how to fix/work around it?
×
×
  • Create New...

Important Information

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