|
|
|
 Yes, good job being calm and asking about the validity of a rumor before fanning the flames and assuming the conspiracy must be true. - Greg McKaskle [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| Yes, good job being calm and asking about the validity of a rumor before fanning the flames and assuming the conspiracy must be true. - Greg McKaskle [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#4
15-12-2009, 10:43
|
|||
|
|||
|
Re: Problem with cRIO Imaging Tool
This sounds like a firewall issue most likely. MAX and the cRIO imaging tool find NI real-time devices in the same manner, so if MAX can find the target the imaging tool should as well.
What is your network setup? It should be a cross-over cable between your PC and the cRIO (a regular ethernet cable will work on most newer network cards). Settings on the PC should be static IP address 10.xx.yy.5, subnet mask 255.0.0.0 where xx.yy is your team number. 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| cRIO Imaging Tool HELP PLEASE!!! | furiousgeorge | FRC Control System | 2 | 08-02-2009 22:44 |
| FRC cRIO Imaging Tool | furiousgeorge | Programming | 1 | 06-02-2009 09:52 |
| cRio Stand-alone Image Tool | Vikesrock | FRC Control System | 3 | 29-01-2009 19:38 |
| [FTC]: Problem with Code or Problem with Bluetooth? | VeedotJaydot | FIRST Tech Challenge | 3 | 27-01-2009 18:22 |
| cRIO Problem | Pneumaticsman | NI LabVIEW | 8 | 10-01-2009 11:59 |
Threaded Mode