LabVIEW should have no problem communicating over the serial port to the driver (assuming that there is a serial port, fewer computers are coming with them!). If you know the syntax for the commands you will just need to build a sub-vi that constructs these command strings and outputs them using the serial port. There are a number of examples. The things that usually confuse things are:
1) selecting the correct serial port
2) setting up the comm parameters (baud rate, bits, etc.) to agree at both ends of the communications, the PC and the controller
3) having a correctly wired communications cable (some applications need pins 2 and 3 swapped at one end). If you already have an application that talks to the controller then this one should be ok.
As to having LabVIEW detect conditions to change the direction, this should also be no problem, as long as the program is structured properly. Not knowing how the controller works makes it a little more difficult to give more answers. For example, does it make absolute or incremental moves? Absolute means that you have a starting reference and all moves are made from that (i.e if you command it to move 3.0 cm and then 4.0 cm the second move will only be 1.0 cm, from 3 to 4cm. If it using incremental then the second move would take it to 7.0 cm. Knowing which way the controller works is important in the design of your over all system. Also, does this setup have a way to find a "home" (zero) position? Otherwise you will have a difficult time make repeated movements, and your pressure measurement will not have a reference to a movement distance.
Don't be too intimidated by this, give it a try, ask more questions and good luck. Just keep your hand on the power switch the first few times you initiate movement towards stationary objects!
Putnam Monroe
PutnamCertified LabVIEW Developer
Senior Test Engineer North Shore Technology, Inc.
Currently using LV 2012-LabVIEW 2018, RT8.5
LabVIEW Champion