-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AnyTone D578UVII Uses Different USB VID and PID, Following Changes Read Radio #415
Comments
Possible solution to above changes to support old Anytone VID/PID as well as new Anytone VID/PID:
|
This kind of bug is present on all radios where serial communication is used, why qdmr is masking this with USB ids is beyond me. |
@ken-clifton , @galagithub : Is this related to #196 and/or #370? |
@ken-clifton : which of the models in https://www.wouxun.us/images/D578UV-Family.jpg is your radio? Or yet a different one? |
@ken-clifton : since the title of this issue reads "AnyTone D578UVII Uses Different USB VID and PID, Following Changes Read Radio" and also "I noticed my AnyTone D578UVII uses different a different USB VID and PID than those defined near the top of anytone_interface.cc" I just wanted to confirm that it is indeed a "D578UVIII Plus" according to that table and not yet another model Anytone came up with - since there is a "D578UVII" mentioned in https://www.wouxun.us/Software/AnyTone-Software/AT-D578UVII-PLUS-v2.06.2-Changelog.pdf .. |
@allesand I appreciate you checking. Several of the AnyTone D578 series report as "D578UV2" in the USB information. |
If different models with different options in the codeplug report the same model via USB, @hmatuschek will not be happy, since from what I understood Anytone does not encode the model in the data read from the radio. But I will leave that up to @hmatuschek, just wanted to gather as much info as possible. |
This comment was marked as abuse.
This comment was marked as abuse.
Re: #285 and #389, end of discussion for me. @galagithub : good to read that you got a good laugh, maybe that will make your discussion more ham-spirit like. Side note: your "!" seems to be stuck. |
This would do well to explain why I received the "No radio found: No matching device was found" information dialog upon attempting to detect my product in v0.11.2 I am using Distributor ID: Pop lsusb output2e3c:5740 Artery AT32 Virtual Com Port My Anytone AT-D578UV III Pro usually shows up around /dev/ttyACM0: USB ACM device Probe in syslog I would be more than happy to assist where I can with this issue. Would there be anything additional you need? FYI, I am pretty sure the model I have uses the D578UV_1.20(AT) firmware. I am unsure how this will impact the complexity of the issue at hand but you may benefit from a file that was was included "Which firmware to use for D578UV.txt" of which the content below could be highly relevant:
Hope this helps, Chris WRUH997 |
I noticed my AnyTone D578UVII uses different a different USB VID and PID than those defined near the top of anytone_interface.cc
Not sure of the best approach should you want to get QDMR working for both the "old" and "new" VID and PID ?
Here are the changes I implemented in 0.11 to successfully read from the radio:
In /lib/anytone_interface.cc
changed VID/PID to - VID: 2e3c PID: 5740
Also in /lib/anytone_interface.cc
Added line below:
} else if ("D578UV" == _info.name) {
return RadioInfo::byID(RadioInfo::D578UV);
}
As:
else if ("D578UV2" == _info.name) {
return RadioInfo::byID(RadioInfo::D578UVII);
}
In /lib/radioinfo.hh
Below D878UVII,
Added D578UVII,
Also in /lib/radioinfo.hh
below D578UVII,
Added D578UV = D578UVII, // Actually a different device, Implement!
In /lib/radioinfo.cc
Below line: {"d578uv", RadioInfo::D578UV}
Added: a comma ( , ) then on next line
{"d578uv2", RadioInfo::D578UVII}
Also in /lib/radioinfo.cc
Below line: {RadioInfo::D578UV, D578UV::defaultRadioInfo()},
Added:
{RadioInfo::D578UVII, D578UV::defaultRadioInfo()},
In /lib/radio.cc
Below line: return new D578UV(anytone);
Added:
} else if ((id.isValid() && (RadioInfo::D578UVII == id.id())) || (force.isValid() && (RadioInfo::D578UVII == force.id()))) {
return new D578UV(anytone);
In /lib/d578uv.cc
Changed the lines at the bottom below:
RadioInfo
D578UV::defaultRadioInfo() {
return RadioInfo(
To:
RadioInfo::D578UVII, "d578uv2", "AT-D578UVII", "AnyTone", AnytoneInterface::interfaceInfo(),
QList{
RadioInfo(RadioInfo::D578UV, "d578uv", "AT-D578UV", "AnyTone", AnytoneInterface::interfaceInfo())
});
The text was updated successfully, but these errors were encountered: