Running a Command in CMD vs LabVIEW System exec

[JScherer]

I'm trying to build an API for the Pololu Tic T500 ( https://www.pololu.com/docs/0J71 ) Stepper motor controller and am having an issue getting the system to respond to LabVIEW controls even though it does work on controls issued through the command prompt.

For Example: if I 

1. Open command prompt ( windows, type "cmd," hit "enter")
2. Type "ticcmd --home fwd"
3. Hit "enter" 

The system homes to the forward position.

However, when I try to do the same in LabVIEW I get:

but without the motor moving.

What is the difference between the two methods, and how do I get the LabVIEW to execute the same as manually entering the value in the command prompt? 

[Bob_Schor]

You need quotation marks around the ticcmd argument.  Make your string ticcmd "--home fwd".

Bob Schor

[JScherer]

Tried this, but no luck:

[aputman]

Use cmd /c. 

[RTSLVU]

This might help 

[JScherer]

I tried this

No dice, I also don't get an output with cmd/c 

[JScherer]

One thing I just noticed is that when I go to Start -> cmd -> Command Prompt I get a window that says "Command Prompt." When I open one with LabVIEW, it looks like I get C:\windows\system32\cmd.exe

See below:

[Darin.K]

Check the 'standard error' output

[aputman]

What output do you expect from this command?

Try putting the whole command in the command line string (with and without quotes as Bob mentioned).

cmd /c ticcmd --home fwd

[Worle]

Try without the EOL constant. I wouldn’t have thought it was necessary. 

Also, from a quick google it looks like ticcmd adds itself to the system path variable. Try using the path the the ticcmd.exe file rather than just ticcmd. I have never tried relying on system path variables with system exec...not 100% it will work.