|
Re: G3 and QNet?
I think it was Adrian (VK4TUX) who came up with the overlay for ircddbgateway and G3.? You might ask him. Personally, I think that the G3Trust Admins should come up with a method to port users into and drop the local registrations.? It's really probably just pretty straightforward SQL to bring the login information over to regist, and update the registered gateway in the master tables. On Mon, Jun 15, 2020 at 1:32 PM Jeff WA3PNY via <bauerjv=[email protected]> wrote:
--
John D. Hays Kingston, WA K7VE ? |
|
Re: G3 and QNet?
¿ªÔÆÌåÓýTerry,I¡¯ll look - I know I just read something about that. Jeff Jeffrey V. Bauer 6381 Mulberry Ln. Macungie, PA 18062 WA3PNY CCS-7 3142263 NXDN 504 Wires-X 18394/28394 On Jun 15, 2020, at 4:13 PM, Terry M. Stader <ka8scp@...> wrote:
|
|
G3 and QNet?
Any chance that QNet could be overlayed with an existing Icom G3 installation. Some of our gateways have hundreds of registered USTRUST users we do NOT want to orphan! I have a Installation document that lets us add a DL5DI OpenDV with G3 that let¡¯s us keep the registration piece, turn off dplus. Sure the gateway now looks like a hotspot, but users like the simpler command set. |
|
Re: new release
John, A quick note to say thank you for the assistance you provided to me as I was getting the QnetGateway software talking to my id-51. It¡¯s working great now and I also love the new version Tom released today. Maybe we¡¯ll be able to chat on DSTAR one of these days. 73 Dale - K0HYD On June 14, 2020 at 7:10:29 PM, John F Davis (wa8yxm@...) wrote:
> Love it Those new dashboard items are great Even better than the competition. > > "Nothing adds excitement like something that is none of your business" Note I am not a > doctor, I don't even play one on television John F Davis > > On Sunday, June 14, 2020, 01:36:01 PM EDT, Tom Early wrote: > > There are a couple of new features: > > If you never do any routing (you only do linking), you can disable IRCDDB by clearing the > ha parameter in the IRCDDB Menu of ./qnconfig. This normally defaults to "rr.openquad.net", > so you have to set it to an empty string by entering "ha" followed by a . Also make > sure the hb parameter has its default value. This will shut off the traffic between your > gateway and the QuadNet Servers and so will be especially useful to users that have a low-quality, > low-speed connection to the internet. Because you're not connected to the QuadNet Servers, > you won't see your transmission on the www.openquad.net Last Heard page, but you will > still see your activity on any reflector dashboard, including XLX307, XRF757 and XRF735. > > Two new columns have been added to the Last Heard dashboard: the sender's 20-character > text message, and, if the sender has enabled the GPS in his radio, his current 6-character > Maidenhead grid square, linked to google maps. To make these new columns work, qngateway > now reads the slow data that is sent in the AMBE voice packets. This slow data is not FEC > encoded, so it's is not that reliable, you may occasional see some unusual characters > in the text message, or you may see a message in the qngateway log that it can't figure out > how to parse the GPS data. > > There is also a big internal change. Inter-process communication now uses bidirectional > Unix sockets. QnetGateway has been using one-way Unix sockets as a way to emulate the > previous UDP communications over the loopback device (127.0.0.1), but this new protocol > is even more efficient than the one-way Unix sockets. > > Finally, there is also a new capability in this release that can't be used yet because > there is no infrastructure to support it. We're working on that and when that infrastructure > becomes available, I'll make an announcement here. > > > > -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: new release
Tom, The new version of QnetGateway is working great here. Love the additions to the Dashboard too. I wanted to send a quick not to say thank you for you help in getting my system set up. The extra space in front of the callsign was the last remaining major obstacle. I had a few tweaks to make with the way the RT Systems programming software works but once I got to the final setup everything has been working tremendously. Its going to be great to be able to have that DVAP available anytime I need it. And I there is plenty of horsepower left in the Raspberry Pi 3B if I ever want to do anything else with it concurrently. Thanks again! 73 Dale - K0HYD On June 14, 2020 at 12:35:58 PM, Tom Early (n7tae@...) wrote:
> There are a couple of new features: > > If you never do any routing (you only do linking), you can disable IRCDDB by clearing the > *ha* parameter in the IRCDDB Menu of ./qnconfig. This normally defaults to "rr.openquad.net", > so you have to set it to an empty string by entering "ha" followed by a . Also make > sure the *hb* parameter has its default value. This will shut off the traffic between > your gateway and the QuadNet Servers and so will be especially useful to users that have > a low-quality, low-speed connection to the internet. Because you're not connected > to the QuadNet Servers, you won't see your transmission on the www.openquad.net Last > Heard page, but you will still see your activity on any reflector dashboard, including > XLX307, XRF757 and XRF735. > > Two new columns have been added to the Last Heard dashboard: the sender's 20-character > text message, and, if the sender has enabled the GPS in his radio, his current 6-character > Maidenhead grid square, linked to google maps. To make these new columns work, qngateway > now reads the slow data that is sent in the AMBE voice packets. This slow data is not FEC > ( https://en.wikipedia.org/wiki/Forward_error_correction ) encoded, so it's is > not that reliable, you may occasional see some unusual characters in the text message, > or you may see a message in the qngateway log that it can't figure out how to parse the GPS > data. > > There is also a big internal change. Inter-process communication now uses bidirectional > Unix sockets. QnetGateway has been using one-way Unix sockets as a way to emulate the > previous UDP communications over the loopback device (127.0.0.1), but this new protocol > is even more efficient than the one-way Unix sockets. > > Finally, there is also a new capability in this release that can't be used yet because > there is no infrastructure to support it. We're working on that and when that infrastructure > becomes available, I'll make an announcement here. > > > > -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
new release
There are a couple of new features:
If you never do any routing (you only do linking), you can disable IRCDDB by clearing the ha parameter in the IRCDDB Menu of ./qnconfig. This normally defaults to "rr.openquad.net", so you have to set it to an empty string by entering "ha" followed by a <return>. Also make sure the hb parameter has its default value. This will shut off the traffic between your gateway and the QuadNet Servers and so will be especially useful to users that have a low-quality, low-speed connection to the internet. Because you're not connected to the QuadNet Servers, you won't see your transmission on the www.openquad.net Last Heard page, but you will still see your activity on any reflector dashboard, including XLX307, XRF757 and XRF735. Two new columns have been added to the Last Heard dashboard: the sender's 20-character text message, and, if the sender has enabled the GPS in his radio, his current 6-character Maidenhead grid square, linked to google maps. To make these new columns work, qngateway now reads the slow data that is sent in the AMBE voice packets. This slow data is not encoded, so it's is not that reliable, you may occasional see some unusual characters in the text message, or you may see a message in the qngateway log that it can't figure out how to parse the GPS data. There is also a big internal change. Inter-process communication now uses bidirectional Unix sockets. QnetGateway has been using one-way Unix sockets as a way to emulate the previous UDP communications over the loopback device (127.0.0.1), but this new protocol is even more efficient than the one-way Unix sockets. Finally, there is also a new capability in this release that can't be used yet because there is no infrastructure to support it. We're working on that and when that infrastructure becomes available, I'll make an announcement here. |
|
Re: Close to Success... Need id-51 help I think
Thanks Tom!
toggle quoted message
Show quoted text
I¡¯ll check it out soon! 73 On June 11, 2020 at 1:18:36 PM, John F Davis (wa8yxm@...) wrote:
-- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: Close to Success... Need id-51 help I think
Correct matters not if you are using Pi-Star or Qnetgateway to the radio. You program the same only the open spot is different.. and even with the open spot if you program the radio the same. It works.. It is just "over kill". But qntetgateway wants Rpt-1 and Rpt-2 same as Pi-Star does.. from a "Radio side" viewpoint they work the same (Some serious differences from other viewpoints but the radio is set up the same way) "Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis On Thursday, June 11, 2020, 07:31:02 AM EDT, Dale L Puckett <dale.puckett@...> wrote: Thanks John! Unfortunately, I am using QnetGateway as a HotSpot. My ID-51 does not have terminal or access point mode. It is older model. 73? On June 11, 2020 at 5:58:54 AM, John F Davis (wa8yxm@...) wrote:
Dale are you useig Qnetgateway as a HOTSPOT or are you usingITAP (Icom Terminal, Access Point) I use ITAP with my ID-51A+2There is no "Memory entry" for the Terminal mode sine there is noradio For use with other than the Open Spot hot spot I have MY CALL onthe ID-51 set to.. Well MY CALL Rpt1 is My Call and a module number (The Terminal is Module T forTerminal but that's not in the radio. only in Qnet) Rpt1 is thesame as the Hot-spot's D-Star config IE WA8YXM B And RPT2 is always "G" WA8YXM G (NOT sure about the space RT willdeal with that)... RT may force the hotspot into SKIP mode if it'sa simplex hotspot. Since I program in DR mode the UR field is usually populated viaradio menu as CQCQCQ (The display says USE REFLECTOR by the wayMore on that in a line or 3 IF I want to use DSTAR1 or 2 It's in YOUR CALL memories (Also theTerminate command DSTAR1 T and DSTAR2 T) and I just selectthem. What is the difference between "Local CQ" and Use Reflector? RPT2is not sent when using Local CQ so it will not go out over thegateway Only on USE REFLELCTOR or GATEWAY CQ is the RPT2Sent. This is the importance of RPT2 with a other than open spot hot spot(Open spot assumes RPT2) This is not the method for the other (Regular) memories "Nothing adds excitement like something that is none of yourbusiness" Note I am not a doctor, I don't even play one ontelevision John F Davis On Thursday, June 11, 2020, 02:23:51 AM EDT, Dale L Puckett<dale.puckett@...> wrote: Thank you to Tom, Colby and John for you assistance. I'm still fighting these issue trying to get my ID-51 running withthe Qnet Gateway. My RT Systems programming software won't save an entry with out aCallsign in the repeater 1 position... and when I try to transmitafter entering a callsign there I get this in the gatewaylog: Jun 11 00:43:52 raspberrypi-qnet qngateway[416]: MYCALL [K0HYD? ] failed IRC expression validation I was able to link to Reflector 30C using the Send UR Call field inthe QnetGateway Dashboard. I can also unlink there. After linkingto 30c this way I was able to listen to QSO's. But when I try totransmit using the Use repeater entry with CQCQCQ I get the messageabove. Here are a few lines from the link log after linking thisway: Jun 11 00:46:31 raspberrypi-qnet qnlink[429]: Connected to callREF030 Jun 11 00:46:32 raspberrypi-qnet qnlink[429]: Login OK to callREF030?? mod C Jun 11 00:46:33 raspberrypi-qnet qnlink[429]: sendingFile:[/usr/local/etc/linked.dat], mod:[B], RADIO_ID=[LINKED REF030C???? ] It appears in the gateway log that the subscribe to DSTAR2 alsoworks from the Send UR Field. But if I try to Subscribe or Linkfrom the radio I get the failed message above. Here is my entry inthe RT Systems Programmer: I also used K0HYD? B in that field following the directions ofa YouTube video from K9WLW. I get the same error with both entries.Here's the My Callsign entry form with the UR Callsigns that gointo the "To:" field: I had to enter the data for the MYDVAP repeater using the radio'ssoftware as RT Systems Software woudn't save the entries. I'm hoping there are some ID-51 users out there using QnetGatewaythat can help. Thanks again for all the help so far. 73 -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: Close to Success... Need id-51 help I think
It looks like there's a space before your MyCall callsign (it's easier to see in a fixed width font):
Jun 11 00:43:52 raspberrypi-qnet qngateway[416]: MYCALL [ K0HYD? ] failed IRC expression validation ???????????????????????????????????????????????????????? ^ That's why it's failing validation. |
|
Re: Close to Success... Need id-51 help I think
Thanks John! Unfortunately, I am using QnetGateway as a HotSpot. My ID-51 does not have terminal or access point mode. It is older model.
toggle quoted message
Show quoted text
73? On June 11, 2020 at 5:58:54 AM, John F Davis (wa8yxm@...) wrote:
-- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: Close to Success... Need id-51 help I think
Dale are you useig Qnetgateway as a HOTSPOT or are you using ITAP (Icom Terminal, Access Point) I use ITAP with my ID-51A+2 There is no "Memory entry" for the Terminal mode sine there is no radio For use with other than the Open Spot hot spot I have MY CALL on the ID-51 set to.. Well MY CALL Rpt1 is My Call and a module number (The Terminal is Module T for Terminal but that's not in the radio. only in Qnet) Rpt1 is the same as the Hot-spot's D-Star config IE WA8YXM B And RPT2 is always "G" WA8YXM G (NOT sure about the space RT will deal with that)... RT may force the hotspot into SKIP mode if it's a simplex hotspot. Since I program in DR mode the UR field is usually populated via radio menu as CQCQCQ (The display says USE REFLECTOR by the way More on that in a line or 3 IF I want to use DSTAR1 or 2 It's in YOUR CALL memories (Also the Terminate command DSTAR1 T and DSTAR2 T) and I just select them. What is the difference between "Local CQ" and Use Reflector? RPT2 is not sent when using Local CQ so it will not go out over the gateway Only on USE REFLELCTOR or GATEWAY CQ is the RPT2 Sent. This is the importance of RPT2 with a other than open spot hot spot (Open spot assumes RPT2) This is not the method for the other (Regular) memories "Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis On Thursday, June 11, 2020, 02:23:51 AM EDT, Dale L Puckett <dale.puckett@...> wrote: Thank you to Tom, Colby and John for you assistance. I'm still fighting these issue trying to get my ID-51 running with the Qnet Gateway. My RT Systems programming software won't save an entry with out a Callsign in the repeater 1 position... and when I try to transmit after entering a callsign there I get this in the gateway log: Jun 11 00:43:52 raspberrypi-qnet qngateway[416]: MYCALL [ K0HYD? ] failed IRC expression validation I was able to link to Reflector 30C using the Send UR Call field in the QnetGateway Dashboard. I can also unlink there. After linking to 30c this way I was able to listen to QSO's. But when I try to transmit using the Use repeater entry with CQCQCQ I get the message above. Here are a few lines from the link log after linking this way: Jun 11 00:46:31 raspberrypi-qnet qnlink[429]: Connected to call REF030 Jun 11 00:46:32 raspberrypi-qnet qnlink[429]: Login OK to call REF030?? mod C Jun 11 00:46:33 raspberrypi-qnet qnlink[429]: sending File:[/usr/local/etc/linked.dat], mod:[B], RADIO_ID=[LINKED REF030 C???? ] It appears in the gateway log that the subscribe to DSTAR2 also works from the Send UR Field. But if I try to Subscribe or Link from the radio I get the failed message above. Here is my entry in the RT Systems Programmer: I also used K0HYD? B in that field following the directions of a YouTube video from K9WLW. I get the same error with both entries. Here's the My Callsign entry form with the UR Callsigns that go into the "To:" field: I had to enter the data for the MYDVAP repeater using the radio's software as RT Systems Software woudn't save the entries. I'm hoping there are some ID-51 users out there using QnetGateway that can help. Thanks again for all the help so far. 73 -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: Close to Success... Need id-51 help I think
Thank you to Tom, Colby and John for you assistance.
I'm still fighting these issue trying to get my ID-51 running with the Qnet Gateway. My RT Systems programming software won't save an entry with out a Callsign in the repeater 1 position... and when I try to transmit after entering a callsign there I get this in the gateway log: Jun 11 00:43:52 raspberrypi-qnet qngateway[416]: MYCALL [ K0HYD? ] failed IRC expression validation I was able to link to Reflector 30C using the Send UR Call field in the QnetGateway Dashboard. I can also unlink there. After linking to 30c this way I was able to listen to QSO's. But when I try to transmit using the Use repeater entry with CQCQCQ I get the message above. Here are a few lines from the link log after linking this way: Jun 11 00:46:31 raspberrypi-qnet qnlink[429]: Connected to call REF030 Jun 11 00:46:32 raspberrypi-qnet qnlink[429]: Login OK to call REF030?? mod C Jun 11 00:46:33 raspberrypi-qnet qnlink[429]: sending File:[/usr/local/etc/linked.dat], mod:[B], RADIO_ID=[LINKED REF030 C???? ] It appears in the gateway log that the subscribe to DSTAR2 also works from the Send UR Field. But if I try to Subscribe or Link from the radio I get the failed message above. Here is my entry in the RT Systems Programmer: I also used K0HYD? B in that field following the directions of a YouTube video from K9WLW. I get the same error with both entries. Here's the My Callsign entry form with the UR Callsigns that go into the "To:" field: I had to enter the data for the MYDVAP repeater using the radio's software as RT Systems Software woudn't save the entries. I'm hoping there are some ID-51 users out there using QnetGateway that can help. Thanks again for all the help so far. 73 -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
|
Re: I¡¯m Nooby! Close to Success but not playing horse shoes
Hi Dale,
Nearly everyone that first starts using an Icom radio with a hot-spot makes that error. Never use simplex, always use duplex (+ or -, it doesn't matter) with zero offset. When you set an Icom radio to simplex, it transmits "DIRECT? " in the RPT1 and RPT2 parameters of the header, no matter what might be indicated elsewhere on you radio, and when that happens, your hot-spot won't send your voice stream anywhere. I vaguely remember discussion in other forums that the 70cm DVAP is a bit more temperamental than the 2M DVAP, but I don't know if that is the source of you problem. If echo is working, then there is probably nothing wrong with the DVAP and I don't have a lot of good advice for you. If you are linking, make sure you are showing up as linked on your target's dashboard. For example, link to XRF735A. That's a much less crowded reflector channel that is also connected to the Quadnet Array, the you can look on to see if your hot-spot module is shown on the right side of the "Last Heard" page. Then when you transmit, the Last Heard page should show a new row for you at the top of the list. If that's working, just keep putting out a "Radio check" call. Somebody will eventually respond. |
|
Re: I¡¯m Nooby! Close to Success but not playing horse shoes
John,
Thanks for the tips and the step by step. I look forward to trying them out in great detail tomorrow (actually, later today (Monday)). If you have any additional ideas please send. See my reply to Tom regarding partial success Sunday. Thanks again! 73 -- Dale L Puckett K0HYD Goddard, KS 67052 Member Society of Professional Journalists |
John Hays - K7VE / WRJT-215
Jeff WA3PNY
Tom Early
Terry M. Stader
Dale L Puckett