NMT-450 real time clock #3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NMT phones, like Nokia 550 (THF-10) rely on network to set and show time, as they have no RTC build-in. This functionality is covered by http://download.eversberg.eu/mobilfunk/NMT-Dokus/NMT%20DOC%20450-1%20System%20Description%201997-08-08.pdf section 4.3.3.12.5 Additional information [OPTIONAL]. I'm not quite sure what frame it belongs to, but it doesn't seems to be implemented.
Yes, it is just not implemented. One would need to implement battery saving information and clock. (At least some dummy information that says that there are no phones or no frames for battery saving.) I have not tried it yet, because I don't have a phone that I know of that supports clock. In line 644 of nmt.c (frame->additional_info) must be set some valid clock frame as described on page 54.
frame->additional_info = 0xeb00000c40;
This sould give you 5 o'clock PM. It will not work with combinded TC+CC, so try CC only.
Understood, will do. My limesdr is still being delivered, so for next 2 weeks I'm out of luck testing that. On the other hand, I have quite a lot of NMT phones around, and can send you one that supports clock function. Just send me email with address where to (my email should be visible now) and I will send it to you, considering that you will be able to find 10-12V 3mm nokia charger or equivalent barrel plug and dc power supply.
Is the phone, that provides clock, NMT 900 or 450? The specs only give hints abount NMT 450 with clock. I guess that also NMT 900 supports that. (Note that many other codings are different between NMT 900 and NMT 450, not just the band.)
Sorry, delivery took longer than expected.
It's NMT-450. Tested with Nokia THF-10 and THF-11, and indeed phone shows "17:00" with the code change you suggested.
I have spare THF-11, and if your address on your home page is up-to-date I can send it (and some AMPS motorolas) to you.
@shadowcaster3 please be careful which website you're getting the contact details from. All the osmocom.org stuff lists me as contact (legal requirement in Germany).
Contact details fo @jolly are at http://eversberg.eu/contact/
Sure thing, it's strictly osmocom-analog and @jolly I was refering to.
Yes, the address on my homepage is valid.
Recently I pushd a patch that supports sending clock from machine's local time. You need to add "--clock 1" to your command line to enable it. Check if it works. Still it does not work with combined channel, as the specs say.
Works wonderfully. Thank you.
Can you try to change line 663 in nmt.c?
Change
if (nmt->send_clock && frame->mt != NMT_MESSAGE_1b) {
into
if (nmt->send_clock) {
.
It is out of spec, but I just want to know if it works with a combined TC-CC.
Phone signal level jumps erraticaly, can't seem to get proper scan of the network. Phone locks up when I try to place a call. No messages from osmocom-analog nmt console.
So you applied the patch, slected "--clock 1" and used CC+TC channel? What if you do not enable clock? Does your phone work then?
With the patch applied, this one prevents phone from registering:
This one works with the patch:
So effectively yes, if I use single channel, apply patch and enable clock it prevents phone from registering. Disabling clock fixes the problem.
On a combined channel the last three digits are used for area information and not for clock. This is why clock cannot be sent there. The phone rejects it, because it expects a valid area information. So it continues to search for a valid channel.