Latest WIN10 update version 2014

VK3KYY
Posts: 4003
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: Latest WIN10 update version 2014

Post by VK3KYY » Mon Feb 15, 2021 3:44 am

what happens when you read the codeplug?

vk2fmet
Posts: 55
Joined: Mon Jun 22, 2020 11:17 am

Re: Latest WIN10 update version 2014

Post by vk2fmet » Mon Feb 15, 2021 3:52 am

no problem reading - I can do it over and over no issue

VK3KYY
Posts: 4003
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: Latest WIN10 update version 2014

Post by VK3KYY » Mon Feb 15, 2021 4:10 am

Is the USB port USB 2 or 3 ?

How old is the radio? I recall some old ones having Write speed problems on the EEPROM

vk2fmet
Posts: 55
Joined: Mon Jun 22, 2020 11:17 am

Re: Latest WIN10 update version 2014

Post by vk2fmet » Mon Feb 15, 2021 4:19 am

USB 3, Com Port is COM9
The radio is less than a year

vk2fmet
Posts: 55
Joined: Mon Jun 22, 2020 11:17 am

Re: Latest WIN10 update version 2014

Post by vk2fmet » Mon Feb 15, 2021 4:22 am

the error message suggests a thread crash to me - one thread is getting ahead of where another expects it to be. Just something I tend to try in my thread code.. I look at the syncing and try a pause to test..

VK3KYY
Posts: 4003
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: Latest WIN10 update version 2014

Post by VK3KYY » Mon Feb 15, 2021 4:30 am

Ah,

You know that the source is available on github...

https://github.com/rogerclarkmelbourne/OpenGD77CPS

You could try running it in Visual Studio and see exactly where it freaks out

VK3KYY
Posts: 4003
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: Latest WIN10 update version 2014

Post by VK3KYY » Mon Feb 15, 2021 4:36 am

BTW.

I didnt write the threading code. I think Daniel F1RMB wrote it.

It does seem to use

Code: Select all

worker.RunWorkerAsync(dataObj);
But as far as I can tell, there should only be 1 async task running.

Perhaps

Code: Select all

void worker_DoWork(object sender, DoWorkEventArgs e)
is being called more than once ?

vk2fmet
Posts: 55
Joined: Mon Jun 22, 2020 11:17 am

Re: Latest WIN10 update version 2014

Post by vk2fmet » Mon Feb 15, 2021 4:38 am

I don't use VS. Bit of work getting a dev environment up for that.
I wasn't trying to tell you to suck eggs.
just thinking out loud.
happy to sit back down

vk2fmet
Posts: 55
Joined: Mon Jun 22, 2020 11:17 am

Re: Latest WIN10 update version 2014

Post by vk2fmet » Mon Feb 15, 2021 4:43 am

I was just reminded of many times where 2 threads are running as expected... and it takes only one small thing to make one thread to run longer than you think and you get a clash. Sometimes all you need to do is wait thru more development.. the code base grows, the tasks (or one task) gets slightly longer and the sync issue no longer presents... you never know there was an issue, it may never present again...

VK3KYY
Posts: 4003
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia
Contact:

Re: Latest WIN10 update version 2014

Post by VK3KYY » Mon Feb 15, 2021 4:48 am

VS Community Edition is really easy to install.

I'm sure I've seen the same error before, but I can't quite remember what was causing it.

I'll email F1RMB, as I think he added in the threaded stuff to the existing code that transferred the data.

BTW.

Did this stop working when Windows 10 updated ? or did you always have this problem.

Post Reply