@ John - We’ve got a bench top test fixture that is wired with regular cables and has some but not all of the instruments the fully loaded go-to-sea version in the pressure housing has. We don’t see this issue very often, if at all, on the bench top unit. However, it won’t have the same exact noise environment the go-to-sea unit has. The bench top unit will be better in some ways, standard cabling and less instruments generating noise but it isn’t in a metal pressure housing which may act as a shield to some degree.
I am trying to narrow down this problem to something I can understand. I’ve had the same problem with the system in the pressure housing when I crack the end cap and use a regular USB cable to the dual USB module. I’ve nearly, but not quite, convinced myself it isn’t the cabling. I say not quite because it might be that my non-standard USB cabling is slightly more susceptible to noise and the problem may be a random result of how much welding or RF or ? is going on in my vicinity.
The one fact that seems most repeatable is that the download process hangs after it says “Ready” as I mentioned in my first post. The process has certainly hung up at other points but this is the most likely stopping point. If I hit the green arrow/download debug button it usually, but not always, will download properly on the 2nd or 3rd try.
Can you tell me what is going on just before and after the “Ready” statement is printed out?
Another question is: What can I be doing in my program that might be causing this problem?
For example, I had some 20-30 second Thread.Sleep statements in my program as a temporary way to see what some of my instruments were doing. When those statements were in, this problem seemed to be much, much worse. It happened almost every download and sometimes it took all kinds of reboot, power cycle, FezConfig, etc to get my program to download. I’ve replaced those Thread.Sleep statements with logic in my state machine that checks the machine time and does something when the desired period has elapsed and doesn’t put the thread to sleep. I only have one thread by the way. This seems to have made the problem much better but it still happens quite often.
Is there any reason to believe that a Thread.Sleep for more than 1 or 2 seconds will prevent VS from downloading a new program?
Thanks for your help, I really appreciate it.