John wrote: > > > Ok, I have the 92AD and the D800H setup as follows: > > UR: CQCQCQ > RPT1: KD0CGR C > RPT2: KD0CGR G > > When I TX on the 92AD the readback data appears to be fine but on the > D800H I get the > RPT*
Completely normal. The ID-800H doesn't display the repeater callsign, but it does STORE it, and you can view it via a menu. The IC-92AD displays the complete repeater reply, including the callsign. Different "generations" of rigs. > Now, the local repeater does not have a gateway but is linked to a > different repeater 50 > miles away that does have a gateway and I think that is why the port > designation on RPT2 > as G. RPT2: Set to G is you requesting to route your audio stream to the Gateway. If the system is linked to another via dplus (add-on software that allows Gateway to Gateway linking -- the bare Icom software doesn't have this feature), then everything you've been told to do is correct. To be heard on both systems you would set RPT2 to the Gateway. Your transmissions are always heard on the local repeater you come in through, and setting RPT2 to the Gateway sends your audio stream over to it also. The Gateway then has the "intelligence" to know it's connected via dplus linking to another system, and it forwards the packets over to Gateway 2 in the network. Routing to the Gateway via RPT2 at all times also has the benefit of allowing any DV-Dongle users connected to your Gateway from the Internet, to hear you and join in your conversation. Otherwise, only the local repeater RF users will hear you, and the Dongle will remain silent. Does that make sense? > I would think icom would keep the same convention in their transceivers. No, the ID-800H was designed from a previous analog-only rig, with add-ons for D-STAR, if you look it over carefully. The next rig designed was the IC-91AD, which is pretty much the same software as it's later bretheren the IC-92AD, but Icom added features like four power levels, the ability to use a fancy GPS microphone with a funny connector, and a bigger size for heatsinking to the IC-92AD. The IC-92AD is kinda the "fixed" version of the IC-91AD, although I'm not trying to knock the 91 too hard. I own one. But for anything more than a few minutes of transmit on high power, you need an oven mitt to hold on to the thing. Then came the IC-2820. It's the first mobile rig with the features and user interface work found in the IC-91AD and IC-92AD. So if you just look at the release history you start to see how they got "easier to use" and display more data as the line of rigs came along. Personally I think if you use your TIME to learn how to do EVERYTHING on the ID-800H from the menus, etc... it's time well spent. Because at a $400 price differential between that rig and the 2820... I can work a lot of hours at studying how to do things on the ID-800H (and hey, I'm going to operate the rig anyway!) and not lose money on the deal. If you have the budget and you're pressed for time and want a shallower learning curve, the 2820 is slightly better. > On another question Can the text to be transmitted on the D800 along > with voice such as > location, name, etc be placed anywhere? Not sure what you mean. Text with locations and things is called the "text message" in the programming software (since you mention you have that software below), and you can choose one of the text messages as a "default" message to send, and also turn on the sending of text messages during each transmission. This is commonly used for location, name, etc... by end-users, but you could literally put anything in there. > I am utilizing the icom software for programming on a laptop. It makes things a lot easier, but at some point you do want to "wean" yourself from this -- to really know the rig. Being able to route to stored callsigns in the menus is something that only requires about 4 button presses if you pre-load the callsigns of your buddies throughout the world, and the Icom callsign routing via a Gateway does work VERY well. You do NOT want to mix callsign routing with a system that's "permanently" linked via dplus however. That's a problem today, as both Icom's software and the Dplus software will be sending streams out to different Gateways during your transmission, leading to confusion. Unlink the dplus (if your local gateway operators allow that - it's configurable) or use the other band module if they have decreed that one module is always linked and the other is open for use. Or however your local "powers that be" like to use the system. Just ask them where they'd like you to do "Icom style callsign routing" and they'll tell you. > Appreciate any assistance! No problem, hope it helps... it makes more sense after a while of doing it. Kinda like learning to ride a bike... Have fun with it John. A D-STAR repeater equipped with a Gateway will do things NOTHING else in the repeater marketplace will do, today. It's cool stuff. But you do have to mess with and practice and learn it. Having the attitude that you won't BREAK anything, helps. You can't really "hurt" the repeaters, so try stuff... it's fun. Nate WY0X
