开云体育

The D-RATS General Training Syllabus used at the recent training in Farmington, NM is available on the D-RATS Yahoo Group in the Files section <D-RATS Training

All, I am trying to connect my D-RATS terminal to my Hotspot (Connected to REF 15C) for testing. I get an error from D-RATS software, stating, "Unable to Connect 10061, connection refused."

All, ? I am trying to connect my D-RATS terminal to my Hotspot (Connected to REF 15C) for testing.? I get an error from D-RATS software, stating, "Unable to Connect 10061, connection refused." ?

Problem solved. The new PC had DRATS set to transmit on the AGWPE modem (bottom left corner of DRATS) instead of the net:127.0.0.1:9000 modem. In order for the TCP encapsulation to happen we had

First packet PC is up and running without a problem. But, the second attempt isn't going so well. We verified that it can communicate with the DRATS client/repeater PC over RF using UZ7HO modem

Got it! Jeff, I read your email about 100 times and finally understood (my fault, not yours)! So, I've got three PCs running. One is the ratflector/client. The second is a DRATS client

Excellent news!!! I can't wait to give this a try, Jeff. Did you see my post of the thread on Wednesday? I'm kind of stuck, and wondered if you could help me clear my mind on this. I'm going to

Good news from the Tulsa DRATS group. We were able to run multiple clients on the TCP forwarding to the "server" to tie in packet users to the ratflector repeater. Have some issues with it

Jeff, I'm struggling to understand this. Wondered if you could help me a little more. I currently have UZ7HO running on the remote PC (with the DRATS client and let's say callsign W4DTO) and the

James, Sounds like you and I have had very similar experiences. Have you tried MULTIPLE packet clients with all pointed to port 9000? Just wanted to confirm that the proxy software is robust

Hello, I have had no success using tnc / packet direct with ratfelctor. However if you set up your PC and TNC with IP over ax25, you can run d-rats on top. I have a raspberry pi set up with a

Exactly. Do step one on the client machine and step two on the "server/ratflector". The key is you will be running both the client and the ratflector software on the "server/ratflector", as the

Will be a while before I can test this, but it sounds like excellent news! So, step one is for the remote D-RATS client that will be connecting via packet, and step two is for the ratflector side,

I think you have to start the email with: WL2K: Example: WL2K:me@... Good luck --73 de Doug (N1OBU)

Dan, Congrats on your test bed setup. I too have been playing with AGWPE and D-RATS. I am using AGWPE with a TinyTracker 4 TNC in KISS. Works great!! I have D-RATS, AGWTracker and RMS

Noticed that you cannot set a DIGI PATH on a sound card modem in the D-RATS software. I assume the function works for a TNC port? Just found it odd that it was available on the TNC port, but not the

I think I finally came up with a work-around for the bug in ratflector that keeps TNC and soundcard modems from working with it: 1) For the TNC and soundcard modem clients, set them up in D-RATS

If you watch the logs for the repeater app you will see it throw errors when it starts up if there is a TNC or AGWPE modem defined. Sent from my Samsung Captivate Glide on AT&TDan Ozment

That's correct, Jeff. I believe there is a bug in the repeater app that causes it to not work at all if you set up a TNC or AGWPE connection in it. I have only made packet work to the D-RATS app.

Dan, Have been trying to connect either a COM port TNC or a sound card modem to the ratflector and had no success with either. From what I'm gathering in your message, you've only got a D-Star