[hpsdr] HPSDRProgrammer_v2_nocap V2.0.4.9
Dick Faust
k9ivb at cox.net
Sun Apr 20 14:54:19 PDT 2014
Dave
I do believe I have located the issue I had with
HPSDRProgrammer_v2_nopcap V2.0.4.9.
Micro$oft [aka Miracle$h-t] has chosen to assign the identical file name
"dotnetfx35.exe" in downloads to _*both*_***dotnetfx35 and dotnetfx35-SP1**!
*_*
*_The file dotnetfx35 [SP-0] does not work and dotnetfx35 [SP1] appears
to solve the problem
You may wish to explicitly specify the SP1 in the documentation.
Dick
On 3/4/2014 7:29 AM, Dave Larsen wrote:
>
> Dick
>
> I am busy at work but I will try to create your configure you system
> in my shack an test it this week. This email let me know what I need.
>
> Dave KV0S
>
> On Mar 4, 2014 1:38 AM, "Dick Faust" <k9ivb at cox.net
> <mailto:k9ivb at cox.net>> wrote:
>
> Dave
> I do not have 2 links to the same address space. One [the WiFi]
> goes to my router [DHCP IP 192.168.1.xxx], the second NIC goes
> directly to the Hermes or to the Metis [APIPA IP 169.254.x.x]. It
> does not make any difference if the WiFi connection is enabled or
> disabled you get the error screen [as an attachment gif this
> time]. The Adapter Watch program clearly shows each adapter
> connected to the separate networks.
> The older programmer works, the new one does not .
>
> There was another post on the list today from G4KFZ with the same
> issue.
>
> Perhaps in your testing you did not test with XP. All of my XP
> systems were clean install XP Pro SP3 without any additional
> automatic updates from M$. All of the Net Framework garbage was
> installed as well.
>
> Dick K9IVB
>
> On 3/3/2014 10:02 PM, Dave Larsen wrote:
>
> Dick
>
> I can not see the error message in either message. it seems
> the email software removed the image of paste text.
>
> My best guess is that several people in HPSDRProgrammer and
> PowerSDR have had crouble if you have two interfaces to the
> same address space.
>
> so if you have a wireless and a wired link to the same IP
> space. so there are two ways to get to the HPSDR board
>
>
> I did quite a bit of testinf with a hermes and metis on one
> network while I had another network present. The I moved both
> boards to the other network and I had no problem program
> either board. I did turn off the wireless on my laptop and
> used the wired line.
>
> Dave KV0S
>
>
> On Mon, Mar 3, 2014 at 11:14 AM, Dick Faust <k9ivb at cox.net
> <mailto:k9ivb at cox.net> <mailto:k9ivb at cox.net
> <mailto:k9ivb at cox.net>>> wrote:
>
> Dave
> In looking at Phil's reply,I did not see a copy of the
> error image
> that was supposed to be imbedded after " ...
>
> I received the following popup:"
>
>
>
> Any suggestions would be appreciated.
>
> Thanks
>
> Dick K9IVB
>
>
> On 3/3/2014 4:16 AM, Phil Harman wrote:
>
> Hi Dick,
>
> Thanks for your email. Can't really help with the
> Programmer
> problem so suggest you contact Dave, KV0S, who wrote it.
>
> (kv0s.dave at gmail.com <mailto:kv0s.dave at gmail.com>
> <mailto:kv0s.dave at gmail.com <mailto:kv0s.dave at gmail.com>>)
>
> I'm sure your instructions for using multiple copies of
> PowerSDR would be of interest to others. Again Dave
> maintains the openHPSDR web site and Wiki which I
> think would
> be an ideal home for your document.
>
> 73 Phil...VK6PH
>
>
>
> -----Original Message----- From: Dick Faust
> Sent: Monday, March 3, 2014 2:40 PM
> To: Phil Harman
> Subject: HPSDRProgrammer_v2_nocap V2.0.4.9
>
> Hi Phil
>
> The last time I updated my boards [May 2013]I did not keep
> notes. This
> time I decided to make notes in case Murphy were to
> appear -
> of course
> he did !
>
> I have been playing around with some HTPC boxes and
> got one
> from Foxconn
> with a dual core Atom D525 that would work on XP and
> Win7. I
> decided to
> maks a some what portable Station as the Nettop will mount
> directly to
> the mounting holes on the back of most monitors.
>
> I traded in my Penny for a PennyLane at TAPR and needed to
> update the
> new board and thought I could use the Atom to
> reprogram and setup
> mutiple units of PowerSDR_mRX_PS_v3.2.8.0 for Hermes
> and the
> Atlas-Metis
> and Atlas-OZY [thought I would use this as the v3.2.9.x
> appears to be
> having some issues].
>
> I am running XP Pro SP3 on the Atom [no automatic
> updates what
> so ever]
> I installed all of the ugly NET Framework programs and the
> WInpcap as
> outlined in the setup guides [virtually the same setup
> as May
> 2013 on
> another XP Pro SP3 with a Pentium G860].
>
> When I ran the programmer on my Hermes I received the
> following popup:
>
>
>
> I have a wireless connection to my network and the
> Hermes is
> directly
> attached to the NIC on board [10-100-1000]. It made no
> difference if I
> turned the WiFi on or off, other than the programmer would
> default to
> the wireless if it were on and I would switch to the
> NIC on
> board. I
> did not change anything on the Hermes and do not have
> a jumper
> on J12..
>
> When I loaded the old Programmer
> [HPSDRProgrammer_V2-2.0.4.0.msi] and
> ran the programmer on my Hermes it did the update to
> Hermes_V2.5a.rbf
> with out a problem.
>
> Next I disassembled my Atlas box and tried to do the
> same with
> Metis and
> received the same error with v2.0.4.9 [and J1 off].
> The old
> version
> [v2.0.4.0] worked fine to do the update to Metis 2.6b.
>
> The HPSDRBootloader 2.0.4.3 worked fine to update my
> PennyLane and
> Mercury with Metis with the J1 jumper on.
>
> What am I missing with the new Programmer ?
>
> I also use a neat program from Nirsoft called Adapter
> Watch
> which give
> you all of the info on all the NIC's on board. You
> might find
> it useful.
>
> http://www.nirsoft.net/utils/awatch.html
>
> A secondary & side issue of my endeavors today is the
> implementation of
> multiple instances of PowerSDR_mRX_PS_v3.2.8.0.
> Previous posts
> on the
> list seem to have bad info. I can not believe I am the
> only
> one trying
> to do this. I decided to try to follow the
> instructions. I could
> modify the install path for the first install [inst say to
> install 2nd
> to a different location, but the installer will not
> permit this !]
> I ended up installing the first to:
> C:\Program Files\OpenHPSDR\PowerSDR mRX PS_3280_Hermes.
> The second and third I just copied the entire contents
> of the
> install to
> each of the following locations.:
> C:\Program Files\OpenHPSDR\PowerSDR mRX
> PS_3280_Atlas_Metis
> and
> C:\Program Files\OpenHPSDR\PowerSDR mRX PS_3280_Atlas_Ozy
>
> When it came to generating the shortcuts to the unique
> database
> locations there is a syntax error in most
> representations of the
> datapath command. The -datapath: must not be enclosed in
> quotes for the
> command as illustrated below:
>
> "C:\Program Files\OpenHPSDR\PowerSDR mRX
> PS_3280_Hermes\PowerSDR.exe"
> -datapath:"C:\HPSDR_db\Hermes"
>
> "C:\Program Files\OpenHPSDR\PowerSDR mRX
> PS_3280_Atlas_Metis\PowerSDR.exe"
> -datapath:"C:\HPSDR_db\Atlas_Metis"
>
> "C:\Program Files\OpenHPSDR\PowerSDR mRX
> PS_3280_Atlas_Ozy\PowerSDR.exe"
> -datapath:"C:\HPSDR_db\Atlas_Ozy"
>
> Is there someplace this information can be located ? I am
> willing to
> write it up in a little more detail if necessary. I
> can also
> post it on
> my website if there is no place else to put it.
>
> Well Murphy struck again. I was composing this while
> waiting for
> PowerSDR to initialize for the Atlas-Metis
> configuration. Now
> Mercury
> does not want to receive any signals and I can not
> verify my
> multiple
> instance approach actually works.
>
> Out of time and have to put all away - perhaps will
> get back next
> weekend and go back to when it last worked setup.
>
> If you can shed any light on the Programmer error
> message I would
> appreciate your input.
>
>
> Thanks for your help
>
>
> ---
> This email is free from viruses and malware because avast!
> Antivirus protection is active.
> http://www.avast.com
>
>
>
>
>
>
> --
> KV0S - Dave Larsen
> Columbia, MO, USA
>
>
More information about the Hpsdr
mailing list