|
Title: Ch340. Why doesn’t it work? Post by: 1slwb5 on May 13, 2019, 12:18:58 PM All I read is that it doesn’t work but no one has asked the question of why.
So I’m asking it. Is it an IO conflict? Title: Re: Ch340. Why doesn’t it work? Post by: Blazius on May 13, 2019, 04:36:40 PM work with what?
Title: Re: Ch340. Why doesn’t it work? Post by: 1slwb5 on May 15, 2019, 09:00:58 PM Nefmoto software
Title: Re: Ch340. Why doesn’t it work? Post by: nyet on May 15, 2019, 09:19:42 PM It relies on the FTDI API. Not really sure what you mean by "IO conflict".
Title: Re: Ch340. Why doesn’t it work? Post by: Blazius on May 16, 2019, 05:37:40 AM Ch340 provides the same exact functionality as an ftdi chip, however nefmoto is written using the ftdi api/drivers as ftdi chips carry an unique unchangeable id, etc., and nefmoto uses this. If nefmoto would be written with COM port support it should work.
Title: Re: Ch340. Why doesn’t it work? Post by: nyet on May 16, 2019, 08:13:52 AM Ch340 provides the same exact functionality as an ftdi chip, however nefmoto is written using the ftdi api/drivers as ftdi chips carry an unique unchangeable id, etc., and nefmoto uses this. If nefmoto would be written with COM port support it should work. The thing is, nef is now fully open source and does not even rely on the ID thing any more... Again, all the source is on github, I would welcome anyone to take a look and issue pull requests. Title: Re: Ch340. Why doesn’t it work? Post by: nyet on May 16, 2019, 08:17:58 AM Just opened this
https://github.com/NefMoto/NefMotoOpenSource/issues/16 Title: Re: Ch340. Why doesn’t it work? Post by: Blazius on May 16, 2019, 03:25:45 PM The thing is, nef is now fully open source and does not even rely on the ID thing any more... Again, all the source is on github, I would welcome anyone to take a look and issue pull requests. I would but my programming skills arent there for this kinda of job. I only worked in preset system and cases. I wish I would be able to help though. |