Latest WIN10 update version 2014
Re: Latest WIN10 update version 2014
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
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
Re: Latest WIN10 update version 2014
BTW.
I didnt write the threading code. I think Daniel F1RMB wrote it.
It does seem to use
But as far as I can tell, there should only be 1 async task running.
Perhaps is being called more than once ?
I didnt write the threading code. I think Daniel F1RMB wrote it.
It does seem to use
Code: Select all
worker.RunWorkerAsync(dataObj);
Perhaps
Code: Select all
void worker_DoWork(object sender, DoWorkEventArgs e)
Re: Latest WIN10 update version 2014
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
I wasn't trying to tell you to suck eggs.
just thinking out loud.
happy to sit back down
Re: Latest WIN10 update version 2014
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...
Re: Latest WIN10 update version 2014
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.
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.
Re: Latest WIN10 update version 2014
I have never had this issue before today.
Very reliable normally.
I can't sync the updates lately... I mean my windows updates when it forces me so I don't take notice of the builds. I've had 10 for a while now.
I am on Version 2004, 23.09.2020 OS Build 19041.804
Suggests I've had it for a while and therefore definitely done a few updates of GD77 since Sep last year.
Very reliable normally.
I can't sync the updates lately... I mean my windows updates when it forces me so I don't take notice of the builds. I've had 10 for a while now.
I am on Version 2004, 23.09.2020 OS Build 19041.804
Suggests I've had it for a while and therefore definitely done a few updates of GD77 since Sep last year.
Re: Latest WIN10 update version 2014
Did you update the firmware ?vk2fmet wrote: ↑Mon Feb 15, 2021 5:00 amI have never had this issue before today.
Very reliable normally.
I can't sync the updates lately... I mean my windows updates when it forces me so I don't take notice of the builds. I've had 10 for a while now.
I am on Version 2004, 23.09.2020 OS Build 19041.804
Suggests I've had it for a while and therefore definitely done a few updates of GD77 since Sep last year.
Re: Latest WIN10 update version 2014
Umm
Just tried it on my W10 machine and I'm now getting the same error.
I'll try reverting the firmware.
I think this may actually be a timeout error.
Just tried it on my W10 machine and I'm now getting the same error.
I'll try reverting the firmware.
I think this may actually be a timeout error.
Re: Latest WIN10 update version 2014
Yep.
Its comms timeout error.
The comms speed got reduced after I fixed a serious bug with the CPU being accidental overclocked by 50% from the very beginning of the project.
(Not my original code)
Looks like somehow this has caused a bug on W10, but not on W7 or W8 etc.
I'll need to see if its also related to USB type, i.e USB 3.
Anyway, the thread message is potentially misleading
Its comms timeout error.
The comms speed got reduced after I fixed a serious bug with the CPU being accidental overclocked by 50% from the very beginning of the project.
(Not my original code)
Looks like somehow this has caused a bug on W10, but not on W7 or W8 etc.
I'll need to see if its also related to USB type, i.e USB 3.
Anyway, the thread message is potentially misleading
Re: Latest WIN10 update version 2014
yes - all possible there.
I updated the firmware without issue. It's just the code plug write that has the issue.
Alan
I updated the firmware without issue. It's just the code plug write that has the issue.
Alan