Changes in SDK 1.7

[FTC4855]

Has anybody experienced this issue with the new beta SDK 1.7?

We have in our init_loop code similar to the following and during our testing we had the servo disconnected and it immediately causes the Servo Controller USB device to close. Is this expected behavior? In the previous SDK versions it would not cause an issue.

[SIZE=1][COLOR=#000000][FONT=lucida console][COLOR=#660e7a][B]colorServo[/B][/COLOR][/FONT][/COLOR][/SIZE][COLOR=#000000][FONT=lucida console].setPosition([/FONT][/COLOR][COLOR=#0000FF][FONT=lucida console][/FONT][/COLOR][SIZE=2][COLOR=#000000][FONT=lucida console][/FONT][/COLOR][/SIZE][SIZE=1][COLOR=#000000][FONT=lucida console][COLOR=#0000ff]0.5f[/COLOR][/FONT][/COLOR][/SIZE][COLOR=#000000][FONT=lucida console])[/FONT][/COLOR][COLOR=#CC7832][FONT=lucida console][/FONT][/COLOR][SIZE=2][COLOR=#000000][FONT=lucida console][/FONT][/COLOR][/SIZE][SIZE=1][COLOR=#000000][FONT=lucida console][COLOR=#cc7832];[/COLOR][/FONT][/COLOR][/SIZE]

03-31 07:46:28.883 V/RobotCore(12767): sending CMD_INIT_OP_MODE_RESP(401), attempt 0
03-31 07:47:12.263 D/UsbDeviceConnectionJNI(12767): close
03-31 07:47:12.263 D/ProcessRequestThread:12767): Device has been closed.
03-31 07:47:12.263 W/System.err(12767): java.lang.InterruptedException
03-31 07:47:12.273 W/System.err(12767): at java.util.concurrent.locks.AbstractQueuedSynchroni zer.doAcquireSharedInterruptibly(AbstractQueuedSyn chronizer.java:975)
03-31 07:47:12.273 W/System.err(12767): at java.util.concurrent.locks.AbstractQueuedSynchroni zer.acquireSharedInterruptibly(AbstractQueuedSynch ronizer.java:1281)
03-31 07:47:12.273 D/BulkIn:12767): Stop BulkIn thread
03-31 07:47:12.273 W/System.err(12767): at java.util.concurrent.Semaphore.acquire(Semaphore.j ava:283)
03-31 07:47:12.273 W/System.err(12767): at com.ftdi.j2xx.o.c(SourceFile:2294)
03-31 07:47:12.273 W/System.err(12767): at com.ftdi.j2xx.p.run(SourceFile:2764)
03-31 07:47:12.273 W/System.err(12767): at java.lang.Thread.run(Thread.java:811)
03-31 07:47:12.273 W/RobotCore(12767): could not write to Modern Robotics USB Servo Controller [AL00XLO2]: FTDI Null Pointer Exception
03-31 07:47:12.273 E/RobotCore(12767): java.lang.NullPointerException: Attempt to invoke interface method 'void java.util.concurrent.locks.Lock.unlock()' on a null object reference
03-31 07:47:12.273 W/System.err(12767): java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.ftdi.j2xx.n.d()' on a null object reference
03-31 07:47:12.273 W/System.err(12767): at com.ftdi.j2xx.o.f(SourceFile:2675)
03-31 07:47:12.273 W/System.err(12767): at com.ftdi.j2xx.a.run(SourceFile:2879)
03-31 07:47:12.273 W/System.err(12767): at java.lang.Thread.run(Thread.java:811)
03-31 07:47:12.363 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.363 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.363 W/RobotCore(12767): [55 aa 80 70 20] -> [00 00 00 00 00]
03-31 07:47:12.363 W/RobotCore(12767): [55 aa 80 40 09] -> [00 00 00 00 00]
03-31 07:47:12.363 W/RobotCore(12767): could not read Modern Robotics USB Servo Controller [AL00XON7]: comm timeout
03-31 07:47:12.363 W/RobotCore(12767): could not read Modern Robotics USB Core Device Interface Module [AL00VDMM]: comm timeout
03-31 07:47:12.363 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.363 W/RobotCore(12767): [55 aa 80 40 1e] -> [00 00 00 00 00]
03-31 07:47:12.363 W/RobotCore(12767): could not read Modern Robotics USB DC Motor Controller [AL00VJ0E]: comm timeout
03-31 07:47:12.373 W/RobotCore(12767): [55 aa 80 40 09] -> [33 cc 80 40 09]
03-31 07:47:12.373 W/RobotCore(12767): could not read Modern Robotics USB Servo Controller [AL00VDQP]: comm timeout on payload
03-31 07:47:12.373 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.373 W/RobotCore(12767): [55 aa 80 40 1e] -> [00 00 00 00 00]
03-31 07:47:12.373 W/RobotCore(12767): could not read Modern Robotics USB DC Motor Controller [AL00VB7K]: comm timeout
03-31 07:47:12.393 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.393 W/RobotCore(12767): Modern Robotics USB header sync bytes are incorrect
03-31 07:47:12.393 W/RobotCore(12767): [55 aa 80 40 1e] -> [00 00 00 00 00]
03-31 07:47:12.393 W/RobotCore(12767): [55 aa 80 40 1e] -> [00 00 00 00 00]
03-31 07:47:12.393 W/RobotCore(12767): could not read Modern Robotics USB DC Motor Controller [AL00VE5A]: comm timeout
03-31 07:47:12.393 W/RobotCore(12767): could not read Modern Robotics USB DC Motor Controller [AL00VIFG]: comm timeout
03-31 07:47:12.393 E/RobotCore(12767): com.ftdi.j2xx.o.a(SourceFile:2520)
03-31 07:47:12.393 E/RobotCore(12767): com.ftdi.j2xx.FT_Device.read(SourceFile:666)
03-31 07:47:12.393 E/RobotCore(12767): com.qualcomm.robotcore.hardware.usb.ftdi.RobotUsbD eviceFtdi.read(SourceFile:112)
03-31 07:47:12.393 E/RobotCore(12767): com.qualcomm.modernrobotics.ReadWriteRunnableUsbHa ndler.a(SourceFile:77)
03-31 07:47:12.393 E/RobotCore(12767): com.qualcomm.modernrobotics.ReadWriteRunnableUsbHa ndler.read(SourceFile:66)
03-31 07:47:12.393 E/RobotCore(12767): com.qualcomm.hardware.modernrobotics.ReadWriteRunn ableStandard$1.run(SourceFile:339)