I have been programming my T3-BB for the past few weeks. This has been more difficult than I expected due to frequent “Not-responding” delays when attempting to F2 Send or F8 Refresh. This occurs on average about half the time - sometimes more, sometimes less.
I am using a Windows10 LaptopPC running the lastest T3000 version, connected via LAN-Hub to the T3-BB. The hub only has 3 connections - Internet/Router via LAN, PC, T3-BB. The “health” is green 92-100%.
There is no way to tell is a problem is going to arise. I usually click of Send by mouse - The “Send” icon gets a blue highlight when mousing-over, and that usually means the send will work - but not always. Sometimes there is no blue highlight but it works anyway Refresh will more-often than not result in Not-Responding. (Per Murphy, the way to get good performance is to start writing a post about the problems!)
Typically, I click on send and nothing happens…but the screen freezes, then I click again. After 2 extra clicks the screen banner shows “Panel 1 Program N Name [name]: (Not Responding)”.
I click again and the hourglass shows, another click and the program window becomes “washed-out”. Then after about 40sec a pop-up/beep says “Write Program Code Timeout”.
I suspect that the fault is more likely with just a short interval between click “Send” and click “Refresh”.
(see screenshots)
Throughout all this, the health indicator stays green - 92-100%. Often enough the repeat attempt after failure also fails. All these 40sec delays make programming very slow.
Sometimes the main program window comes to the front - leaving the edited program in the background. Sometimes things appear to “unfreeze” after 30sec or so, and the send or refresh has happened - but usually not
What is very disconcerting is that every few days the currently-edited program gets spontaneously copied into other programs - usually empty ones, but sometimes on-top of what was there before. I have found up to 3 redundant versions as well as the original. Sometimes the editor switches to one of the redundant copies - discovered because further edits dont affect the running program. The only clue from the main program window is that the new copies have the same size as the one being edited.
Does anyone else experience these issues? Is there any solution?
Can the write-timeout be shortened (to say 20 sec)?
