-
Notifications
You must be signed in to change notification settings - Fork 46
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
(Try to) Stabilize communication with DR1801UV #464
Comments
@DH1PK I've fixed the DR1801UV interface in the |
Thanks!
Building it right now.
Will test and report...
Am Mo., 22. Juli 2024 um 15:19 Uhr schrieb Hannes Matuschek <
***@***.***>:
… @DH1PK <https://github.com/DH1PK> I've fixed the DR1801UV interface in
the 464-... branch. It now syncs the reading with the start-of-packet
bytes and should ignore any garbage the A6 throws at qdmr.
—
Reply to this email directly, view it on GitHub
<#464 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEN2F3LY2KJYLPCJRP636Q3ZNUBFLAVCNFSM6AAAAABLIIVFJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBSHE2DEOJSGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
OK, different but not successful:
dmrconf -V -D ttyUSB0 -R DR1801UV write '2024-07-22 DR1801 01.yaml'
Debug in ***@***.***: Using format version 0.12.0.
Debug in ***@***.***: Read codeplug from '2024-07-22 DR1801
01.yaml'.
Debug in ***@***.***: Autodetect radios.
Debug in ***@***.***: Search for serial port with matching VID:PID
28e9:18a.
Debug in ***@***.***: Search for serial port with matching VID:PID
1fc9:94.
Debug in ***@***.***: Search for HID interfaces matching VID:PID
15a2:73.
Debug in ***@***.***: Search for DFU devices matching VID:PID
483:df11.
Debug in ***@***.***: Search for C7000 devices matching VID:PID
1206:227.
Debug in ***@***.***: Search for serial port with matching VID:PID
28e9:18a.
Debug in ***@***.***: Search for serial port with matching VID:PID
1fc9:94.
Debug in ***@***.***: Search for HID interfaces matching VID:PID
15a2:73.
Debug in ***@***.***: Search for DFU devices matching VID:PID
483:df11.
Debug in ***@***.***: Search for serial ports.
Debug in ***@***.***: Found ttyUSB0 (USB 1a86:7523).
Debug in ***@***.***: Search for C7000 devices matching VID:PID
1206:227.
Info in ***@***.***: Found 1 device(s):
Info in ***@***.***: Serial interface 'ttyUSB0'.
Debug in ***@***.***: Check if serial port ttyUSB0 still exisist
and has VID:PID 1a86:7523.
Debug in ***@***.***: Using device ttyUSB0.
Debug in ***@***.***: Check if serial port ttyUSB0 still exisist
and has VID:PID 1a86:7523.
Debug in ***@***.***: Try to detect radio at Serial interface
'ttyUSB0'.
Debug in ***@***.***: Try to open Serial interface 'ttyUSB0'.
Debug in ***@***.***: Opened serial port ttyUSB0 with 9600baud.
Debug in ***@***.***: Open interface to Auctus A6 based
radio.
Debug in ***@***.***: Send aa06010403bb
Debug in ***@***.***: Got response aa0781040183bb.
Debug in ***@***.***: Send aa06000006bb
Debug in ***@***.***: Got response
aa3a800001202c4246313830312c41362d303030302d585858582c706f727461626c652c3133364d2d3137344d2c3430304d2d3438304d2cfdbb.
Debug in ***@***.***:
,BF1801,A6-0000-XXXX,portable,136M-174M,400M-480M,
Warning in ***@***.***: Verification Issue: Warn: In : The
support for this radio is still under development. Some features may sill
be missing or are not well tested.
Warning in ***@***.***: Verification Issue: Warn: In List
'channels', Element 0 ('PMR 1'): Frequency 446.006MHz is outside of
allowed frequency ranges.
Warning in ***@***.***: Verification Issue: Warn: In List
'channels', Element 0 ('PMR 1'): Frequency 446.006MHz is outside of
allowed frequency ranges.
[ ] 0%
Debug in ***@***.***: Start upload to Baofeng DR-1801UV.
Debug in ***@***.***: Send aa0a01000001c200c8bb
Debug in ***@***.***: Got response
aa158100010001dd90000000680002e69eb892e1bb.
Debug in ***@***.***: Set baudrate to 115200.
[ ] 0%
[========================= ] 50%
Debug in ***@***.***: Reset baudrate to 9600.
Debug in ***@***.***: Send aa06010403bb
Debug in ***@***.***: Got response aa0781040183bb.
Debug in ***@***.***: Send
aa12010200010001da8c42e90000258049bb
Debug in ***@***.***: Got response aa08810201008abb.
[========================= ] 50%
[==================================================] 100%
Debug in ***@***.***: Receive write-ACK.
At this point the debug output stops and the TRX does a reset as if a
successfull upload had happened.
The data on the TRX is unchanged, still the factory configuration.
After the TRX reset is finished and the chinese frequencies are up on the
display again the debug output continues:
ERROR in ***@***.***: Serial port error: (12) Operation timed out.
ERROR in ***@***.***: QSerialPort: Operation timed out
ERROR in ***@***.***: Cannot read response 103h.
ERROR in ***@***.***: Cannot complete codeplug write.
ERROR in ***@***.***: Cannot finish write operation
properly. Partial write?
ERROR in ***@***.***: Cannot write codeplug to the device.
Debug in ***@***.***: Serial port will close now.
Debug in ***@***.***: Upload completed.
Regards,
Patrick
Am Mo., 22. Juli 2024 um 15:52 Uhr schrieb cologne bynight <
***@***.***>:
… Thanks!
Building it right now.
Will test and report...
Am Mo., 22. Juli 2024 um 15:19 Uhr schrieb Hannes Matuschek <
***@***.***>:
> @DH1PK <https://github.com/DH1PK> I've fixed the DR1801UV interface in
> the 464-... branch. It now syncs the reading with the start-of-packet
> bytes and should ignore any garbage the A6 throws at qdmr.
>
> —
> Reply to this email directly, view it on GitHub
> <#464 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BEN2F3LY2KJYLPCJRP636Q3ZNUBFLAVCNFSM6AAAAABLIIVFJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBSHE2DEOJSGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
But anyway, this is new:
Debug in ***@***.***: Receive write-ACK.
Am Mo., 22. Juli 2024 um 16:31 Uhr schrieb cologne bynight <
***@***.***>:
… OK, different but not successful:
dmrconf -V -D ttyUSB0 -R DR1801UV write '2024-07-22 DR1801 01.yaml'
Debug in ***@***.***: Using format version 0.12.0.
Debug in ***@***.***: Read codeplug from '2024-07-22 DR1801
01.yaml'.
Debug in ***@***.***: Autodetect radios.
Debug in ***@***.***: Search for serial port with matching
VID:PID 28e9:18a.
Debug in ***@***.***: Search for serial port with matching
VID:PID 1fc9:94.
Debug in ***@***.***: Search for HID interfaces matching
VID:PID 15a2:73.
Debug in ***@***.***: Search for DFU devices matching VID:PID
483:df11.
Debug in ***@***.***: Search for C7000 devices matching
VID:PID 1206:227.
Debug in ***@***.***: Search for serial port with matching
VID:PID 28e9:18a.
Debug in ***@***.***: Search for serial port with matching
VID:PID 1fc9:94.
Debug in ***@***.***: Search for HID interfaces matching
VID:PID 15a2:73.
Debug in ***@***.***: Search for DFU devices matching VID:PID
483:df11.
Debug in ***@***.***: Search for serial ports.
Debug in ***@***.***: Found ttyUSB0 (USB 1a86:7523).
Debug in ***@***.***: Search for C7000 devices matching
VID:PID 1206:227.
Info in ***@***.***: Found 1 device(s):
Info in ***@***.***: Serial interface 'ttyUSB0'.
Debug in ***@***.***: Check if serial port ttyUSB0 still exisist
and has VID:PID 1a86:7523.
Debug in ***@***.***: Using device ttyUSB0.
Debug in ***@***.***: Check if serial port ttyUSB0 still exisist
and has VID:PID 1a86:7523.
Debug in ***@***.***: Try to detect radio at Serial interface
'ttyUSB0'.
Debug in ***@***.***: Try to open Serial interface 'ttyUSB0'.
Debug in ***@***.***: Opened serial port ttyUSB0 with 9600baud.
Debug in ***@***.***: Open interface to Auctus A6 based
radio.
Debug in ***@***.***: Send aa06010403bb
Debug in ***@***.***: Got response aa0781040183bb.
Debug in ***@***.***: Send aa06000006bb
Debug in ***@***.***: Got response
aa3a800001202c4246313830312c41362d303030302d585858582c706f727461626c652c3133364d2d3137344d2c3430304d2d3438304d2cfdbb.
Debug in ***@***.***:
,BF1801,A6-0000-XXXX,portable,136M-174M,400M-480M,
Warning in ***@***.***: Verification Issue: Warn: In : The
support for this radio is still under development. Some features may sill
be missing or are not well tested.
Warning in ***@***.***: Verification Issue: Warn: In List
'channels', Element 0 ('PMR 1'): Frequency 446.006MHz is outside of
allowed frequency ranges.
Warning in ***@***.***: Verification Issue: Warn: In List
'channels', Element 0 ('PMR 1'): Frequency 446.006MHz is outside of
allowed frequency ranges.
[ ] 0%
Debug in ***@***.***: Start upload to Baofeng DR-1801UV.
Debug in ***@***.***: Send aa0a01000001c200c8bb
Debug in ***@***.***: Got response
aa158100010001dd90000000680002e69eb892e1bb.
Debug in ***@***.***: Set baudrate to 115200.
[ ] 0%
[========================= ] 50%
Debug in ***@***.***: Reset baudrate to 9600.
Debug in ***@***.***: Send aa06010403bb
Debug in ***@***.***: Got response aa0781040183bb.
Debug in ***@***.***: Send
aa12010200010001da8c42e90000258049bb
Debug in ***@***.***: Got response aa08810201008abb.
[========================= ] 50%
[==================================================] 100%
Debug in ***@***.***: Receive write-ACK.
At this point the debug output stops and the TRX does a reset as if a
successfull upload had happened.
The data on the TRX is unchanged, still the factory configuration.
After the TRX reset is finished and the chinese frequencies are up on the
display again the debug output continues:
ERROR in ***@***.***: Serial port error: (12) Operation timed
out.
ERROR in ***@***.***: QSerialPort: Operation timed out
ERROR in ***@***.***: Cannot read response 103h.
ERROR in ***@***.***: Cannot complete codeplug write.
ERROR in ***@***.***: Cannot finish write operation
properly. Partial write?
ERROR in ***@***.***: Cannot write codeplug to the device.
Debug in ***@***.***: Serial port will close now.
Debug in ***@***.***: Upload completed.
Regards,
Patrick
Am Mo., 22. Juli 2024 um 15:52 Uhr schrieb cologne bynight <
***@***.***>:
> Thanks!
>
> Building it right now.
> Will test and report...
>
>
> Am Mo., 22. Juli 2024 um 15:19 Uhr schrieb Hannes Matuschek <
> ***@***.***>:
>
>> @DH1PK <https://github.com/DH1PK> I've fixed the DR1801UV interface in
>> the 464-... branch. It now syncs the reading with the start-of-packet
>> bytes and should ignore any garbage the A6 throws at qdmr.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#464 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/BEN2F3LY2KJYLPCJRP636Q3ZNUBFLAVCNFSM6AAAAABLIIVFJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBSHE2DEOJSGY>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> ***@***.***>
>>
>
|
Okay, this is going to be a though one. I can actually reproduce the problem with my device. One reason, that the upload is so slow, is, that I need to do it with 96kBaud only. If I change the speed to anything else, the radio will show exactly that weird behavior. However, I do not want to delay the 0.12.0 release for that. So, for the time being, the RD1801UV will be unreliable. |
TRX stayed in "Memory prog..." mode during the whole upload process, but no
success.
Regards,
Patrick
The text was updated successfully, but these errors were encountered: