News Today

04/05/2006

The NODE broke!

First, a little history over the last two weeks.  About two weeks ago, I made a call to Kauai via echolink too find out what was going on over there with the weather.  Since we are heading there in May, I kind of wanted to know how things were...There was no one there to answer the call.  Kauai has very limited amounts of Radio repeaters and the two IRLP nodes there have been shut down.  Echolink still exists and I am planning on using it while I am over there.  Since no one was around, I waited for two days before I tried to call again.  This time, when I opened up the link, my radio hung in PTT.  NOT A GOOD THING!! Fortunately, we have timers to take care of such events and the radio timed out so the amp did not go into meltdown.  This is not the kind of problem that I want to have happen while I am gone.  What I mean by this is, the node has been operating all on its own for a long time and has not had a problem.  This was a problem that was very hard to figure out since I had not made any changes to it and it had come about without any outside manipulating.  What this means is that the problem could be very deep in the scripting and I am not good at scripting let alone debugging it.

Well, after countless days and attempts to fix it, I had to resort to higher knowledge.  This was not easy either since the node is an echoirlp node and irlp folks are not obligated to work on a hybrid node.  It took days and a few half hearted attempts from the irlp regulars for me to decide to go even higher in the knowledge base for help.  I went to VE7LTD (Dave Cameron), IRLP creator!  This is not the first time I have been in touch with Dave for help, but the other things were minor problems when I had even less knowledge on the subject.  Dave found the problem inside of an hours time (probably less since that is when I checked back for a reply).  The problem was with the APRS script and when the node runs the script and goes to get the information from the APRS server that is listed, it would lock up because the server was down.  The script had a flaw, because it could not escape what it was trying to do.  Well now, here we were!  A problem identified, but no way yet to fix it.  APRS was then disabled until a fix was found.  I decided then that I would do everything possible to find a fix.

Several more days went by and I was trying to contact the author of the script.  I could not get in touch with him.  By this time, I had started getting some local feedback regarding not being able to see if the node was active or not on APRS.  I then decided to go back out to the people on the IRLP group and the echoirlp group.  Finally, once again, Randy Hamock (KC6HUR) came to the rescue.  Because there was another node having the same issue and it was coming from a script that Randy had altered slightly from the original ZL1AMW script, he began to help fix it.  One day later, Randy had a fix for it and it was off and running again.  But mine was not...it was not hanging any longer...but it was not sending a position either!

Yes, I was getting concerned that my problem may lay deeper than the others...Well, after a few emails to Randy, he determined that I had a minor problem in my script...something as simple a character out of place.  He sent me his script and after I loaded it....the node came back to life on APRS.

I would just like to say THANKS! These people that help others out in their times of need are absolutely great people.  It is what HAMS are all about!  For those that rejected trying to help,,,well, I will be nice and not share my feelings....for now!

The node is alive and well now.  Hopefully for a long time to come!

02/01/2006

Still haven't figured out how to get you on the air more.  There are still stations calling in and not finding anyone to talk to.  I know that this is not a repeater, and maybe that's what it will take to get more amateurs involved, becoming a repeater that is!  Well anyway, there is more news than just this.  The EchoIRLP node got its new ID.  No longer will it just beacon, which really was not a kosher thing to do.  At this time, the node will ID anytime the node is used and every ten minutes that it is in use.  After it has finished transmitting for the last time, it will send one more ID out 10 minutes after the end.  At that point the node will shut-up until there is actual node activity.  Finally, the ID I have been waiting for, thanks to KC6HUR.

As for control Op's, Dave, N7TYO has offered to help monitor the node while I am gone to Hawaii in May.  I am sure that he as well as I would more than welcome some more help in this area.  Again, I can train you in no time.  If you have an internet connection. and can hear the node, you can control it.

11/01/2005

Lots of things going on now!  As you probably seen on the front page of this site, the node is going through some growth and is bringing in new contacts every day.  It is amazing at just how many more people are trying to connect up to here from other places.  We have essentially doubled our connection stats in only a month and 5 or so days since installing EchoIRLP.  OUTSTANDING!  Now the down side, many people are calling in and no one has been around to answer back???? We need to get you on the air and talking so I will try to figure that one out.

