01-18-2013 04:16 AM
hello all,
i have an NI 9403(DI/O) connected to the chassis and wanna test it, so connected two ports of it to eachother to send data on one & read it from the other. i'm not sure weather to use the fpga/scan mode. Can u plz help?in fpga mode i just face errors the whole time, like " a connection could not be established'.
thanks
01-18-2013 05:51 AM - edited 01-18-2013 06:05 AM
Hello AutonomusMode,
this error could happend, if you want to autodetect the system.
You can manually add the componets to your project and then made
a connection to the system this should also work.
Please check before that the system is available in the MAX and that
the IP is the same in MAX and the project.
01-18-2013 07:59 AM
Thanks a lot.
03-12-2013 05:38 AM
I can not see any shared variables in DSM? can u plz tell me why?
03-12-2013 05:42 AM
03-12-2013 07:03 AM
Hello AutonomusMode,
have you tried to deploy all new in the project, are then the variables shown in the DSM?
Sorry, i didn´t have an LinkIn account.
03-12-2013 07:45 AM
Hello Alexander,
i have no shared variables in the VI(attached), but it does not run headless. i can switch on the CRIO led headlessly(test). the code also runs properly as it runs on host. What do u think could be wrong?
Best,
Samira
03-12-2013 08:19 AM
Hello AutonomusMode,
what means headless? In your code only vi´s from the kuka youbot and your code stops automatically
after 30 seconds this is configured int the elapsed time vi´s.
What is the rio headlessly(LED)?
03-12-2013 08:44 AM
Alexander,
i want the robot to run in stand alone mode. A simple test program runs headless(just turning an led on as start up).
I want the program to run on the controller without being connected to the PC.
03-12-2013 08:52 AM
Hello AutonomousMode,
normaly if you run the vi and close the project the vi should still run again until you reset or power off the device.
Your programm stops after 30 seconds because the elapsed time vi.
If you want that the controler also restart if power off and on will done, you have to create a startup exe in
the build specification and deploy this executable to the target.