Yeah, I went ahead and reformatted it and it still is extremely sluggish. I tried plugging it in via the other cvs network jacks that have always retrieved data with ease, and still sluggish. Interestingly, using a crossover cable on site has become much faster to transfer to and from. I plugged in one of the other sytems up to the network using the same cable and jack as the one giving me trouble and no problems. Also, when I reformatted the compact flash drive and then reinstalled the software, and reinstalled my product files (inspections) the images being taken have switched. I use two cameras for the majority of my inspections and have discovered that the the images which should be coming from the left camera is now taken from the right. Furthermore, since I have your attention, with all the CVS' (we own four), I have discovered that every time I transfer one inspection to another CVS, I have to open it in config mode and change the Acquire Image steps due to the fact that the cameras have different serial numbers(?). Not sure why, but that is what I figure. This is a bummer, but it gets worst. Every time I transfer one product inspection to another CVS and go to change the acquire image steps (the first steps of my inspections; usually two) the list shows up with the cameras (Bassler 622f) that are plugged into the CVS via IEEE1394, but the format drop down list is almost always blank. When it isn't blank (which usually takes a reboot to get to) I select the one I need to use (Format 7) and I get an "Unknown Error" message. This happens every time. Then the VBAI stops responding, and I have to close the program and reboot the systems. When I go into Measurement and Automation first, and select remote target, and click on the cameras, I can select the Formats with out any problems. But when I open VBAI (which I've uninstalled/reinstalled from host computers) it still does this. This is a major problem for me since I work in a manufacturing environment where minutes are critical. Lastly, I use the decision making step in VBAI 2.5 to reject unacceptable parts by sending the signal out the 37? Pin connector via an ISO OUT port, in which I have been doing since we first purchased the CVS 1456 systems. I wondered why it takes so long to send this signal when in inspection mode vs. configuration mode or benchmark tests? In other words, if I run the inspection there is nearly a 1-2 second lapse in time until the signal is sent, however, when I run configuration mode until failure, it takes an instant to send this signal. This is verified on the display as well. Every inspection has a final step of displaying images which includes a Boolean of fail or pass (after the decision making step; and the inspection is set to fail upon the decision making step). When a part pass/fails, the display shows the result 1 to 2 seconds after it has started, yet, Benchmarking instantly sends the signal every time there is a failure (all inspections take up to 400ms according to benchmark tests) and the display shows the result just as fast. Same goes with configuration mode.
1). The ethernet/network of one of my CVS' is still extremely sluggish even after reformatting.
2). Is there a way to trick the CVS' into thinking that the left camera is the right so I don't have to change every acquire inspection step via the software? Swapping the IEEE1394 ports doesn't work.
3). Why are there so many errors when I transfer one product inspection to another CVS? All of the vision systems are wired the exact same.
4). Lastly, why is it taking so much longer to send a signal through the 37-pin connector when in inspection mode vs. configuration mode and benchmarking?
I am very sorry for the length of this, but these are very serious problems for us that we hope can be cleared up promptly. Thank you so much for your support.