hamradionl
Member
- Joined
- Mar 23, 2014
- Messages
- 730
if you say so.RMW1010 said:I doubt it, so stop spreading false info.
DV10?
Last edited:
if you say so.RMW1010 said:I doubt it, so stop spreading false info.
No idea, do you?If you mean DV10 then just say it in the first place.
What network info will the DV10 give you?
No idea, do you?
DV1, DV10 or S200 used as example that not need to register to network for using as receive only (TX off). We do it all the time using TSSDR, TTT or DSDplus so its possible Sorry, there is little "itchy" for now let it pass, later when the stress for flu is over and the body temp is down, thanks"But I have also head about a firmware that is only used for receiving but I have never seen this"
I suppose there are special FW versions for monitoring purposes, but probably guarded like a treasure. In theory it should not be too tricky to tell a terminal to follow a certain ISSI (ie to "pretend" to be an already logged in terminal, without demanding confirmation of registration on the network - i.e. no TX at all). But it would only work if the receive only terminal is on the same site as the terminal it is emulating of course.Normal you can set radio Talk groups to receive only. But it will still try to register before it can be in use.
Even base station that I can hear fine in TTT do not received by DV10. Absolute crap in my opinion.
I have try the more expensive AOR DV1 and this seems to work better but still no information about GSSI or ISSI.
I don't know what this zello is. Or what it does or your requirements to stream to a remote device.
No such receive only, monitor mode in depot cps. You'll need to use a special dongle, shipped by curier, and be online to M server to use depot but still no way to monitor without being detected in the tetra system. It needs to be a hacked firmware that fools the code that it always gets the proper acknowledment to every registration attempt, but the actual transmit function are totally disabled.I was wondering if it is a setting you can set if you have Tetra CPS Plus DEPOT software and not a special firmware.Normal you can set radio Talk groups to receive only. But it will still try to register before it can be in use.
I don't think this is a bug but rather a system specific issue.
Some where have this problem awhile ago, see this post here for a possible solution.
Since I'm not able to reproduce the error I'm not able to investigate it further.
Latest version (v1.7.1.0) can be found here: Release post
Happy the solution worked for you.I changed from MME Virtual Cable to Directsound Virtual Cable, it's now recording calls. The problem was MME. Thanks for the help.
Can you let me know what virtual audio cable program you use:
Thanks for the reply.It is VB-Cable, haven't tried the other one yet so I don't know if it's better.
I'm not even sure about the difference between MME and DirectSound.
me to having frequent freeze when recording audio. I have Intel I7 laptop with 8gb of ram, Windows 10 64 bit, SDR#1732 and when I start TTT with recording, it freeze immediately, even when no communication. If I uncheck recording, TTT work wells for days without freezing.Thanks for the reply.
I have just tested with VB-CABLE using "[MME] Cable Input" with the following with no issues:
I really can't think of anything else as to why MME works for some people and not others.
- Windows 7 Pro - 32 bit
- Windows 10 - 64 bit.
- SDR# 1700 and SDR# 1732
I still think this is a system specific issue. What that issue actually is, is anyone's guess.
Do you use a Desktop/Laptop/Tablet PC and what version of Windows 10 are you using. (Home, Professional, Other?)
Latest version (v1.7.1.0) can be found here: Release post
So did you try the suggested solution?me to having frequent freeze when recording audio. I have Intel I7 laptop with 8gb of ram, Windows 10 64 bit, SDR#1732 and when I start TTT with recording, it freeze immediately, even when no communication. If I uncheck recording, TTT work wells for days without freezing.
Do you have this receive only firmware for a TETRA handheld? I doubt it, so stop spreading false info.
Wouldn't you still need to register on the network and authenticate on it (valid ISSI, TEI, K-key)?You don't need RX only firmware. Some TETRA terminals (and when I say some, I only know of the Motorola MTP700) can be programmed to scan a system talkgroup from a DMO channel. In that very limited circumstance, you can receive "RX Only". There are a pile of "gotchas" though, such as you can only receive the GSSI on the system, as that of the DMO channel you're on. You can also only have (IIRC) 8 DMO channels in the radio. So, you'd be limited to 8 talkgroups. It isn't a practical way at all to do it, but not impossible.
Wouldn't you still need to register on the network and authenticate on it (valid ISSI, TEI, K-key)?
Sorry, but this doesn't make sense. DMO has no system infrastructure. Or do you mean MCC and MNC of DMO Talkgroup needs to match TMO?There are a pile of "gotchas" though, such as you can only receive the GSSI on the system, as that of the DMO channel you're on.
MTP700 can have 208 DMO TalkgroupsYou can also only have (IIRC) 8 DMO channels in the radio. So, you'd be limited to 8 talkgroups. It isn't a practical way at all to do it, but not impossible.
Thanks for the reply.
I have just tested with VB-CABLE using "[MME] Cable Input" with the following with no issues:
I really can't think of anything else as to why MME works for some people and not others.
- Windows 7 Pro - 32 bit
- Windows 10 - 64 bit.
- SDR# 1700 and SDR# 1732
I still think this is a system specific issue. What that issue actually is, is anyone's guess.
Do you use a Desktop/Laptop/Tablet PC and what version of Windows 10 are you using. (Home, Professional, Other?)
Latest version (v1.7.1.0) can be found here: Release post