Stuck buttons on the Proscan client?

[jjn555]

I'll try to keep this short.

My system:
SDS-200 (1.24.00 Main, 1.03.15 Sub firmware)
Shielded 25' CAT6 cable from the SDS-200 to a GS-105 Ethernet switch
Unshielded 10' CAT6 cable from the GS-105 to my TP-LINK AX1800 WiFi 6 router.
Unshielded 1' CAT5 cable from the AX1800 to my cable modem.
Samsung Galaxy cellphone.
Registered user of Proscan version 24.5

The Web Server works fine. I can see & hear everything on my desktop computer that's running Proscan AND when I connect to the external IP address when I'm away from home.

HOWEVER....
I have a specific problem that only shows up on my cellphone when I connect to the SDS-200's Web Server.
It happens BOTH when I connect within my internal network http://192.168.x.x:5000 and when I connect via cell towers http://98.xxx.xxx.xxx:5000
I just realized I haven't checked if I connect to the external IP address of the Web Server from my house. Ah well.

The problem is that when I press on a key (such as, but not limited to, 'System' in this example screenshot), it stays depressed. The radio itself continues to run normally as if the key was never pressed. Repeated taps of that button eventually seems to work most of the time such that the radio does what it's supposed to do and the button will appear in its unpressed state.

I did some searching via AI and found a few suggestions there. I did some of them (new CAT6 cable, new Ethernet switch), but the problem still is present.
This 'not seeing the key go back to the 'unpressed state after clicking on it' doesn't happen when I click on the key from the Proscan program running on my PC. It only happens when I connect to my scanner's web server.

Anybody else run across this? Anybody have any ideas on what I might try? I'm not sure what I'm missing. One of the AI things I read said that Proscan had options in the on the Web Server tab that I could tweak (see attached screenshot). Apparently, those are no longer available or maybe the buttons have moved. Aside from that, I love the flexibility that the Proscan Webserver gives me.

 

[Whiskey3JMC]

FWIW not an issue for me, albeit an SDS100. Several Galaxy phones on Chrome & Firefox. "Scanner only" view mode. What view mode are you set to?

 

[avery_k]

I don't recall seeing this behavior using browsers on my phone or home computers. I wouldn't suspect any of the networking gear as all it does is pass along the packets generated by Proscan. Maybe Bob will chime in.

 

[jjn555]

FWIW not an issue for me, albeit an SDS100. Several Galaxy phones on Chrome & Firefox. "Scanner only" view mode. What view mode are you set to?

Thanks for reading. I'm

FWIW not an issue for me, albeit an SDS100. Several Galaxy phones on Chrome & Firefox. "Scanner only" view mode. What view mode are you set to?

Thanks for reading. I assume you're talking about this one:
I'll play around with those other choices to see if I can see any pattern. Thanks.

 

[jjn555]

I don't recall seeing this behavior using browsers on my phone or home computers. I wouldn't suspect any of the networking gear as all it does is pass along the packets generated by Proscan. Maybe Bob will chime in.

I've not found a clear concise answer, but the tidbits that I have found seem to imply that there's something in the OS that treats momentary pushbuttons questionably. Apparently, it sends a KeyDown message immediately followed by a KeyUp message with no delay inbetween, and the implication is that the SDS200 can't handle rapid fire messages like that. That's just my understanding of what I've read about it. Maybe that's all BS, maybe not.

 

[ProScan]

@jjn555
If you don't mind, can you post the URL and password so we can see if the problem is on the server or client side.
You can change the password after testing or use a temporary password for us to test.

{edit} Keep it at Normal Display like you have it in the image. Make sure the buttons are visible and not off screen.

 

[jjn555]

@jjn555
If you don't mind, can you post the URL and password so we can see if the problem is on the server or client side.
You can change the password after testing or use a temporary password for us to test.

{edit} Keep it at Normal Display like you have it in the image. Make sure the buttons are visible and not off screen.

OK, I'll do that later today.

 

[ProScan]

OK, I'll do that later today.

I setup a test server. Try it for a more conclusive result.
super user password: 1234

https://proscan.freedynamicdns.org:5000/

 

[jjn555]

OK, I'll do that later today.

Just for kicks, I set up a mobile Hotspot on my phone, connected my work PC (Windows) to it, and then browsed to my external IP of my SDS-200 web server.
With this configuration, the keys were very responsive and I never saw a "stuck key".

The only thing unusual is that I don't see the image of any key being depressed when I tap on it using my work PC. If my cellphone did this, I'd consider it a minor thing. I don't know what firewall restrictions were implemented at my workplace, so I'm not too concerned with this difference.

 

[jjn555]

I setup a test server. Try it for a more conclusive result.
super user password: 1234

https://proscan.freedynamicdns.org:5000/

 

[jjn555]

Using the same hotspot configuration I used to connect to MY radio, my experience with the test web server you posted is similar.
I only pressed the SYSTEM, DEPT and CHANNEL keys. I did not see any 'stuck keys'. I did not see any key in its depressed state, same as when I connected to my radio. The image of each key did not change when I clicked on it.

It took a second or two or three for the radio's display to respond to whatever key I pressed on the test server, which was MUCH longer than the delays I saw connecting to my radio.

The LED bar on each of these softkeys remains lit at all times. I don't remember what my radio did.

I found that I need to wait for the test radio to update the display in response to a key I tap BEFORE I press the next key. Otherwise, that 'second' key may be ignored. For example, I pressed SYSTEM, paused 1/2 a second, DEPT, paused ½ a second, CHANNEL, and only the SYSTEM and the CHANNEL display changed; the DEPT display remained what it was before I pressed SYSTEM.

I did notice one thing different. On your test server, I appear as a "SuperUser", but on mine, I see "Serve Scanner Control Mode".

Probably insignificant, but I thought I'd mention it anyway.

Thanks for setting this up for me to try. Maybe it'll help zero in on where I should be focusing my attention.

-Jim

 

[ProScan]

Using the same hotspot configuration I used to connect to MY radio, my experience with the test web server you posted is similar.
I only pressed the SYSTEM, DEPT and CHANNEL keys. I did not see any 'stuck keys'. I did not see any key in its depressed state, same as when I connected to my radio. The image of each key did not change when I clicked on it.

It took a second or two or three for the radio's display to respond to whatever key I pressed on the test server, which was MUCH longer than the delays I saw connecting to my radio.

The LED bar on each of these softkeys remains lit at all times. I don't remember what my radio did.

I found that I need to wait for the test radio to update the display in response to a key I tap BEFORE I press the next key. Otherwise, that 'second' key may be ignored. For example, I pressed SYSTEM, paused 1/2 a second, DEPT, paused ½ a second, CHANNEL, and only the SYSTEM and the CHANNEL display changed; the DEPT display remained what it was before I pressed SYSTEM.

I did notice one thing different. On your test server, I appear as a "SuperUser", but on mine, I see "Serve Scanner Control Mode".

Probably insignificant, but I thought I'd mention it anyway.

Thanks for setting this up for me to try. Maybe it'll help zero in on where I should be focusing my attention.

-Jim

You're making it more complicated then needed. I'm trying to determine if the problem is on the client side which I suspect or if it's on the server side. Don't change things around. We want the same setup so the symptoms don't change. Let us try your server and you try mine.