Know it's a long shot by now to ask about this, but I have to try.
My KSU is a KX-TD816BX, no silver sticker, bog standard P401A firmware. Works fine, no issues whatsoever (except clock and RTC battery, but that's another story.)
I've installed a KX-TD193DX Caller ID board on it. However, despite going to program [406] and enabling Caller ID for all CO lines, I get nothing... Either on DPT screens or SMDR output. It's the same thing as the card wasn't there.
Now, the guy who sold me the pull card told me that some systems may be incompatible with the DX variant (that, besides also processing DTMF, seems to be a widely different project.) Is it true?
Things that I tried thus far: - Connected a PSTN phone to T1/R1 corresponding pins (I get tone, as expected, so no continuity issues); - Tried a lot of different CID protocols using PAP2T; - Enabled CPC (100ms), though I don't think that has anything to do with it — I just did it because "CPC" is printed on the card; - Resetting the entire thing (system data clear); - Tried to change some COS bits based on poorly translated info. from here (but not only it's for KX-T1232, but probably the RU version, on P211P, albeit this makes me thing there is, somewhere, some flag I probably have to toggle for it to work.)
I'm very tempted, at this point, to get all those lines hooked up to my old R-Pi to see if I get any data on D0-D7... But, if I can't make it work, I'll probably just return it.
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
It's been a loooong time since I touched an 816, and always programmed from the telephone! Afraid I'm of no help here...
Old system, indeed. But it was cheap, got intercom and still a bit interesting piece of tech to play around.
In other news, I've searched everything across Google and USENET and didn't find much information on the subject, though some Cyrillic-writing folks do suggest this board may have compatibility issues with some ye' olde TD1232 ROM's. Since those two are nearly twins, I'm gonna assume this also holds true for TD816. Another possibility is that some obscure SYS or COS bit needs to be set for the system to be able to work with that hardware. The only thing that surprises me in that is the fact this little card was manufactured back in 1993, whilst my KSU got a 1996 ROM, so it may well be a regional thing.
The seller told me he knows some old folks who probably know something about it. There's a thin chance someone got this forgotten piece of knowledge written at back of some paper bag out there. I'll check with him and report back.
He also doesn't have the pure FSK version, i.e. TD193X, so whatever happens, I guess I'll have to make do with that one. That stuff is incredibly hard to find around here, and, though I love those Panasonic systems, I have to say they've gone on full Apple on those. It's quite infuriating how murky waters get when it comes to compatibility of modules between only slightly different regional versions of the same model.
Get yourself a Panasonic TDA50G, it should have the Caller ID module already installed. It supports the 7200 and 7400 series telephones, and can be programmed from a phone. Panasonic manufactured them for about 18 years, plenty of them out there and cheap. Kevin
Get yourself a Panasonic TDA50G, it should have the Caller ID module already installed. It supports the 7200 and 7400 series telephones, and can be programmed from a phone. Panasonic manufactured them for about 18 years, plenty of them out there and cheap. Kevin
I could entertain this possibility, indeed. Albeit they're a bit hard to come by around here, sometime ago I was able to find a reasonably priced KX-TDA30BR for what would be equivalent to fifty bucks, roughly. I'll be on the lookout.
Meanwhile, I'm holding on to this old kicker. It has been serving well, for now.
Update: after getting information from the card seller (also available here) for D1232, it looks like only recent ROM's will work with 193DX. Why they made two cards, with same connections and same functions, speak two different kind of data is definitely beyond me. Also, I haven't been able to find specific information on D816, but I assume this forum post is correct on it's versions:
Quote
KX-TD816 Chip information: -0 P011 Non-DPITS pre-DPITS 8MHz CPU. 2MB, RAM 256K -0.5 P051I / first DPITS 8MHz CPU. 4MB, RAM 256K -1 P401A / B DPITS 8MHz CPU. 4MB, RAM 256K (Suffix of Serial No. "N?"), RAM 1M (Suffix of Serial No. "O?") -2 P301C / H 12MHz CPU. 8MB -3 P301I / O / U 12MHz CPU. 8MB -4 P311D / H -5 P311K / M / P -6 P311Q -7 P311W
Albeit, it's a bit strange, because my TD816 has lots of things (Lunch break, VM Port Name, Selectable FWD/DND light pattern et. al.) that seems be associated with the -4 version (cf. attachment.) The CPU (TMP68301AF-12) also seems to be a 12 MHz one. So, IDK, maybe it's a BX-model thing, whilst that information only applies to the RU variant.
At any rate, though, it seems like it's a software question. The P401A simply won't support it.
So, at this point, I might as well either try my hand and try changing the ROM (as well as upgrading the socketed RAM)or jerry rig something with a ESP32 along the path to pop some notification at my KDE desktop. Or, better yet, if I still have any sanity left, just do as my illustrious colleague C5Z suggested and get a reasonably priced KX-TDA box.