We are currently searching for some "Control Operators" since W7BUG and I will be gone for just over three weeks early next year, we will need help to keep the station up while we are gone.  If you are interested (it is very very simple), please email W7DUX .  I promise to make it very easy to learn and I will teach you everything.  You can control it via PC as well as RF (PC preferred).

On a last note today.  We are in the developmental stages of trying to put together a system here that presents both a 440 repeater and a 2m simplex station all connected together in one package with the EchoIRLP node.  This may take some time since we are working with a PC Based repeater controller (EchoStation).  This controller is primarily made for a single repeater and we are trying to come up with a way to run all three basic setups.  If this works, it is a much less expensive trip into using a repeater since most controllers cost a bit of change.  If you have any ideas, please feel free to call me on the radio.

10/18/2005

Two things today. 

1.) I am now a registered user of eQSL and will accept all IRLP and Echolink QSL's sent through this system.  If you have had a contact with me, please send the particulars and I will send you a QSL card (electronically). I will need to know your call sign, your location, the node number you called from, and the time and date in UTC of the contact.  In order to receive it, you must sign up for an eQSL account on your own...don't worry, it is free.  Here is the site to go to:  www.eqsl.cc.  If you would like a regular QSL card, please email me at w7dux@yahoo.com .  Keep in mind that my normal QSL cards are not truly set up for IRLP or Echolink and I will write some info on the back of them regarding this type of contact.  Go ahead and sign up for eQSL, you may already have cards waiting for you to do so.

2.) The new combination IRLP and Echolink system on the node has definitely brought in more activity.  This is a great thing, I only wish I had the time to answer all the calls that have come in.  I just want to say thanks to all of you that help out on the system as well as those that offer to help in the future.  This system can sort of get to the point where you must "Baby-sit" it all the time.  It is not labor intensive, just "Monitor" intensive.  In the future I would like to have a few more control operators around, so if you are interested, please contact me and we can discuss the particulars over breakfast or something.  Down the road, I am looking to install a 440 repeater on the node and I am looking for some help on the subject.  I would still want to have the 2M side connected although we may have to shift the frequency a bit.  The reason for this is that it would open up more ability for control and not necessarily require someone to have internet access capabilities.  (Let me know if you have the expertise to setup a 440 repeater system with this IRLP/Echolink System and we will talk).

09/26/2005

Today I took a giant step and created and EchoIRLP node.  What is that you ask!  Well, simply put, the node not only does IRLP but also now does Echolink.  Why is this a big step you ask!  Well, when you do this, you basically give up a certain amount of support from the IRLP people.  If something breaks, I have to fix it with the help of the EchoIRLP Group.  Enough said!

So what does all this mean to me you ask!  Well, you can now use either system from this location and you will likely hear more traffic coming in on the node.  There are changes to how to connect and there will likely be more changes in the future as I get the bugs out.  Follow this link for a current list of commands (commands).

As we go along, I will try to keep you informed of the changes.  If you find something not working, be patient, I may be working on it at the time or there may be a conflict that I have not resolved.  As of today, everything is working properly!

Most of all have fun and use the node....make some contacts!  73

06/15/2005

Well, the node has undergone some changes!  As stated below, it was updated to Fedora Core 3.  I have also investigated the changes to the sound card and for now I feel that we will stay the course with this card...I have heard some issues with the "Synth" type cards and Fedora Core 3.  But on a better note, the node now can tell you what node it was just connected to by simply keying and pressing *69 (star, 6,9) on your keypad.  So if you missed the node number of who just called in...you can now find it immediately and call them back.  Also, (for APRS people), if you go to Findu.com, you can type in IRLP3089 (use all capitals) and APRS will show you node info and location.  Thanks to ZL1AMW (Alan) for your much appreciated help with both of these programs.

On a more background issue, the node should not interfere with local traffic if it senses that there has been traffic within a set amount of time.  The node will sense the carrier and not allow the remote station to enter for a given amount of time (I think it is set for 30 seconds at this point).  Not that this has been a problem, I just didn't want it to interrupt a local QSO. (it will however, still CW ID every 30 minutes.  Yes yes, I am working on it...be patient)

06/13/2005

