Transcription of CHIRP - #Bug 4125
1 CHIRP - Bug # 4125 Status:ClosedPriority:NormalAuthor:Steph en IrelandCategory:Created:10/11/2016 Assignee:Updated:10/12/2016 Due date: CHIRP affected:(All models)Platform:WindowsSubject:CH340G - based chips/adaptors: Not reading data correctlyDescriptionHi,The CH350G is a commonly used chip these days to supersede the get buffer-under-runs/over-runs with this chip when used with the latest supplied Wouxun KG-UVD1P -"Failed to communicate with radio: Failed to read full block (65!=64).Also unspecified issues with Baofeng works perfectly with FTDI (possibly fake) Windows 10 IVK3 VMHistory#1 - 10/11/2016 11:45 am - Brian Dickman- Status changed from New to ClosedUnfortunately, the functionality of the chip and driver is out of CHIRP 's control.
2 The program asks for data from the driver, and it is up to the cable chipand driver to return the correct amount of data. As you note, FTDI chips do work properly so we know CHIRP is behaving as expected. Werecommend using FTDI-based cables going forward. You may also refer to the cable guide page here: #2 - 10/12/2016 07:13 pm - Stephen IrelandHi,I actually find this to be a strange as the entire CHIRP project is dedicated to advancing the free and open access to hardware that is07/04/20201/2somewhat shunned by the traditionals - Icom, Yaesu.
3 Kenwood and major manufacturers such as reason that I raise the CH340G is in relation to its exposure out there with the Arduino "Clones" that I have been able to apply the CH340G in almost every application and see it work better than chips that are prices 10 - 100 times its only application that I cannot see it functioning correctly in is have seen this error a number of times before in very early CHIRP perhaps it is worthy of investigation/reinvestigation?Steve I#3 - 10/12/2016 07:33 pm - Dan SmithNo, really. As Brian says, CHIRP has no idea which driver or chip you're using.
4 It can't. It's insulated from all of that by the serial line disciplineabstraction layer of the operating system. We have no existing code in CHIRP that is specific to any driver or chip because we can'
