› Forums › General Questions and Comments › dropControllerPC ver 1.2.0.2 › Reply To: dropControllerPC ver 1.2.0.2
I’m finding this a little strange. The app is getting the HELLO reply from the dropController but then losing the connection / not getting anything else.
If I start a sequence and then disconnect the usb cable the app crashes with the error “The port is closed”. I then have to restart everything (I haven’t trapped a disconnect error internally).
Here is the log I get from the loop page using the same drop settings as you. I get the FTS code reliably.
Loop Page init performed
ACKTimerOff
SUB loopTimerOff()
SUB – updateDropData(). SEQ = 1
SUB – updateScreen()
RESET performed
wait user click START
START BTN clicked
SUB buttonStart()
SUB – sendDropData()
ACKTimerOn
Inside Timer_ACK
ACKTimerOff
timeOutCount = 1
ACKTimerOn
Inside Timer_ACK
ACKTimerOff
timeOutCount = 2
ACKTimerOn
Inside Timer_ACK
ACKTimerOff
timeOutCount = 3
receivedData = <FTS>
FTS rec’d from the dropController
Completed
On the main window, above the debug text box are a couple of flags. Does the Connected flag stay as “True”.
If you have visual studio installed it may be worth while trying the examples at
http://www.martyncurrey.com/arduino-and-visual-basic-part-1-receiving-data-from-the-arduino/
http://www.martyncurrey.com/arduino-and-visual-basic-part-2-receiving-data-from-the-arduino-part-2/
http://www.martyncurrey.com/arduino-and-visual-basic-part-3-controlling-an-arduino/
This will then confirm the serial connection works.
Are you still using the Nano?