next »

Would there be any chance of a Write-with-verify option, please?

I set up a load of systems last night, writing hundreds of channels (about 40% of the 230's memory) and when I went through them to check, it had mucked up about 5 or 6 that ended up as frequency 0.00000.
I had to go through and work out which they should have been, enter the frequencies manually, and name them the hard way, etc.
There was nothing odd about any of them as set up in the program, correct frequencies/steps and names not that different from the others alongside them.

It's probably my cheapo PL2303 lead at fault (running at 19200 because top speed isn't reliable - it made FreeSCAN seize up),
 but all the same it would be wonderful if FreeSCAN could have an option to check the upload afterwards - reading back from the scanner, memory by memory, comparing with what it thought it had uploaded - and correcting any mistakes (with a report dialog of how many errors it had fixed).

That would give me so much extra confidence in the product, it would be the dog's danglies as we say here in Britain 

73

I would eliminate any USB extension cords or HUBs that you may be using, they could be causing this problem. Beyond that, you can also lower the UART buffer down to zero in the driver's properties and that might help as well..

If those don't help, than you probably just had the misfortune of either getting a bad convertor or the world's worst knockoff - I'm not sure which but the problems you describe seem to indicate bad hardware. It's not worth it for me to code around defective hardware, just the same what do you think Microsoft would say if you asked them to code Windows to work with defective ram?

The only other thing the could be causing this issue is if you have your decimal separator set to a comma or something else other than a period. This tends to muck things up in upload time, though granted it usually affects just about every frequency that isn't a whole number.

Fair enough, I do understand that it's not much fun writing an involved routine just for an odd case like mine - I just can't help wondering how common it is? It looked like a best-selling USB/Serial from Amazon, so it's not exactly obscure - but then the official drivers wouldn't work, so it's probably a knock-off chip in there. Maybe other people have had the same problem but haven't said anything? Who knows 
At least FreeSCAN works 99% for me    whereas BCTool was a nightmare, so overall I'm still very grateful.

Doesn't look like there's anything wrong with the sys/grp setup in the programme itself, it's just the data transfer going wrong - it could even be something unique to the usc230 for all I know - you guys over the other side of the water don't really get any hands-on experience of stuff made for us limeys!

I'll try the buffers suggestion, thanks for that.
73

I wonder if you just have a bad unit. If you were getting the Code 10 errors with the official drivers, it means you have a counterfeit. The ones posted on this site are older ones not smart enough to discriminate so they will work with yours. My adapters are all fakes as well but I haven't had any issue.