any have info for controler to yaesu rotator
over usb need Economy unit
"Are you still wasting your time with spam?...
There is a solution!"
Protected by GIANT Company's Spam Inspector
The most powerful anti-spam software available.
Much of the debate on the board here arises from our common desire to
see the launching of satellites with a larger footprint.
A fine analysis of one approach to this is the video and ppt of David,
G0MRF, discussing his ideas for a bird that reaches the financial
sweet spot, between LEO and HEO, a 'middle earth orbit, or MEO.
He points out that a bird at 7000 km altitude is beyond the inner
radiation belt and yet has a pass duration of 90 minutes and a
footprint diameter of over 13,000 km.
Here's the great thing, though: it is possible to do an orbital
transfer from LEO to MEO.
David points out some difficulties, though: VLSI electronics
components are not as tolerant of radiation than others, and the
attitude control of the second burn might be tricky.
Another approach (also gleaned from David's rich harvest), which would
be even more simple, and perhaps within the realm of a 3x cubesat,
would be to raise a typical cubesat from its 650km altitude to the
1400km or so that has made AO-7 so popular.
An elliptical orbit, requiring only one 'burn' might even be seen as
an advantage. As David says, it would allow for the bird eventually to
be deorbited, but it would also mean that periodically the bird could
be used with very simple antennas for local communications, and on
other occasions would require a better groundstation affording a wider
footprint.Using DH2VA's propulsion spreasheet, I see that delta_v for
one half of a Hohmann Transfer Orbit from 650 to 1500 is 212 m/sec
ish. Since my understanding of the HTO is that it comprises two burns,
one creating an ellipse, the second turning that ellipse into a
circle, I've assumed that that number is about right for an elliptical
orbit with the final altitude.
Using David's http://g0mrf.com/MEOSAT.htm, I gather that the Isp of a
cold-gas thruster is about 60 sec, which should be enough to get the
necessary delta_v above.
And then there's the transponder. With William PE1RAH's transponder
board in hand, and the work about to be done on FUNCUBE (not to
mention Delfi C3 and NE3T), we should have a very good idea of what
can be achieved with linear transponders in small LEO vessels. With
one or two of the cubes dedicated to thrust, we'd have lots of solar
panel area. What about a software transponder vs. hardware transponder
shootout with respect to volume and power requirements? Could a
software transponder include the modulation/demod of a suitable
digital mode, allowing less elaborate stations to work the bird at
Anyway, that's the sort of fun one can have with the materials that
David has provided.
>From a promotional standpoint, a project that aims to provide the
functionality of AO-7 could highlight the remarkable success of that
bird and at the same time point out the new opportunities and
challenges in space.
my unit is not really a new unit that does not run, it is a homebrewed unit on a what we call "1000 fori" board (a board with holes that you have to wire).
Today I changed Xtal with a 4.433.... and tried the in circuit programming (picprog procedure).
Finally, when I understood how the reset button must be used, I succeeded in program the pic.
Rs232 communication seems to answer something to the command C+ENTER, but what I receive are characters without sense.
At this point I think the only thing wrong is the not exact frequency of my XTAL.
No LCD yet.
I add also Howard to email, in case he would be so kindly to comment even on a homebrewed LVB board.
Da: Allen Fugelseth <allen(a)cruzio.com>
A: Stefano Simonetti <iw1rdz(a)yahoo.it>
Inviato: Lunedì 24 agosto 2009, 1:37:19
Oggetto: RE: [amsat-bb] lvb tracker circuit -- xtal?
I don't know. I had a problem with mine not working after I upgraded it. I had an earlier revision and I wanted to upgrade it to the latest and greatest. I sent the PIC and the revised hex file from G6LVB on his web page. to a friend. My friend has the capability to program PICs. He reprogrammed it, but the circuit wouldn't work. It wouldn't oscillate. So I wrote to G6LVB describing my problem and he sent back what I sent to you. In my case I had a working unit, but I broke it with the new upgraded version hex code. G6LVB sent me the additional code as I sent to you. My friend added the code and the PIC worked. I think the main problem was that the oscillator input to the PIC wasn't set. Apparently it must be done in the first four bits sent to the PIC. This gets the PIC clock input receiving the clocking signal and the PIC runs. The PIC can be configured to use an xtal, RC, and one or two other clock inputs. With the xtal the PIC can be configured to
provide an oscillator with the 4 MHZ xtal.
I could ask my friend what FPW=on is. I am not any kind of an expert here. I have learned all of this by talking with smart people. I had to go to G6LVB. Don't be afraid to email him and inquire. He seems to be a friendly guy and willing to help. I take it that your unit is new and hasn't worked yet.
My friend is Harold Hallikainen, WA6FDN. He is at Hallikainen.org. He is another nice guy. He is one of my resources for knowledge of these things.
Harold programmed my PIC externally. Howard expected these to be programmed with his software, but I don't remember why I originally didn't program it that way. Maybe I couldn't get it to work for me. Harold priginally programmed my PIC. I believe we also had the configure problem then also. I remember trying diffrent xtals and maybe capacitors. The prblem turned out to be these first four configuration bits. If you take a look at the data sheet for the PIC I think you will find something about these config bits.
I/m sorry that I could not have been more help here.
>From: Stefano Simonetti [mailto:[email protected]]
>Sent: Sunday, August 23, 2009 1:54 PM
>To: Allen Fugelseth
>Subject: Re: [amsat-bb] lvb tracker circuit -- xtal?
>thanks Allen, I tried now with the configuration you wrote.
>In IC-PROG I've set:
>Write enable: WRT OFF
>PWRT (Power up timer):enable (this you call PUT)
>Boden:disable (this is BOD)
>CPD (code protection data):disable (this is data EE prot)
>CP (code protection): disable
>BDM (background debugger mode): disable (this is BDG)
>But what is FPW=on ? I could not find in IC-Prog, even if at the end, with this configuration, IC-prog gave the exact config word: 3F31.
>Now, the cases are 2:
>1) there is a big mistake in my circuit, apart the xtal, that I cannot see...
>2) FPW that I did not recognize in Ic-prog, makes the difference, even if the configuration word is exact (strange I think).
>What do you think?
Da: Allen Fugelseth <allen(a)cruzio.com>
>A: Stefano Simonetti <iw1rdz(a)yahoo.it>
>Inviato: Domenica 23 agosto 2009, 0:48:09
>Oggetto: RE: [amsat-bb] lvb tracker circuit -- xtal?
>I had this problem. The problem was at the begining of the program in the
>first instruction, the program needs to tell the PIC to use a xtal osc as a
>clock sourece. The PIC will use maybe four kinds of time bases. RC. xtal,
>etc. A ham friend was programing the PCI externally for me and I had to go
>to Howard to get a solution. The following is what he told me. After my
>friend WA6FDN added some code, the PIC worked fine.
>Normally, you don't program it with a PIC programmer, it is programmed in
>situ using the picprog.exe program on my website
>http://www.g6lvb.com/Articles/LVBTracker/PicProg.exe and run from the
>command line of a Windows PC using a real (not USB emulated) serial port.
>This sets the correct configuration bits: way back in 2001?? When I
>originally did the tracker, there was no Hex file example provided by
>Microchip that included the config bits, so I hard wired them in the
>If you really do want to program the PIC outside of the tracker, then the
>correct bits to set are:
> // Osc=XT, WDT off, PUT on, BOD off, LVP off, FPW on, DBG off, data
>EE prot off, CodeProt off
>[stolen form the picprog.c source code!]
>I hope this helps you.
>From: amsat-bb-bounces(a)amsat.org [mailto:[email protected]]On
>Behalf Of Stefano Simonetti
>Sent: Saturday, August 22, 2009 2:45 PM
>Subject: [amsat-bb] lvb tracker circuit -- xtal?
>Hi, I have problems in making the LVB tracker circuit run.
>I have built the LVB tracker ver. PCB v1.2, Firmware v0.7, Programmer v0.2,
>Documentation v1.9, 7 Dec 2004, by G6LVB.
>The firmware was flashed successfully with IC-PROG v 1.06B, a
>homebrewed interface for LPT, and an old PC with LPT1 running win98.
>The LVB circuit requires a 4 MHz XTAL for the PIC 16F876A.
>I tried with a 10MHz, and a 3,5795MHz as I haven't a 4MHz. No success. No
>LCD, no serial communication at all.
>Does anybody know if the problem could be in having installed a
>different xtal (i.e.: does the firmware takes care about the frequency of
>Regards, Stefano Simonetti (IW1RDZ) - Italy.
>Sent via AMSAT-BB(a)amsat.org. Opinions expressed are those of the author.
>Not an AMSAT-NA member? Join now to support the amateur satellite program!
>Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
To work in uplink on the L band without a dedicated radio able to transmit at 1269MHz an upconverter is needed, probably with if input is in 70cm.
Someone can suggest me how to use or build?
I'm analyzing this way to save money instead of the station upgrade with a new radio.
Thank you in advance.
I'm selling my Kenwood TS-790A with 1.2ghz module, voice module, matching SP-31 external speaker, and (NIB) IF-232 computer module.
I'm basically selling most of my gear due to failing health.
Great full duplex satellite rig!
I have the original box for the radio but I'm not sure if I have the speaker box.
I do have the manual but it's a bit dog eared from use.
Sorry, but I will not seperate the package.
Cosmetically, I would rate the radio an 8+ on a scale of 10 only because of a very small scratch on the far right side of the display. If you didn't know it was there you wouldn't know it. It's really not worth mentioning but I try to decribe everything the best I can.
Also the plastic carrying handle on the side has been romoved by a previous owner.
The screws are still there but the handle has been removed.
Electrically, the radio is a 10. NO problems whatsoever. It meets or exceeds
all manufacturers ratings.
Will sell all for $1300.00 plus shipping.
Thanks for looking,
I was searching Google for the EDC-24 Alinco charger, and your message below came up. So happens, my DJ-580T EDC-24 charger has failed, and I can't find one anywhere. All I need is the trickle charger, and new chargers are > $50. If it still works, I will pay postage plus $10 for your trouble. Do you still have it? Thanks, Earl Deason K4YTK Huntsville, Alabama
p.s.- my message to Leroy Stenzel has bounced, so trying to reach him thru AMSAT contact. thanks
Leroy Stenzel lstenzel at bellsouth.net
Tue Jun 16 08:52:09 PDT 2009
• Previous message: [amsat-bb] Re: CP6 Decoding
• Next message: [amsat-bb] Garmin GPS12 data and power cable
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
My Alinco DJ-580 met with a terrible accident and is no longer with us.
Seriously, the radio was destroyed in a freak mishap. I have the following
accessories that I will send to you free if you can use them:
Alinco EDC-43 12-volt power cable assembly
Alinco EDC-24 battery charger for ni-cad batteries
Alinco floor plate (battery cover) for use when operating the radio without
EarTalk remote microphone and earpiece with PTT for the DJ-580
I will send to the first request I receive - respond direct to me - not thru
BB. I'll let you know when they are gone.
I was just monitoring a signal at 435.795 MHz +/- doppler, that I can't identify. It seems to be some sort of modulated carrier. Does anyone know which satellite this might be? It lasted from about 18:45 UTC until 18:56 UTC.
The worldwide amateur radio community must interface with one unified voice to
the various space agencies that form the ISS partnership. The ARISS
organization, whatever its flaws may be, was created by the efforts of a lot
of hard working hams in many countries to provide that interface. Without it
ham radio would have no access to the manned space program, and as a child of
the 1960's who grew up with the Mercury, Gemini and Apollo missions, I am
thrilled that we hams have such access. I could easily imagine a world where
this was not allowed. The fact that we are able to launch anything to the ISS,
given the astronomical value of every kilogram of payload mass on the Progress
or the Shuttle, and every minute of astronaut and cosmonaut time on orbit, is
The recent complaints on the BB remind me of the hams who bash the ARRL
without understanding that without the ARRL, amateur radio would have been
abolished long ago by the powers that be. We hams need to understand that
whatever disagreements exist between us are not nearly as serious as the
external threats to our amateur radio avocation. Whatever your beef is, please
work within the organization to make it better, and not tear it down in public
view. Writing “open letters” addressed to the world’s space agencies is
not helpful to this effort or to your fellow hams.
Moving on another amsat-bb thread, AO-40 was designed and built to take
advantage of what turned out to be a once in a lifetime opportunity to launch
a very large amateur payload into geosynchronous transfer orbit. Had we chosen
not to build it, I can imagine lots of people complaining on amsat-bb about
how Amsat management had dropped the ball and squandered an amazing launch
The presence of exotic transponders on AO-40 is not what caused its failure.
The 24 GHz payload was contributed by an Amsat member organization and was
built because they believed strongly enough in its value that they committed
their effort and their funds to get it built. There were transponders on AO-40
to serve every interest, from VHF to UHF to S-band to millimeter wave. Hams
MUST push their technical limits and explore new frontiers, it is one of the
reasons amateur radio still exists. Critics cried about the "complexity" of
the S-band downlink and then some clever hams took some cheap off the shelf TV
down converters, made some slight mods to retune the input frequency, and got
a lot of hams active with 2.4 GHz receive capability for very little money.
I agree with the letter in this month's QST (September issue, page 24),
suggesting that those who complain that the amateur radio has gotten "too
technical" might better enjoy reading People Magazine instead.
Dan Schultz N8FGV