# Any way to make a non CM108-CM119 compatible sound chip radio interface? **URL:** https://community.allstarlink.org/t/any-way-to-make-a-non-cm108-cm119-compatible-sound-chip-radio-interface/22372 **Category:** AllStarLink **Created:** [November 28, 2024, 3:11am UTC](https://community.allstarlink.org/t/any-way-to-make-a-non-cm108-cm119-compatible-sound-chip-radio-interface/22372 "2024-11-28T03:11:20Z") **Posts on this page:** 1 **Showing post:** 9
### Author: ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike) #### Post date: [November 30, 2024, 1:28pm UTC](https://community.allstarlink.org/t/any-way-to-make-a-non-cm108-cm119-compatible-sound-chip-radio-interface/22372/9 "2024-11-30T13:28:31Z")
> [@n8lbv](#): > > I was asking this back in 2010. > I’ve always thought it would be fun or cool to use the built in audio on a laptop or PC motherboard that is already there. > In that case COS and PTT would be on a serial port or parallel port (also built in to thePC). Well, I agree that something else needs to appear. But to take you back to 2010, on a PC, you could have. And still can. Using the parallel port (not a usb parallel adapter) to obtain cos /ptt , the sound unit is much less critical. For the software addresses for extracting those lines change with other adaptors and likely other things that are specific to that sound dongle. My 1st private node back then actually did this with the built-in sound on a PC with a parallel port. But there is only one built-in sound and I had 3 private nodes then, so I just used the cm108’s and disabled the built-in as the motherboard was giving me issues with the shared IRQ supporting that built-in sound and I never looked back. Of course this is no help with a Pi unless you separate the hardware interfacing with some other means. Every couple of years I load a Pi up and experiment with something on this. The best results came from the I2C interface. And one can generate enough I/O to serve up 4 nodes+ and still have plenty of switches/inputs to play with. Then I come to find out there was an attempt to do this already and has been buried in the code and not released since the passing of it’s author. I did take some notes for others to follow. > [@Raspberry Pi and DMK eng PITA Board](https://community.allstarlink.org/t/raspberry-pi-and-dmk-eng-pita-board/20501): > > The purpose of this post is 2 fold. To provide all the general information I have at this time to the topic in the hopes that those interested in it will band together and will do something with it. Just trying to speed you up? To some of those same folks, to stop them from asking me by email and PM’s the same and proposing I do something as I am not interested and repeating much of the same info I’m putting here… I have plenty of irons in the fire. So I will refer this post when asked in … But the framework is in there in the source to extract the code just for the i2c interfacing. But I am looking in one other direction now and I am not sure when I will have time to sit with it again. I really don’t use the Pi for anything in Ham Radio/ASL, but I might. I am using Pi’s with a i2c for other utility purposes. So will anyone pick it up and run with it… I doubt it. I may after retirement. No incentive at present. This discussion comes around at least once a year for over the last decade. --- _[View the full topic](https://community.allstarlink.org/t/any-way-to-make-a-non-cm108-cm119-compatible-sound-chip-radio-interface/22372)._