[DSTAR_DIGITAL] Re: transceiver output spectrum
You can find images comparing my Hot Spot node adapter via Yaesu FT-8000 and RF Concepts 4-110 vs my IC-92 in the gmsk_dv_node Yahoo group here: http://tinyurl.com/y4k7rza Comments on the images indicate which is which. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, dh5ym dh...@... wrote: Dear all, i am searching for some real measured data of the output spectrum of different D-Star radio's. I am wondering how the spectrum looks like in real world. In theory it's clear i think ;) The purpose is to compare some homemade solutions with the commercial radio's in terms of the TX signal. regards Mario, DH5YM
[DSTAR_DIGITAL] Re: Random Thoughts on an Open D-STAR Architecture [Was: Home Rptr is MIA, What do I do???]
--- In dstar_digital@yahoogroups.com, John Hays j...@... wrote: This is where I think the Icom implementation added an unnecessary feature. D-STAR protocol has its own useable address space in the callsign fields of the header. In DV mode there is no reason to assign a callsign an IP address (nor in DD mode either, really). What I am thinking is we need a D-STAR protocol router and only when the D- STAR protocol needs to be tunneled through the Internet is there a need for the D-STAR routers to be able to locate one another and Secure Dynamic DNS would provide that service. Also D-STAR routers could use a variety of transports besides IPv4 to tunnel the D-STAR protocol over other networks. I whole-heartedly, absolutely, 100% agree with this. Dump the IP address junk from D-STAR. Mark (KB9KHM)
[DSTAR_DIGITAL] Re: HOTSPOT and DPRS?
You can also open a console window and type: telnet localhost 20003 and watch the slow speed data that is being sent from Hot Spot. You can do this to confirm TPC/IP connectivity and data flow. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, ae5pl p...@... wrote: D-PRS Interface lets you look at the serial stream directly (without interpretation) by selecting Direct under View in the main menu. If Direct is not selected, it only shows you what passes CRC or FCS per the D-PRS specification. If it is not connecting properly to the hot spot serial TCP port, that should show in the Error Log (under Tools in the main menu). 73, Pete AE5PL --- In dstar_digital@yahoogroups.com, Francis Miele fran@ wrote: Thanks Pete. The DPRS interface is setup correctly. I have asked him to check his radio again. Fran, W1FJM
[DSTAR_DIGITAL] Re: Has anyone tried using the node adapter in the simplex mode as a link on ...
A node adapter does not, at any point, convert a D-STAR GMSK signal to analog audio. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, ka2ugz whitej...@... wrote: an analog repeater? The purpose would be to connect a reflector to a tradional analog repeater. If you prevented analog generated audio from reaching the reflector it would be like rebroadcasting space shuttle mission over the analog repeater. Again the purpose for asking is to get some traffic on the frequency. 73 de KA2UGZ - Jay
[DSTAR_DIGITAL] Re: Purchasing a Node Adapter
Fred is Fred Van Kempen - PA4YBR. The man behind http://www.dutch-star.nl/ Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, ka2ugz whitej...@... wrote: Hi Mark - Who is doing this development of new non-Satoshi firmware? Is it you, and who is Fred? 73 de KA2UGZ - Jay New non-Satoshi firmware will be available very soon. And the Hot Spot application already works with this new firmware and drivers. Fred's new drivers also get around the Win7 (x64) issue that plagues the old LibUSB drivers.
[DSTAR_DIGITAL] Re: Purchasing a Node Adapter
As Fran mentioned, if you are in the US, the easiest place to purchase a node adapter board to set up a Hot Spot is here: http://www.enicomms.com/ If you are in Europe, then you probably want to go here instead: http://www.dutch-star.nl/ For information/questions/etc. join the gmsk_dv_node Yahoo group here: http://groups.yahoo.com/group/gmsk_dv_node/ New non-Satoshi firmware will be available very soon. And the Hot Spot application already works with this new firmware and drivers. Fred's new drivers also get around the Win7 (x64) issue that plagues the old LibUSB drivers. tooting my horn Hot Spot is the most full featured software package for D-Star access available. It can be used as a simplex node, a full duplex repeater, or an auxiliary station to provide D-Plus linking for a real Icom D-Star repeater that has no Internet access. Hot Spot has a DVR function that can be used to record and play back QSO's (and alternately export them in DV-Tool format). Hot Spot supports common D-Plus linking commands so that it can be remotely linked/unlinked from a repeater/reflector just like a G2 server. It also supports linking and access authorization lists so you can control who can link and who can even access your Hot Spot. Hot Spot can be used with DRATS as a complete non-Icom data only station. It works with DPRS Interface to Igate DPRS packets to the IS-APRS network. Hot Spot accepts up to 4 simultaneous inbound connections so other Hot Spots and DV Dongles can connect directly to your Hot Spot. Hot Spot can be configured to echo back to all simplex or repeater end users their received signal strength so everyone knows how well they are getting into the Hot Spot with EVERY transmission. Soon I'll be adding connection scheduling so you can set up Hot Spot to automatically connect to various reflectors/repeaters at different times of the day/days of the week. Never miss listing to a net because the DVR will capture it for you! /tooting my horn No Hot Spot does not support callsign routing. My personal opinion is that the current callsign routing implementation isn't very useful. I don't use it at all, and don't miss it. So pick up a node adapter, set up a Hot Spot, and spread D-STAR! Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, ka2ugz whitej...@... wrote: WOW what a response for the recent new guy post! Seems like an abundance of energy in this group. I saw a presentation and demonstration of a D-Star hot-spot using a node adapter (Ham Radio University sponsored by GSBARC) and as a result I joined this group to learn more. I am an officer in a Long Island club that operates 3 analog repeaters, two 70cm and one 2m. We have discussed turning one of them into a D-Star repeater but the significant investment is beyond the reach of our small club. I think the node adapter hot spot is well within our grasp though. With the closest D-Star repeater on the Empire State Building in NYC there is not much D-Star activity here and I think the hot-spots will create opportunity. So on to my first question: I sent an email to Satoshi (7m3...@... ) to buy an assembled node adapter which his website says is available (updated 12/23/2009). It has been about 10-days with no reply and no indication that the email was undeliverable. In the experience of this group, does it take Satoshi a long time to answer email? I realize that this is probably not his day job and he might be overloaded with requests so please help set my expectation levelÂ… how patient do I need to be? 73 de KA2UGZ - Jay
[DSTAR_DIGITAL] Re: Purchasing a Node Adapter
--- In dstar_digital@yahoogroups.com, Woodrick, Ed ewoodr...@... wrote: The hot spots aren't probably your answer because their main goal tends to be for a single user. Their main goal is however you configure them. Hot Spot works just as well in repeater mode as it does in simplex mode. You might be surprised how many Hot Spot repeaters there are in operation. In Belgium it looks like about 30 percent of their repeaters are Hot Spots. That percentage goes up considerably if you throw in all the simplex nodes with wide area coverage. Still, it's a considerable percentage. It's nice to see D-STAR home brewing in action as there seemed to be so many saying that D-STAR would be impossible to home brew when it first came out. Mark (KB9KHM)
[DSTAR_DIGITAL] Re: DV Dongle - [ADGRV]OIP
DVAR Hot Spot is not a hack of anything. It uses the same DPlus protocol as DVTool, with Robin's blessing. Hot Spot passes the callsigns and slow speed data in both directions with fidelity. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, barrymung barrym...@... wrote: Yes, it seems that way. I'm guessing that hotspot and hotpoint are just 'hacked' versions of the DV Tool somewhat. No idea if the 'data' and DV (voice) are kept together in the same stream or not, doesn't seem to be when you connect to port 20001 or wherever, just one port on the reflector/node IP etc. Will have to play a little more. No RF D-Star around my QTH, so all my working is mobile and rather dodgy trying to set YOUR/UR: to something when driving and want to do something else on the fly. (Or the wheel!) Its still great to be able to connect to reflectors and call up Dongle users via RF on the nodes wherever I am. My work has changed quite a lot recently, so I've been to a lot of extra places, thank god for mobile internet so I can look up what's within range (I hope). My milage IS different now. Where do you 'hang out'? 14C seems really busy every time I connect and can't get a word in edgwise, so I usually stay local and connect elsewhere where its possible to make contact. At least Robin's fixed the fault with the Dongle and double key-ups for now. (Thanks Robin.) Bed time here. 73. Neil. G7EBY. Came into this a bit late really (Year or so ago) so not really 'up' on all the protocols and stuff.
[DSTAR_DIGITAL] Re: CROSSPOST: Response to call for FCC action. [United States]
Being the owner of the gmsk_dv_node Yahoo group, and the author of D-Star Hot Spot, I have to say that I've not heard of anyone using D-Star Hot Spot who's been denied access to the the D-Star network (D-Plus). I've worked closely with Robin to ensure that Hot Spot meets all of the necessary requirements for D-Plus connectivity, and Hot Spot usage has his blessing. My guess is that this message from Scott is pure crap and is his sorry attempt to try and stir up some (more) trouble. Remember ... don't feed the trolls. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, John Hays j...@... wrote: Since the rptDir group is moderated, this response may not get posted, so I am crossposting this response to the message at http://tech.groups.yahoo.com/group/rtpDir/message/1991 This is an incredibly bad idea: 1) The FCC regulates on air amateur radio activities, not private Internet networks that interconnect repeaters. 2) If the FCC were to make a ruling, you might get results you didn't expect like maybe the FCC would rule that you can't interconnect using the Internet, which might include killing IRLP and Echolink. This is a new administration, we don't know their attitude towards amateur radio. 3) The D-STAR network is a cooperative effort. Robin's DPLUS is actually not even part of the D-STAR protocols (or network) but rather an application on top of the US Trust Server authentication network. I agree he has been heavy handed on his security enhancements, but you should be taking this up with him directly, as well as the US Trust Server management team, and possibly the D-STAR International Coordination Council. 4) This draft letter has several technical inaccuracies. Such as the assertion that AA4RC has installed the software. a) The system admins have to initiate the installation and operation of the software. Many do so blindly, but they do initiate it. b) Your amateur radio license does not give you rights to use the resources of another amateur. It gives you the rights to operate on amateur radio frequencies in accordance with the rules and regulations. In fact, the rules specifically allow the trustee of any repeater system to deny use to anyone they choose, or permit use by a select few. There are a few ways to deal with this situation: 1) First appeal to Robin to clear your information for re-entry through his security enhancements 2) Notify the US Trust Server team of your concerns. (trust-server-adm...@... ) 3) Appeal to the larger community with rational, well reasoned and stated discussion through discussion groups and letters to the editors of major amateur publications. 4) Work with the D-STAR ICC (http://www.d-star-icc.org to establish standards that insure access to the network for anyone willing to follow the rules and procedures. (Read the article in this newsletter http://www.dstarinfo.com/Newsletter/default.html by N5MIJ) Save communications with the FCC to regulatory matters (e.g. if you have something that you can cite the FCC regulation about and can't resolve directly) - there is no supporting regulation for this complaint. --- In rtp...@yahoogroups.com, ham44865 ham44865@ wrote: A few users that use satosit boards or other types of hardware/software have been denied D-STAR access over IP. If this still happening to anyone, you can file this complaint with the FCC. E-mail the following to the FCC, Use your name and FCC callsign at the beginning and at the end of this letter. == To: fccham@ From: Your First Name, Last Name, Your FCC callsign Dear Sir/Mam, I wish to file a complain that my access to the D-Star Amateur Radio Service has been obstructed by Robin Cutshaw: AA4RC. AA4RC Amateur Radio Operator has blocked my access to the D-Star network. AA4RC has blocked my FCC callsign, device and IP adress from access to the whole D-STAR system. I have always connected to the system in the past using proper Amateur radio identification and protocol, and have not introduced any forbidden connection or behaviour to the system. So, AA4RC is in control of the whole D-STAR network all over the world and I can not connect to any D-STAR repeater anywhere in the whole world. I find it unbelievable that one person like AA4RC can control all the D-STAR Amateur radio repeaters in the US and the rest of the world. AA4RC has installed his own program on all the D-STAR repeaters in the world and because of this, he has blocked my access to all D-STAR repeaters because he has copied my callsign to all D-STAR repeater databases around the world. He is even in control of my local ham club D-STAR repeaters. I have corrected all and any problems
880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance)
What I would LOVE to see would be to take one of the unused flag bits in the DV Header and use it to indicate of the transmission was initiated by the end user pressing their PTT, or if it is an automatic DPRS beacon transmission. Then, an enhancement to the G2 software (open gateway, etc.) could make a decision if that automatic DPRS beacon should be forwarded on to any linked D-Star servers. It would be great to be able to drive around with my 2820 beaconing out DPRS packets without having them forwarded beyond the gateway. Mark (KB9KHM --- In dstar_digital@yahoogroups.com, John Hays j...@... wrote: If the controller firmware would pass ALL TRAFFIC to the gateway the whole G port thing could go away. A smarter piece of gateway software could determine what needed relayed somewhere else and what is just local repeater traffic. I have been thinking about the whole D-STAR routing paradigm and the world would be much better if: A) Radios (RF) on D-STAR did not need to register - let the gateways just update current location into a dynamic, distributed data store. (FIlters at the gateway could manage who could and could not use a given gateway - and callsign pattern matching, e.g. regex, could filter out most bogus callsigns) B) Only register network devices such as gateways, reflectors, dongles, etc. and have things like dv dongles, autopatches, cross service links (e.g. IRLP), run through servers that present them to the D-STAR network. Redundant trust servers could maintain this registry to remove the single point of failure. This would facilitate such things as mobile D-STAR stations moving from repeater-to-repeater or port to port in real time. Enable addressing services (reflectors, dv dongle type devices, nets, etc.) directly in UR field. RPT2 could be used to route to a different repeater/port and eliminate the whole /repeater syntax. -- John On May 14, 2009, at 6:27 AM, Evans F. Mitchell KD4EFM wrote: From: Evans F. Mitchell KD4EFM [mailto:kd4e...@...] Sent: Thursday, May 14, 2009 9:11 AM To: 'dstar_digital@yahoogroups.com' Subject: RE: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance) Any idea when the JARL will allow you all to install D-Plus??? As far as the R2 goes, DPLUS: with R2 ON, this will tell the RP2C to pass your data stream to the gw. If you where on a dongle, you connect to a US gw, if we DO NOT have R2 enabled or ON, you will not hear our transmission. When you omit R2 your data stream goes from the receiver to the RP2C, and right back out, with out any information going to a connected gateway. R2 set to the local gw callsign and G, the RP2C will send that data stream to the gw software, thus traffic can be heard from the repeater. D-PRS (APRS); with R2 ON, this will send your position data to the gw, and the DPRS program will then send it out to the aprs-is server stream and show your position on an aprs viewing program, jfindU, or other like program (including dstarusers.org) With D-PRS, yes, you will get the RPT? every transmission, that is because the RP2C has not been updated to understand the even though URCALL is CQCQCQ, the data stream is still meant for the gateway. Once there is a RP2C firmware update, things can be adjusted correctly then... John Hays Amateur Radio: K7VE j...@... [Non-text portions of this message have been removed]
880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance)
Evans, I can easily change the D-Star Hot Spot code and have it talk to the G2 server as if it was an Icom repeater controller (instead of linking to DPlus). This would position Hot Spot as a replacement for the Icom repeater controller and the DV Node Adapter and a pair of analog radios would take the place of a band module. Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, Evans F. Mitchell KD4EFM kd4e...@... wrote: John, I could not agree any more then that... With the adventure of two different projects out there right now (Robin's ODP, and Scott's D_Extra) the only thing keeping things in the MUD is the controller... Other then that, we just keep moving forward to a ONE DAY UNIFIED SYSTEM, where P25, D-Star, and what ever else digital ( I have to add POCSAG or any of the DIGITAL programs like PSK-31, RTTY (yeah RTTY for SMS) will be a common tool for not just HF but D-Star too.. Heck, AOR9600 is near D-Star HF as it gets right now, one day it will be D-Star HF ICOM rigs hitting the market... oppps, there goes 300bps HF packet, now 900 bps D-Star Keyboard QSO's. So I say I agree on your comments 100%, it's just not quite time for it. I am thinking about working on a P25 project that will convert to and from D-Star I just have to wait for a couple of other people to collaborate with over the summer to see if it can be pulled off. So many people want to pull the P25 card on d-star, I figure why not? What is to hold me back from doing something like that? ( I have an idea on paper, just need to work on a hardware thing first. Look at eQSO, John) Evans F. Mitchell KD4EFM / AFA4TH FL / WQFK-894 Fla. D-Star Tech Support Group http://www.florida-dstar.info http://www.florida-dstar.info/ Polk ARES A.E.C. http://www.polkemcomm.org http://www.polkemcomm.org/ _ From: dstar_digital@yahoogroups.com [mailto:dstar_digi...@yahoogroups.com] On Behalf Of John Hays Sent: Thursday, May 14, 2009 1:04 PM To: dstar_digital@yahoogroups.com Subject: Re: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance) If the controller firmware would pass ALL TRAFFIC to the gateway the whole G port thing could go away. A smarter piece of gateway software could determine what needed relayed somewhere else and what is just local repeater traffic. I have been thinking about the whole D-STAR routing paradigm and the world would be much better if: A) Radios (RF) on D-STAR did not need to register - let the gateways just update current location into a dynamic, distributed data store. (FIlters at the gateway could manage who could and could not use a given gateway - and callsign pattern matching, e.g. regex, could filter out most bogus callsigns) B) Only register network devices such as gateways, reflectors, dongles, etc. and have things like dv dongles, autopatches, cross service links (e.g. IRLP), run through servers that present them to the D-STAR network. Redundant trust servers could maintain this registry to remove the single point of failure. This would facilitate such things as mobile D-STAR stations moving from repeater-to-repeater or port to port in real time. Enable addressing services (reflectors, dv dongle type devices, nets, etc.) directly in UR field. RPT2 could be used to route to a different repeater/port and eliminate the whole /repeater syntax. -- John On May 14, 2009, at 6:27 AM, Evans F. Mitchell KD4EFM wrote: From: Evans F. Mitchell KD4EFM [mailto:kd4e...@verizon. mailto:kd4efm1%40verizon.net net] Sent: Thursday, May 14, 2009 9:11 AM To: 'dstar_digital@ mailto:%27dstar_digital%40yahoogroups.com yahoogroups.com' Subject: RE: 880 vs 800 (was: Re: [DSTAR_DIGITAL] Signal Distance) Any idea when the JARL will allow you all to install D-Plus??? As far as the R2 goes, DPLUS: with R2 ON, this will tell the RP2C to pass your data stream to the gw. If you where on a dongle, you connect to a US gw, if we DO NOT have R2 enabled or ON, you will not hear our transmission. When you omit R2 your data stream goes from the receiver to the RP2C, and right back out, with out any information going to a connected gateway. R2 set to the local gw callsign and G, the RP2C will send that data stream to the gw software, thus traffic can be heard from the repeater. D-PRS (APRS); with R2 ON, this will send your position data to the gw, and the DPRS program will then send it out to the aprs-is server stream and show your position on an aprs viewing program, jfindU, or other like program (including dstarusers.org) With D-PRS, yes, you will get the RPT? every transmission, that is because the RP2C has not been updated to understand the even though URCALL is CQCQCQ, the data stream is still meant for the gateway. Once there is a RP2C firmware update, things can be adjusted correctly
[DSTAR_DIGITAL] Subject: D-STAR Hot Spot v2.27 released
D-STAR Hot Spot v2.27 is now available for download from the files section of the gmsk_dv_node Yahoo group. - Full duplex repeater mode using the node adapter! If you are upgrading from a previous version, you will need to uninstall the old version before installing the new one. Updated information and instructions can be found here: http://www.W9ARP.com/HotSpot/ Changes in version 2.27: - Now supports full duplex repeater mode using only the node adapter - DVR export to DVTool file. You can now export a selected group of multiple transmissions from the DVR window and export them to a single DVTool file which can be played back using the DVDongle. - Received signal quality reports. If you are using firmware version = 5.00 with a modified node adapter board, D-Star Hot Spot will report the signal quality (relative S/N ratio) of every received transmission as part of its ID message. - Improvements have been made in recovering from a transmission interruption caused by an interruption of CPU processing time. Mark (KB9KHM)
[DSTAR_DIGITAL] D-STAR Hot Spot v2.16 released
D-STAR Hot Spot v2.16 is now available for download from the files section of the gmsk_dv_node Yahoo group. If you are upgrading from a previous version, you will need to uninstall the old version before installing the new one. Updated information and instructions can be found here: http://www.W9ARP.com/HotSpot/ Changes in version 2.16: - Added HeaderArray overrun protection when receiving DV streams over RF from the node adapter (fixes overflow bug). - Coded around a bug in node adapter firmware version 4.06 that sent 7 extra bytes in response to a GET_HEADER if the end user doubled with the node adapter transmitter. - Modified the TX Delay setting in Set_Header_Packet to work around a change in the firmware. The delay should be back to 500ms with firmware v4.06 - Added a new setting to specify the RPT1 callsign that is transmitted by Hot Spot. - No longer sends an transmits and ID (over RF) if the RPT1 value for the node adapter transmitter is not set to DIRECT . - Made changes to help prevent crashing if the node adapter suddenly falls of the USB bus. - Fixed a bug that would cause Hot Spot to crash if a new stream started from the gateway before the previous RF transmission had finished. - Added code to work around DV stream TX problems when receiving a 'double routed' stream from the connected gateway/reflector.
[DSTAR_DIGITAL] Re: tri band that inlcudes 23cm?
I see you were replying to my previous message. If you were directing your comments back to me, I'm well aware of the various standards. I own an Alinco 635 mobile with it's worthless internal connector for either a digital voice board that talks to no one (who would buy an add-on for digital voice with no infrastructure behind it?) or a TNC that seems to be riddled with complaints. I wish Alinco simply had a break-out board that would let me access the the modulator/discriminator taps so I could use a DV Adapter or Node Adapter with the radio. I can't see Alinco's digital voice mode as anything but a dead end. I'd have to guess that their sales of digital and-on boards dropped to near zero with the rise of D-Star. My previous post was merely speculation about Alinco dropping their current digital voice protocol, adopting D-Star, and putting it in that new tri-band HT. What a sweet radio it would be. If only Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, Reiner reiner.w...@... wrote: --- In dstar_digital@yahoogroups.com, kb9khm kb9khm@ wrote: I did notice on Universal Radio's site that Alinco is releasing a new HT with 2m/440/1.2ghz. ... Mark (KB9KHM) There are different digital standards used in amateur radio, one is Alincos digital voice, one is APCO P25, and one is D-Star. There maybe others I don't know. But they are all different. On the english Alinco web page you can read some information from their FAQ's: http://www.alinco.com/faq.html If you like to read about P25 go to this address: http://www.apcointl.org/frequency/project25/information.html I hope more companies will develop D-Star radios, because this is my favorite digital mode. :-) 73 de Reiner, dh9fax
[DSTAR_DIGITAL] D-PRS Interface TCP Reconnect WAS: Re: W0CDS D-PRS
Pete, It seems like if I specify a TCP Port for D-PRS Interface to connect to (I'm talking TCP serial port here - as in connecting to DVTool), that D-PRS Interface will only try once to connect to the TCP port when the application is first launched. Is there anyway I can talk to you into a new version of DPRS-Interface that will retry the TCP serial port connection if the TCP server is not available, or if the connection is lost? A retry of once per minute or so would be great. I've added code to D-STAR Hot Spot to make a TCP server available that will stream out the slow speed (DPRS) data to your D-PRS Interface application. My concern arises in a situation where D-STAR Hot Spot and D-PRS Interface are launched automatically on Windows boot-up. If D-PRS Interface happens to launch before D-STAR Hot Spot, and Hot Spot's TCP server is not ready yet, that D-PRS will never make a connection. A TCP connect retry from D-PRS Interface would cure this issue. Thanks! Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, Peter Loveall p...@... wrote: --- In dstar_digital@yahoogroups.com, Jon M. Hanson jon@ wrote: Is something wrong with W0CDS' D-PRS gateway to the Internet? I thought I heard a couple of position reports come out of my radio acknowledged by W0CDS but they didn't appear to make it out to the APRS network. A simple explanation of the D-PRS IGate on the gateway: The D-PRS IGate monitors the repeater to gateway bit stream looking for the Icom low speed serial information. This information is carried in unprotected form via RF and the bit stream format is not altered going to the gateway. If Icom GPS information is seen AND it is in the proper format (see http://www.aprs-is.net/dprs.aspx) AND there are no bit errors, the D-PRS IGate will translate the received GPS information into an APRS packet and send it to APRS-IS. For the bit stream to be seen by the gateway, you must have the repeater in RPT1 and the gateway in RPT2. For normal operation, we recommend you have CQCQCQ in URCALL. For proper format to be gated to APRS-IS, review http://www.aprs- is.net/dprs.aspx and configure your radio accordingly. The gateway does not acknowledge transmissions (nor does the repeater). What the repeater (and gateway) does is tell you by different responses whether your RF header (contains both forward error correction and error detection) was received properly or not (basically, it is more detailed than that). There is no indication of bit errors in the low speed data portion of the transmission. Individual beacons (never beacon more often than every 5 minutes on a repeater and never beacon if you are active on voice) quite often will have at least one bit error which will invalidate the position report to the D-PRS IGate. If you are using an amplifier with a hand- held, you might also be chopping the RF header preventing your bit stream from making it to the gateway. Icom has their radios continuously send GPS information (GPS or GPS-A mode) when you are talking which greatly increases the chances that at least one report will get through error free. Hope this helps. 73, Pete Loveall AE5PL
[DSTAR_DIGITAL] D-PRS Interface TCP Reconnect WAS: Re: W0CDS D-PRS
Pete, I should also mention that this future version of D-STAR Hot Spot will only send slow speed (DPRS) data received from the attached RF receiver to D-PRS Interface. Slow speed data embedded in a DV stream received from a connected gateway or reflector will NOT be sent out the TCP port to D-PRS Interface. I've added this functionality because mobile D-STAR Hot Spot users who transmit DPRS data do not show up on the APRS-IS network, even when Hot Spot is connected to a repeater with a G2 gateway running D-STAR Monitor. This is because data forwarded to DPlus from a connected D-STAR Hot Spot is not passed to D-STAR Monitor. Thus D-STAR Hot Spot must have it's own means of passing DPRS data to the APRS-IS network, rather then relying on the connected gateway. Rather than build my own APRS-IS client inside of D-STAR Hot Spot, I figured your D-PRS Interface software would fit the bill perfectly. Initial testing shows that the TCP connection between D-STAR Hot Spot and D-PRS Interface works great! Mark (KB9KHM) --- In dstar_digital@yahoogroups.com, kb9khm kb9...@... wrote: Pete, It seems like if I specify a TCP Port for D-PRS Interface to connect to (I'm talking TCP serial port here - as in connecting to DVTool), that D-PRS Interface will only try once to connect to the TCP port when the application is first launched. Is there anyway I can talk to you into a new version of DPRS-Interface that will retry the TCP serial port connection if the TCP server is not available, or if the connection is lost? A retry of once per minute or so would be great. I've added code to D-STAR Hot Spot to make a TCP server available that will stream out the slow speed (DPRS) data to your D-PRS Interface application. My concern arises in a situation where D-STAR Hot Spot and D-PRS Interface are launched automatically on Windows boot-up. If D-PRS Interface happens to launch before D-STAR Hot Spot, and Hot Spot's TCP server is not ready yet, that D-PRS will never make a connection. A TCP connect retry from D-PRS Interface would cure this issue. Thanks! Mark (KB9KHM)
[DSTAR_DIGITAL] D-STAR GMSK Node Adapter - New Yahoo Group
I've just started a new Yahoo group for discussion of the construction/use/interfacing of Satoshi's GMSK Node Adapter. All interested parties are encouraged to join: http://groups.yahoo.com/group/gmsk_dv_node/ Mark (KB9KHM)
[dstar_digital] Re: D-Star scramble code
Satoshi, I've been trying to figure out for some time how to descramble the slow speed data in the DV stream sent between DPlus and the DVDongle. The information you provided in this message is the key! What I don't understand is why this scramble table is different than the one on your website here: http://d-star.dyndns.org/program/scrambletable.c Could you help me to understand why and when one table is used vs. the other? Thanks! Mark (KB9KHM)