Node 3089 was updated to Fedora Core 3 today...with some difficulty.  At this time, the CW ID is not operational.  I will be looking into a new sound card that has Synth that plays through the node.  This way we can have the ID only perform when needed.  Other than that, I am learning a bit about linux and trying to figure things out in order to add more features to the node.  Until then, please be patient as I create much dust.

On another note, one of our control ops has left the area in pursue of his dreams.  Sean (K7TYE), is headed to the Corvallis McMinnville area to gain ride time on an ambulance for his Paramedic Certification and will likely be looking for a job soon after.  He has stated that he is trying to get back over this way...I will keep you informed.

12/31/2005

Today there was a courtesy tone installed on the Node.  If you are local and using the Node, you will here a re-key with a beep at the end of the remote transmission.  If you go to a reflector you may want to turn it off if you think the traffic will be high there.  To do this press PTT *2 and this will toggle it off (do this prior to going to the reflector connection).  When you are done, turn the tone back on by repeating the above process.

12/28/2004

Well, we went to the insomniac net tonight only to find that there was no net.  Possibly due to bad weather in the Southern California area.  That didn't stop us from creating our own fun for the night as we (Myself, K7KIT & K7TYE) made up our own trivia questions.  Well, then things digressed and we began reviewing the potential names for the Duck.  Both Sean and Les  came up with "Ruster".  Well, to understand this you first had to be present at one of the trivia nets we all attended when Les gave his call sign and then his name.  The net op that night in turn did not hear him well and called him "Russ", so to solve this problem the next time he gave his whole name "Lester".  We then began calling him "Ruster".

If this was to be the Ducks name, I think it would be fitting since Les (Ruster) has given so much to the operation of the Node.  And the pure & simple funny side to it leaves us with good memories.  So if your around and see Less (K7KIT) from time to time...be sure to say Hi Ruster!

12/22/2004

The new Mirage B34G amp arrived today and was setup.  Had a problem with the pre-amp on it in that it picks up all kinds of noise.  This resulted in having to not use the preamp for the time being. 

The node has been used almost every night now for the Insomniac Net.  The net originates out of Southern California utilizing the Wins System and connects to the IRLP via Reflector 9253.  Every night hosts a different net control operator with each bringing their own flavor to the net.  The net has also been called the "Trivia Net" since that is really what happens here.  Each night, the control ops bring 3 - 4 trivia questions to be answered by the participants.  If you are interested, please feel free to join us each night at 2300 hrs local time.  The net lasts about 45 minutes to an hour.  If you join us, please keep in mind that the Wins System has been experiencing occasional harmful interference from a problem person in the Southern California area.  Usually it is targeted towards a particular net operator and if it happens, the IRLP connection we have will be terminated by one of our control ops.

12/14/2004

Added an amplifier today so the radio was turned down to 5 watts while the amp puts out 35 watts.  This should help save the radio and place the load on the amp.  The amp is K7TYE's and is only temporary since I ordered a Mirage B34G amp that will be taking its place.  I also placed a 4" muffin fan on top of the amp to help in cooling.  All in all, I think we can safely take part in nets and activity on reflectors where there is high traffic.

12/05/2004

A new antenna was installed on the Node today.  A Diamond F23A was placed at about 24' taking over for the Diamond X200A dual band that was previously in use on the node.  The F23A will provide higher gain and allow the use of less power on the node radio.  Hopefully this will resolve the issue of the radio heating and allow us to use the radio to access reflectors and partake in IRLP Nets.  All test done today were at only 5 watts of power and showed the expected outcome...better overall coverage at a power savings.  The old antenna will go into its intended use as my main antenna for my dual band base station.  This antenna sits at about 34'!

I had one more thought today driving back from Bend and I think we might try placing an amp after the radio so we can increase the power and not have to subject the radio to higher power and heating.

12/04/2004

Had breakfast today with the Sisters Radio Club at Coyote Creek and things are going good, lots of people there today.  On subjects relating to the Node, we discussed making it a repeater...we will take this up in a net.  Wayne Jack (KK7TT) is now using the Node...this is great...the more people getting some use out of it brings happiness to my heart and reaffirms my intentions for building it in the first place.