Tiny Screen HEX-V2

[morris39]

I cannot get actual window to full screen when window size 10 or 11 is selected in Options/Interface screen, only about 30% (for 10) which I cannot read. Size 10 is suggested for 600x400 resolution, native laptop resolution is much higher This is occuring under following conditions:
Win10 on Dell 13XPS laptop on AC or battery, on both laptop and 2nd Dell P1917S monitor, separately or both displays.
When I log in with interface connected to PC I get: Correct interface no, software version 23.3, FW 0.256, you are up to date (check/recheck).
I tried to connect interface to the car yesterday prior to updating software from v22.9 (I had not used scanner for about a year) but could not connect. Same laptop on battery (98% charge), fully charged car battery, internet disconnected. I got only the tiny window. I have not tried to connect interface to car since the software update.
Any ideas if the problem is with my equipment setup or with the interface? Is the FW actually up to date?In the past I had intermittent problems connecting with WIFI connected but could eventually overcome by changing order of VCDS opening and making connections to the laptop (USB adapter order). Since nobody else reported this problem I charged it to having WIFI connection possibly interfering with atempting FW update.
Thanks for any suggestions. The scanner is unusable in present state.

 

[stefdds]

I think I would connect your interface to the laptop via a usb port and go to VConfig and check for updates. Not sure if FW and CB are the same but CB is currently 0.4631.4

 

[Uwe]

I cannot get actual window to full screen when window size 10 or 11 is selected in Options/Interface screen,

You realize Window Size can be set as high as 27, right?

Please increase it somewhat incrementally though.

-Uwe-

 

[morris39]

You realize Window Size can be set as high as 27, right?

Please increase it somewhat incrementally though.

-Uwe-

Am I up to date ? From Config/Update screen with scanner connected to PC by USB I get soft ware and FW as stated before and also CB 0.4631;FW 0.256; CB; 0.10 ; BL;0.28. Screen says up to date on check and recheck. Otherwise there is no data except shop etc, all zeros.
I am able to increase image to about 75% on laptop by decreasing resolution to 1024x768 from native 1920x1080. This should work but I have not yet tried on the car. It does bugger app sizes on monitor due to larger font.

 

[Uwe]

I am able to increase image to about 75% on laptop by decreasing resolution to 1024x768 from native 1920x1080. This should work but I have not yet tried on the car. It does bugger app sizes on monitor due to larger font.

Rather than decreasing the screen resolution, why not use Windows' Display Scaling?

And again, you can increase the Window Size in VCDS to something quite large. I'm typing this on a 2560x1600 screen with Windows Scaling set to 100% and at size 27, VCDS fills about 2/3 of the screen. See the attached image (which I've reduced by 50%).

-Uwe-

 

[morris39]

Rather than decreasing the screen resolution, why not use Windows' Display Scaling?

And again, you can increase the Window Size in VCDS to something quite large. I'm typing this on a 2560x1600 screen with Windows Scaling set to 100% and at size 27, VCDS fills about 2/3 of the screen. See the attached image (which I've reduced by 50%).

-Uwe-

View attachment 2145

Thanks for the suggestion, I will try it later.
I have had success with connecting and image size and discovered the cause of the problems, it's the extension cable. It was represented as RT product by an RT reseller but I see now that your logo does not appear on it. That explains the intermittent faults and my mistake thinking connection order was involved.

 

[Uwe]

I have had success with connecting and image size and discovered the cause of the problems, it's the extension cable.

Huh? I don't see how a possibly fault extension cable and Window size could possibly be related.

-Uwe-

 

[morris39]

Huh? I don't see how a possibly fault extension cable and Window size could possibly be related.

-Uwe-

Bad phrasing on my part. What I meant is that both problems were resolved but not for the same reason. Bad extension explains the intermittent failures to connect certainly. A charitable reading of my poor wording might be inferred as such.