Quote Originally Posted by Toengel View Post
can you try the new firmware 140.32 first and see if the error occur even with 140.32?
Yes, and it didn't change a thing. The same bug remains in firmware version .32 as well. Not surprisingly, as software revision history between v. .27 and .32 didn't mention any attempt to fix that kind of problem.