[chirp_devel] driver file for Alinco DJ-500 with AnyTone protocol
Hi!
I own an Alinco DJ-500, which at least in the programming protocal uses the AnyTone protocol. I've got it basically talking with the AnyTone driver, still fiddling arround with the memory layout. So the good news is it's not difficult to get it running with chirp (actually I've reverse-engineered the protocoll, and while half through I found out about the parallels with AnyTone, tried that and... let's say I learned a lot...)
Now my question would be: Should the details be integrated in the AnyTone driver, or should the AnyTone driver be duplicated?
BR/73
Patrick OE6PSE
I own an Alinco DJ-500, which at least in the programming protocal uses the AnyTone protocol.
Well, technically the anytone radios copied the alinco protocol, but.. yeah :)
I've got it basically talking with the AnyTone driver, still fiddling arround with the memory layout. So the good news is it's not difficult to get it running with chirp (actually I've reverse-engineered the protocoll, and while half through I found out about the parallels with AnyTone, tried that and... let's say I learned a lot...)
Now my question would be: Should the details be integrated in the AnyTone driver, or should the AnyTone driver be duplicated?
It depends. If it's easyish to unify them that would really be best. We have a ton of duplication, but it largely comes from not being able to test refactors once we find a radio that shares something with an existing driver. However, I recall that alinco wireline code being pretty simple, so I think you could probably refactor them to share without much danger, right?
--Dan
participants (2)
-
Dan Smith
-
Patrick Strasser-Mikhail