That’s not an error message. It’s supposed to print that out. The cam prints that when the IDE connects to it.
I don’t know what’s going on with the serial driver for you. However, I’m testing with windows 7 right now to get to the bottom of this. On windows 10 we’re not seeing any problems because windows install the driver itself.
I can increase the serial timeout, but, that shouldn’t make a difference… 500 ms is more than enough time for the cam to connect. Is it possible the USB cable/port is bad? I’ve been testing with 10 ft USB extension cables over here and I haven’t had any issues.
However, even after making the timeout longer I still saw failures with the get firmware command. I’m thinking of making the IDE try more than once before giving up, this might solve the problem. Also, possibly moving the first get firmware command away from the same time the port was opened.
Yeah, windows 10 works a lot better. Our driver is actually the same as the Arduino.inf driver. I copied the code for what they did more or less. The problem is likely the interaction our camera firmware and the old operating system driver.
The pyboard driver is the same too. Sigh… I believe there are some real problems in the serial firmware in the OpenMV Cam. But, we need a reproducible issue.
If I have the module connected before the IDE starts I always get timeout errors
If I start the IDE, attach the module, wait for the flash drive to mount, then press connect I get a connecting text box and nothing else. If I disconnect the module and reconnect I get a warning message that no cams were found and then it connects
If I start the IDE, attache the module, wait for the device drivers to start (windows make a sound), press connect right before the flash drive mounts (I get an OS prompt when removable storage is attached), it usually connects
In all cases I am unable to run example scripts after it connects
I am out on travel and will not be able to do additional testing before Wednesday
I’m getting some the connect issues your having with a windows 7 VM. I’m adding in code to retry commands right now. I don’t think it will help to much. The firmware needs to be able to handle split USB serial packets which I think cause the problem.
I updated the driver and fixed the driver installer. It has perfect behavior except for windows 8 where it displays an info box when done - all else are silent. Also, I tested on windows vista, windows 7, and window 8. All of them are working fine. I added some hard 2 ms delays between serial flush calls for the serial thread in the IDE so that USB packets have to be sent out before another gets built up. Additionally, I also put retries into the IDE so that it will re-execute a command up to 5 times before giving up. Each time it will wait 200 ms. So, a total failure will take the IDE 1 second to see.
Windows XP is completely broken for me. Not even the pyboard works on windows XP. I thinks its because of the version of the OS I have. Its an old service pack 2 disk. It won’t let you install drivers by clicking on the inf. You have to go through the add/remove hardware menu. Anyway, the IDE installs fine on windows XP and can even open the serial port. But, no data is transmitted on the USB link.
"Hmm, the IDE filters out USB ports by the VID/PID of the Cam. Okay, try this:
Click the connect button while the Cam is not connected to the PC. The IDE will then ask you if you have a bricked OpenMV Cam. Say, yes, then select if you want to erase the flash drive or not. Doesn’t matter. Then the IDE will wait for you to connect the Cam to your computer. Do that. The boot loader will not overwrite the cam.
After that everything should work fine.
Note that the bootloader on the IDE won’t work on a VM. But, the IDE should normally run on a VM.
Nyamekye,"
So I tried, but it didn’t work … no results.
So, I installed the OpenMV IDE 1.2.0
Now when I connect the Cam I have green blinks, one red/purple blink then 2 blue blinks and the blinks stop.
When I launch OpenMV IDE, it does not detect the Cam, if I click on the connect button : connecting … and nothing else
If I disconnect the Cam, no result, if I connect the cam while IDE is connecting, if I connect the cam after relaunching IDE … no results
Before I install the IDE 1.2.0 the Cam was always blinking (blue led) but now, it blinks only when I connect the Cam on the USB port and after 2 blue blinks the blinks stop.
I’m working on something else that can fix this all. So, the OpenMV Cam debugging protocol was written for libsub originally. It worked for that. But, when libusb was not usable on windows the debugging protocol was then embedded in the USB CDC calls. Anyway, this means that commands must be sent to the Cam in separate USB packets to work. USB CDC packets can be at maximum 64-bytes.
Ibrahim threw this code together and it sorta works as long as the USB packets come in slow. I’ve been trying to work around this on the PC by sending USB packets slowly so that the host doesn’t combine two commands into one packet. But, I think I have a more stable fix which is to just send 64 byte packets always. The USB debugging code for the Cam doesn’t care if the packets are longer than necessary, only that one command per USB packet is sent. So, by zero padding the command everything works much better. I already tested this on my PC and it let me remove all the delays I added in between sending packets.
However, this fix is not alone enough to guarantee the system works on all PCs. Ibrahim will… fix this… in the next version of the firmware and boot loader by adding in a small 64-byte buffer which will hold commands sent that are shorter than 64-bytes. This will remove the assumption we depend on that the computer will send 64-byte packets in separate frames and not generate short packet lengths.
In reality, the firmware should have never been such that it required debugging packets to be in separate USB transfers. Terrible code right there. But, since that’s what’s there out in the wild right now I have to put fixes in the IDE to get around this.
@Kermit666 - Inability to connect is a separate issue from the USB packets. When you plug in your OpenMV Cam… does it appear as a device in your device manager? If so, what device does it appear as? There’s no IDE fix I can do to solve any problem related to the Cam not connecting to the PC initially.
Two things can be happening:
The wrong driver is getting loaded for your OpenMV Cam.
The Cam’s firmware is bad and you need the bootloader to fix it. If 2 is the case the bootloader should be able to connect to the Cam, but, might have trouble re flashing given the packet issue. You’d get a failed to connect to bootloader error here.
I uninstalled the IDE and reinstalled using the link you provided a couple of post up. This new version still IDs as 1.2.0 (?)
OpenMV driver version 5.1.2600.3
No improvements from my end. The only way I can connect is to attach the module and then quickly press the connect button before the flash drive mounts
When connected, the helloworld script will not run
“@Kermit666 - Inability to connect is a separate issue from the USB packets. When you plug in your OpenMV Cam… does it appear as a device in your device manager? If so, what device does it appear as? There’s no IDE fix I can do to solve any problem related to the Cam not connecting to the PC initially.”
When I plug in the Cam it appears as a removable disk, with 31 KB and 3 files inside.
This works perfectly from the beginning
"Two things can be happening:
The wrong driver is getting loaded for your OpenMV Cam.
The Cam’s firmware is bad and you need the bootloader to fix it. If 2 is the case the bootloader should be able to connect to the Cam, but, might have trouble re flashing given the packet issue. You’d get a failed to connect to bootloader error here."
I have the lcd module, what happens on the lcd module when I connect the cam ? on my cam + lcd I have only a white lcd, nothing else !
…just to report that the new IDE (v. 1.1.0) installs fine on a MacBook Pro (mid-2012) running OS 10.8, and installs the updated firmware. The key is to connect the OpenMV to the Mac via a powered USB 2 hub. Directly connecting OpenMV to the built-in USB ports gives only grief -this is a known feature of this generation USB 3.0 controller.
I couldn’t get it to work on my Ubuntu. Trying to connect tells me “no openmv cams found” and then asks me if I’d like to unbrick the camera and delete the filesystem, when I click yes, it displays a full progress bar and tells me to disconnet and reconnect the camera, but nothing happens when I do. Any hints? It worked fine with the old IDE.