Thank you for the donation. I wish more people would do that as it makes you feel like what you are providing has value to someone. When I spend I will think about you. Thanks manWorks perfect.
I might have to do a second $10 donation if it evolves at this rate.
/Ubbe
Okay I made the changes here is what it doesCan you make some magic code to see to that it always leave 3 decimals, so that a 156.8 frequency will display as 156.800
View attachment 159717
/Ubbe
I have removed the freq function that trims it as it is not working like it supposed to. I will re add it later once I get it working in all curmstances.I figured it would take some intricate coding to pull it off.
It now newer go more than 3 decimals and round the decimals off so that 422.24375 that are displayed as 422.2437 on the scanner are in ScannerScreen displayed as 422.244 and a 166.5125 frequency are displayed as 166.512, so it seems to make everything three decimals and not just the trailing zeros.
I wasn't clear enough what I wished for. I should have stated:
"Can you make some magic code to see to that it always leaves at least 3 decimals, so that a 156.8 frequency will display as 156.800 and only strip any trailing zeros that goes beyond 3 decimals"
I can have several ScannerScreen programs running at the same time so it seems they can coexists and use their own variables and hooks in windows and not interfere with each other, so that's a pleasant surprise.
One thing that happened with this new version are that there's some permission issues: ElnOutError/Access denied (C:\Program Files(x86)\Scanner Screen\SS20240406.TXT) If I switch to another harddrive for the logs that hasn't any user restrictions it works fine but in the previous versions it worked to store the logfile in that same program directory on C:
I deleted any old logfiles to be sure it wasn't an issue with overwrite permissions or similar problem but then it said I needed admin rights to delete them. So previous versions had admin rights when saving the logfile but now it has some lower category rights and not user rights so cannot use the program files folder to store logfiles. It isn't really an issue so perhaps safer to not let the program have admin rights.
/Ubbe
Okay try version 2.650I figured it would take some intricate coding to pull it off.
It now newer go more than 3 decimals and round the decimals off so that 422.24375 that are displayed as 422.2437 on the scanner are in ScannerScreen displayed as 422.244 and a 166.5125 frequency are displayed as 166.512, so it seems to make everything three decimals and not just the trailing zeros.
I wasn't clear enough what I wished for. I should have stated:
"Can you make some magic code to see to that it always leaves at least 3 decimals, so that a 156.8 frequency will display as 156.800 and only strip any trailing zeros that goes beyond 3 decimals"
I can have several ScannerScreen programs running at the same time so it seems they can coexists and use their own variables and hooks in windows and not interfere with each other, so that's a pleasant surprise.
One thing that happened with this new version are that there's some permission issues: ElnOutError/Access denied (C:\Program Files(x86)\Scanner Screen\SS20240406.TXT) If I switch to another harddrive for the logs that hasn't any user restrictions it works fine but in the previous versions it worked to store the logfile in that same program directory on C:
I deleted any old logfiles to be sure it wasn't an issue with overwrite permissions or similar problem but then it said I needed admin rights to delete them. So previous versions had admin rights when saving the logfile but now it has some lower category rights and not user rights so cannot use the program files folder to store logfiles. It isn't really an issue so perhaps safer to not let the program have admin rights.
/Ubbe
Made some more adjustmentsI figured it would take some intricate coding to pull it off.
It now newer go more than 3 decimals and round the decimals off so that 422.24375 that are displayed as 422.2437 on the scanner are in ScannerScreen displayed as 422.244 and a 166.5125 frequency are displayed as 166.512, so it seems to make everything three decimals and not just the trailing zeros.
I wasn't clear enough what I wished for. I should have stated:
"Can you make some magic code to see to that it always leaves at least 3 decimals, so that a 156.8 frequency will display as 156.800 and only strip any trailing zeros that goes beyond 3 decimals"
I can have several ScannerScreen programs running at the same time so it seems they can coexists and use their own variables and hooks in windows and not interfere with each other, so that's a pleasant surprise.
One thing that happened with this new version are that there's some permission issues: ElnOutError/Access denied (C:\Program Files(x86)\Scanner Screen\SS20240406.TXT) If I switch to another harddrive for the logs that hasn't any user restrictions it works fine but in the previous versions it worked to store the logfile in that same program directory on C:
I deleted any old logfiles to be sure it wasn't an issue with overwrite permissions or similar problem but then it said I needed admin rights to delete them. So previous versions had admin rights when saving the logfile but now it has some lower category rights and not user rights so cannot use the program files folder to store logfiles. It isn't really an issue so perhaps safer to not let the program have admin rights.
/Ubbe
Does the screen say anything when it stops?For the GLG command to retrieve the parameters it is a Uniden issue that it doesn't send any system or department info when monitoring private iCalls in DMR. It even gave an AM modulation info when monitoring a trunked system in NFM when I had monitored airband AM prior to that.
For using other commands they give you the whole display info in a comma delimited format but then differs depending of scanner model and if 3 or 5 row display mode are used.
For the comport issue when running ScannerScreen over night it first stopped at 7 o'clock in the morning and next time 2 o'clock at night. I can then use Unidens RH536 program and connect to the 536 scanner and confirm that the comport are still working, but after that check and even reconnecting the USB cable it doesn't help in ScannerScreen but selecting another comport and selecting to connect and then select back to the correct port makes it works again. So something like a crash in a buffer, used for the comport by the ScannerScreen program but not for other programs, that gets cleared when selecting another port.
/Ubbe
For the disconnecting there is a newer version 2.653 I compiled in the newest version of synapse from their github I am using the synaser library for serial communications.For the GLG command to retrieve the parameters it is a Uniden issue that it doesn't send any system or department info when monitoring private iCalls in DMR. It even gave an AM modulation info when monitoring a trunked system in NFM when I had monitored airband AM prior to that.
For using other commands they give you the whole display info in a comma delimited format but then differs depending of scanner model and if 3 or 5 row display mode are used.
For the comport issue when running ScannerScreen over night it first stopped at 7 o'clock in the morning and next time 2 o'clock at night. I can then use Unidens RH536 program and connect to the 536 scanner and confirm that the comport are still working, but after that check and even reconnecting the USB cable it doesn't help in ScannerScreen but selecting another comport and selecting to connect and then select back to the correct port makes it works again. So something like a crash in a buffer, used for the comport by the ScannerScreen program but not for other programs, that gets cleared when selecting another port.
/Ubbe
Does the screen say anything when it stops?
Any error?
I am using a really fast baud rate perhaps I could slow it down some.
ser.config(115200, 8, 'N', 0, False, False);
For the disconnecting there is a newer version 2.653 I compiled in the newest version of synapse from their github I am using the synaser library for serial communications.
Please try and let me know.
Also found a bug with the selecting the dir it was not assigning the edit box a value.
here is the voice reading logicDoes the screen say anything when it stops?
Any error?
I am using a really fast baud rate perhaps I could slow it down some.
ser.config(115200, 8, 'N', 0, False, False);
For the disconnecting there is a newer version 2.653 I compiled in the newest version of synapse from their github I am using the synaser library for serial communications.
Please try and let me know.
Also found a bug with the selecting the dir it was not assigning the edit box a value.
Does the screen say anything when it stops?
Also found a bug with the selecting the dir it was not assigning the edit box a value
I added the following in 2.656Okay try the 2.654 as I am using a 2023 version of the serial library I have run it all day without issue.
If it does it again I will add an option to select the baud rate.
Currently set to 115k