Folks
A few weeks ago my attention was drawn to a compatibility problem with Nova and the LVB Tracker 1. I believe that I have found the fault, but it is not clear why it has taken so long for this problem to occur, especially as Nova has been my tracking program of choce for many years! It may only affect more recent versione of Nova.
I have adjusted the LVB Tecker's Baud Rate Generator slightly to be much closer to 9600bps. I must have made an error in my calculations all those years ago, so it was only operating at 9259bps. I have adjusted the BRG by one to make 9616bps and things seem to be much better now. Technically, we were only 3.5% out anyway which normally would be OK (ISTR that 5% timing error is the limit).
Anyway, new 0.9 binaries and source here:
http://www.g6lvb.com/Articles/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTrack.c
73, Howard G6LVB
Thank you Howard...
Suggestion for the AMSAT LVB Tracker Team; perhaps on future versions of the assembled kit you might provide a MAX232 chip as a spare part on the USB models. The USB daughter board needs to be removed and the MAX232 inserted for reprogramming the PIC as all documentation suggests USB programming is not reliable.
If anyone has successfully reprogrammed though the USB, please let me know and I'll try it.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: May 26, 2008 5:39 AM To: [email protected] Subject: [amsat-bb] LVB Tracker 1 Nova fix
Folks
A few weeks ago my attention was drawn to a compatibility problem with Nova and the LVB Tracker 1. I believe that I have found the fault, but it is not clear why it has taken so long for this problem to occur, especially as Nova has been my tracking program of choce for many years! It may only affect more recent versione of Nova.
I have adjusted the LVB Tecker's Baud Rate Generator slightly to be much closer to 9600bps. I must have made an error in my calculations all those years ago, so it was only operating at 9259bps. I have adjusted the BRG by one to make 9616bps and things seem to be much better now. Technically, we were only 3.5% out anyway which normally would be OK (ISTR that 5% timing error is the limit).
Anyway, new 0.9 binaries and source here:
http://www.g6lvb.com/Articles/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTrack.c
73, Howard G6LVB
_______________________________________________ Sent via [email protected]. 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
Folks
Sorry, the URLs I gave were a bit wrong, they should be:
http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.c
Cheers, Howard
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: 26 May 2008 11:39 To: [email protected] Subject: [amsat-bb] LVB Tracker 1 Nova fix
Folks
A few weeks ago my attention was drawn to a compatibility problem with Nova and the LVB Tracker 1. I believe that I have found the fault, but it is not clear why it has taken so long for this problem to occur, especially as Nova has been my tracking program of choce for many years! It may only affect more recent versione of Nova.
I have adjusted the LVB Tecker's Baud Rate Generator slightly to be much closer to 9600bps. I must have made an error in my calculations all those years ago, so it was only operating at 9259bps. I have adjusted the BRG by one to make 9616bps and things seem to be much better now. Technically, we were only 3.5% out anyway which normally would be OK (ISTR that 5% timing error is the limit).
Anyway, new 0.9 binaries and source here:
http://www.g6lvb.com/Articles/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTrack.c
73, Howard G6LVB
_______________________________________________ Sent via [email protected]. 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
Thanks Howard,
It worked fine.
Did the programming via serial port.
Used the PicProg.exe file from your website and placed it in C: directory together with the "LVBTrack.hex" file.
Used the "Command Prompt" feature in WinXP and the following command:
C:>PicProg LVBTrack.hex \.\COM7
This is a slight different command line as stated in your documentation since the new hex file has a different name.
Also, for those of you that would like to do that, please use your own com port number (mine was 7)
The program will ask you to set HDR1 and HDR3. These are the 3-way and 2-way headers with the little contact bridges. The 3-way header is actually HDR 1 and is next to the J4 buttons. Both headers have a program (PGM) position.
I left the LVB tracker connected to the YAESU G5500 control box as a power source.
Thanks,
Stefan VE4NSA
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: May-26-08 1:05 PM To: 'Howard Long'; [email protected] Subject: [amsat-bb] Re: LVB Tracker 1 Nova fix
Folks
Sorry, the URLs I gave were a bit wrong, they should be:
http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.c
Cheers, Howard
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: 26 May 2008 11:39 To: [email protected] Subject: [amsat-bb] LVB Tracker 1 Nova fix
Folks
A few weeks ago my attention was drawn to a compatibility problem with Nova and the LVB Tracker 1. I believe that I have found the fault, but it is not clear why it has taken so long for this problem to occur, especially as Nova has been my tracking program of choce for many years! It may only affect more recent versione of Nova.
I have adjusted the LVB Tecker's Baud Rate Generator slightly to be much closer to 9600bps. I must have made an error in my calculations all those years ago, so it was only operating at 9259bps. I have adjusted the BRG by one to make 9616bps and things seem to be much better now. Technically, we were only 3.5% out anyway which normally would be OK (ISTR that 5% timing error is the limit).
Anyway, new 0.9 binaries and source here:
http://www.g6lvb.com/Articles/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTrack.c
73, Howard G6LVB
_______________________________________________ Sent via [email protected]. 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
_______________________________________________ Sent via [email protected]. 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
Thanks Stefan,
Just to add one further thing to avoid any confusion, although HDR1 and HDR3 are referred to, there are in fact only two headers! HDR2 doesn't exist, it was removed early on in a board revision.
73, Howard G6LVB
-----Original Message----- From: Stefan Wagener [mailto:[email protected]] Sent: 27 May 2008 00:48 To: 'Howard Long'; [email protected] Subject: RE: [amsat-bb] Re: LVB Tracker 1 Nova fix
Thanks Howard,
It worked fine.
Did the programming via serial port.
Used the PicProg.exe file from your website and placed it in C: directory together with the "LVBTrack.hex" file.
Used the "Command Prompt" feature in WinXP and the following command:
C:>PicProg LVBTrack.hex \.\COM7
This is a slight different command line as stated in your documentation since the new hex file has a different name.
Also, for those of you that would like to do that, please use your own com port number (mine was 7)
The program will ask you to set HDR1 and HDR3. These are the 3-way and 2-way headers with the little contact bridges. The 3-way header is actually HDR 1 and is next to the J4 buttons. Both headers have a program (PGM) position.
I left the LVB tracker connected to the YAESU G5500 control box as a power source.
Thanks,
Stefan VE4NSA
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: May-26-08 1:05 PM To: 'Howard Long'; [email protected] Subject: [amsat-bb] Re: LVB Tracker 1 Nova fix
Folks
Sorry, the URLs I gave were a bit wrong, they should be:
http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTracker/LVBTrack.c
Cheers, Howard
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Howard Long Sent: 26 May 2008 11:39 To: [email protected] Subject: [amsat-bb] LVB Tracker 1 Nova fix
Folks
A few weeks ago my attention was drawn to a compatibility problem with Nova and the LVB Tracker 1. I believe that I have found the fault, but it is not clear why it has taken so long for this problem to occur, especially as Nova has been my tracking program of choce for many years! It may only affect more recent versione of Nova.
I have adjusted the LVB Tecker's Baud Rate Generator slightly to be much closer to 9600bps. I must have made an error in my calculations all those years ago, so it was only operating at 9259bps. I have adjusted the BRG by one to make 9616bps and things seem to be much better now. Technically, we were only 3.5% out anyway which normally would be OK (ISTR that 5% timing error is the limit).
Anyway, new 0.9 binaries and source here:
http://www.g6lvb.com/Articles/LVBTrack.hex http://www.g6lvb.com/Articles/LVBTrack.c
73, Howard G6LVB
_______________________________________________ Sent via [email protected]. 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
_______________________________________________ Sent via [email protected]. 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
Hi Howard and the group...
I successfully updated my LVB from v0.7 to v0.9
The question is: if you only use the LVB Tracker with a USB cable, can you leave the MAX232 chip installed?
Here is why I ask...
After the successful update, replacement of the USB board and recalibration, I ran a pass and the LVB behaved normally. I then realized I left the MAX232 installed. The installation and DIY assembly instructions suggest you run either the USB board or MAX232 serial but not to have both installed. Or I cannot read or comprehend the instructions???
The AMSAT fully assembled USB version of LVB Tracker including the case requires a lot of extra steps to do a firmware upgrade. To remove the USB board from its socket so that the MAX232 chip can be installed and used, you have to remove the motherboard from the case. This is the only way for the USB connector to clear the case so that it can be pulled straight up and out. Afterwards, to remove the MAX232, there is not enough clearance for a chip puller so you fiddle around with a small screw driver or something similar to pry out the chip.
BTW, I took this opportunity to try to upgrade via the USB port and can confirm it is flaky. The serial upgrade took less than a 1 minute of processing time to upload the firmware and verify. Using the USB only took about 1 hour (yes I waited ) and did not verify 100% ( 5 errors - flipped bits - found in my case ).
Thanks... Alan
Hi Alan
You should have either the MAX232 or the USB board in place, but not both!
Having both devices installed causes contention in the incoming lines and it's not designed to work that way. You may well get undesired effects. It only works for you by luck, not by design!
73, Howard GJ6LVB
-----Original Message----- From: Alan [mailto:[email protected]] Sent: 27 May 2008 23:21 To: 'Howard Long'; [email protected] Subject: [!! SPAM] LVB Tracker Firmware v0.9
Hi Howard and the group...
I successfully updated my LVB from v0.7 to v0.9
The question is: if you only use the LVB Tracker with a USB cable, can you leave the MAX232 chip installed?
Here is why I ask...
After the successful update, replacement of the USB board and recalibration, I ran a pass and the LVB behaved normally. I then realized I left the MAX232 installed. The installation and DIY assembly instructions suggest you run either the USB board or MAX232 serial but not to have both installed. Or I cannot read or comprehend the instructions???
The AMSAT fully assembled USB version of LVB Tracker including the case requires a lot of extra steps to do a firmware upgrade. To remove the USB board from its socket so that the MAX232 chip can be installed and used, you have to remove the motherboard from the case. This is the only way for the USB connector to clear the case so that it can be pulled straight up and out. Afterwards, to remove the MAX232, there is not enough clearance for a chip puller so you fiddle around with a small screw driver or something similar to pry out the chip.
BTW, I took this opportunity to try to upgrade via the USB port and can confirm it is flaky. The serial upgrade took less than a 1 minute of processing time to upload the firmware and verify. Using the USB only took about 1 hour (yes I waited ) and did not verify 100% ( 5 errors - flipped bits - found in my case ).
Thanks... Alan
Hello Alan,
Both the USB and Max232 chip are connected to the same data pins on the microprocessor, so they are both trying to talk to the main routine. It is no recommended to have both the USB and Serial chip in the unit at the same time.
This will also draw extra current that wasn't planned for with the heat sink.
I will be sending out an email to the BB later tonight about the upgrade.
73, Gould
----- Original Message ----- From: "Alan" [email protected] To: "'Howard Long'" [email protected]; [email protected] Sent: Tuesday, May 27, 2008 6:21 PM Subject: [amsat-bb] LVB Tracker Firmware v0.9
Hi Howard and the group...
I successfully updated my LVB from v0.7 to v0.9
The question is: if you only use the LVB Tracker with a USB cable, can you leave the MAX232 chip installed?
Here is why I ask...
After the successful update, replacement of the USB board and recalibration, I ran a pass and the LVB behaved normally. I then realized I left the MAX232 installed. The installation and DIY assembly instructions suggest you run either the USB board or MAX232 serial but not to have both installed. Or I cannot read or comprehend the instructions???
The AMSAT fully assembled USB version of LVB Tracker including the case requires a lot of extra steps to do a firmware upgrade. To remove the USB board from its socket so that the MAX232 chip can be installed and used, you have to remove the motherboard from the case. This is the only way for the USB connector to clear the case so that it can be pulled straight up and out. Afterwards, to remove the MAX232, there is not enough clearance for a chip puller so you fiddle around with a small screw driver or something similar to pry out the chip.
BTW, I took this opportunity to try to upgrade via the USB port and can confirm it is flaky. The serial upgrade took less than a 1 minute of processing time to upload the firmware and verify. Using the USB only took about 1 hour (yes I waited ) and did not verify 100% ( 5 errors - flipped bits - found in my case ).
Thanks... Alan
Sent via [email protected]. 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
Thanks Howard and Gould for the speedy responses. MAX232 removed and business as usual using v0.9
I appreciate Howard's comment about not upgrading unless you have existing problems, however, some of us like to "run around while carrying scissors". In the old days I always installed version X.00 of a new operating system rather than waiting for X.01
I have found one re-occurring problem in that SATPC32 when launching ServerSDX does not always "see" the virtual serial port used by the USB/LVB and required a shutdown of SATPC32 and ServerSDX. Turning the G5400B OFF and ON and then restarting SATPC32 usually results in a ServerSDX connection. Perhaps the LVB timing change will resolve this problem. Time will tell.
-----Original Message----- From: Gould Smith [mailto:[email protected]] Sent: May 27, 2008 6:44 PM To: Alan; 'Howard Long'; [email protected] Subject: Re: [amsat-bb] LVB Tracker Firmware v0.9
Hello Alan,
Both the USB and Max232 chip are connected to the same data pins on the microprocessor, so they are both trying to talk to the main routine. It is no recommended to have both the USB and Serial chip in the unit at the same time.
This will also draw extra current that wasn't planned for with the heat sink.
I will be sending out an email to the BB later tonight about the upgrade.
73, Gould
----- Original Message ----- From: "Alan" [email protected] To: "'Howard Long'" [email protected]; [email protected] Sent: Tuesday, May 27, 2008 6:21 PM Subject: [amsat-bb] LVB Tracker Firmware v0.9
Hi Howard and the group...
I successfully updated my LVB from v0.7 to v0.9
The question is: if you only use the LVB Tracker with a USB cable, can you leave the MAX232 chip installed?
Here is why I ask...
After the successful update, replacement of the USB board and recalibration, I ran a pass and the LVB behaved normally. I then realized I left the MAX232 installed. The installation and DIY assembly instructions suggest you run either the USB board or MAX232 serial but not to have both installed. Or I cannot read or comprehend the instructions???
The AMSAT fully assembled USB version of LVB Tracker including the case requires a lot of extra steps to do a firmware upgrade. To remove the USB board from its socket so that the MAX232 chip can be installed and used, you have to remove the motherboard from the case. This is the only way for the USB connector to clear the case so that it can be pulled straight up and out. Afterwards, to remove the MAX232, there is not enough clearance for a chip puller so you fiddle around with a small screw driver or something similar to pry out the chip.
BTW, I took this opportunity to try to upgrade via the USB port and can confirm it is flaky. The serial upgrade took less than a 1 minute of processing time to upload the firmware and verify. Using the USB only took about 1 hour (yes I waited ) and did not verify 100% ( 5 errors - flipped bits - found in my case ).
Thanks... Alan
Sent via [email protected]. 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
participants (4)
-
Alan -
Gould Smith -
Howard Long -
Stefan Wagener