Hi,I own a JVC rs1000/nx5/n5 projector. Recently, I upgraded the firmware to version 3.5 and the calibration software to version 12, 1.10. With these updates, the calibration is interrupted with the error message “Connection to the sensor was cut off. Please un plug USB connection and click retry button. And click the START button at the bottom right.” The calibration worked just fine with the previous firmware and software versions (I’m using the SpyderX Pro and Win 10).Just wanted to check if I'm the only one with this problem... Thinking of going back to previous firmware and software versions.
Apparently the SpyderX returns this error message when it gets a 0 reading. Have you tried increasing the brightness during calibration?
Thank you for the tip!No, I wasn't aware that you could change the brightness setting used during calibration (apart from lamp mode and aperture setting). Just to be sure about this, how do you set brightness for the calibration?Concerning the error message, I was able to run through both red and green gamma measurements even though the two first measurement steps produced 0 values (I used the 20 step "normal" measurement). For the blue gamma, however, the error message pops up. Is this expected? Do all three colors need to have measured zero in one or more steps before giving an error?
Zoom the projector into the screen to make the image smaller (brighter).
I'm receiving the exact same "connection was cut off" error message using firmware version 3.5, also using the SpyderX pro. I tried the suggestion of zooming in to increase brightness, but I got the same error at the same point. I'm also seeing the error when the calibration gets to blue. Any other ideas?
I could not get it to work with my main Win10 PC or my surface pro7 but its working on my wifes laptop. Go figure. No idea what could be different on my two devices. All Win10 and all have the latest autocal installed. The meter connects right away like normal on the one but displays an orange light on the meter and refuses to connect on the other two.
I thought this might be the case so I connected directly with single cable. Same results. Using wife's laptop for now I can work around the issue but doesn't make sense why it doesn't work with other Win10 PCs.