kleinjd
I updated to the latest version today, this also happened on the previous version as well. All the lateset win7 updates, and .NET updates.
Can connect and run EZB no problems, can connect to the drone without issue, enable the camera, still fine live video no problem, enable color tracking, still no issue. put a red target in front of the camera, see the blue tracking square, then the circle of death mouse pointer and a screen refresh with (Not reponding). No more EZB need to kill it off and restart?
Any ideas?
Tried various USB ports for both the wifi and bluetooth (all work the same, no change) tried various com ports for the bluetooth connection. Removed the EZB bluetooth device and re-deiscovered and installed it. Went back to .NET 3.5 same problem. Let the system update back to .NET 4 still same issue.
Not sure what else to try
Thank you jimk
confused
Awesome jim. good to hear the software is mostly stable across multi processors. If you have time, try the latest version i posted today.
also use the Debug window (F2) to see if there are any details in the log before it locks up
uh oh, updated EZB and it told me I needed to update the firmware. Now I find the following, several attempts same result:
Attempting connection to COM3 EZ-B reports EZ-B Firmware V15.3 Connected Press the UPDATE button to start upgrade sending ping sending ping sending bootloader Failed to load bootloader! Have you selected the correct EZ-B COM port? Use the Help menu option to view the online help and watch a video demonstration.
jimk
No worries after all, slowed the port down to 19200 and went without issue. And the update is a SCREAMING SUCCESS !!!!
Been running all 3 targeting modes without a problem, also changing between modes without a problem. So you nailed it :-)
Set the priority to High and affinity to CPU 1, runs about 15% of the CPU.
Thank you !!!! jimk
:) Awesome
You souldn't need to change any COM settings. Defaults work best. I feel less is more
So i never change anything. I install windows, and go from there.
But, sounds like you got it working anyway!