View Single Post
  #3   Spotlight this post!  
Unread 19-02-2009, 20:41
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: Labview Question

If you don't have the robot connected, but you do have the cRIO and DS, then it becomes possible to perform debugging to a basic level. You'd connect the joystick, DS, and cRIO and computer together, run the app, and put a probe on the input to the motor. Clearly the inputs to the FPGA are not going to change without sensors attached, but you can access and update motors and other outputs all you like. The FPGA will dutifully update open circuits and you can test out logic stuff pretty well.

You can test other stuff by writing harness VIs to send sample data into the processing subVI. This HW in the loop testing is pretty much what NI HW and LabVIEW are designed to do.

Greg McKaskle
Reply With Quote