[hpsdr] New Metis and Hermes code.

Mon Feb 18 20:06:24 PST 2013

Hi John,

The only possible issue with using an APIPA IP address is that sometimes
the PC operation system can take quite a while to assign one to the PC. My
PC using Windows 8 can take > 20 seconds from power on.

In which case if you set a fixed IP address to Hermes AND the network card
you will avoid this delay.

You can always reset the Hermes IP address when you need to use it at the
club.

73 Phil...VK6APH

> HI John,
> glad you made progress. Sounds like the rig is behaving correctly.
>
> well make sure your Ethernet connections (cards, router, switch) are
> a minimum of 100BT (100 Mega bits per second) or the Hermes will not
> perform properly for you.
>
> If you use a standard CAT5 cable between your Hermes and any PC LAN
> connection, it will negotiate what is known as an "APIPA" address (A
> Private IP Address) and both PC and rig will be totally happy about it.
> This is a special feature of the networking firmware that Phil labored
> on for a year. He has created a wonderful and extremely flexible network
> interface.
>
> You do *not* need what used to be called a "crossover cable". Modern
> Network interfaces, like Phil's Hermes, are able to talk to another
> piece of equipment without crossing over Rx and Tx like we had to do in
> the olden-days <g>
>
> Sounds like you are well on your way to some fun listening and then some
> great QSOs.
>
> GL my friend,
> 73 de Ken N9VV
>
>
> On 2/18/2013 8:01 PM, John wrote:
>> Hi Ken,
>>
>> The radio works fine now and I really appreciate your help.
>>
>> I read the new Hermes manual (v 1.16; at the link you sent me) and
>> studied Appendix A.  Also, I downloaded the Bootloader and .pof files,
>> but did not put them in the same directory as the installed Bootloader
>> program.  I followed the first section of Appendix A and it seemed to
>> load the program.  However, I did not select the .pof file since
>> Appendix A said use the .rbf file.  Perhaps that EPROM info is in the
>> .rbf, too.  Everything seemed to go well, but then when I tried
>> Programmer 2, it erased it and the red dot in the lower right corner was
>> always red.  Next, I repeated what I had done in Appendix A and it
>> seemed to work fine again.  This time I never used Programmer 2 and just
>> opened PowerSDR (the new one).  At first it didn't read the MAC address
>> or IP address, but I found I could turn on the Hermes and next time I
>> checked setup, it displayed the IP and MAC as well as the new firmware
>> version.
>>
>> So, now I'm way ahead of where I was before I started the upgrade.  This
>> time, before I try to change the IP address, I would like to be
>> confident it will do what I want to do.  Perhaps I should leave it as it
>> is.
>>
>> First of all, for the immediate future, Hermes is the only device I will
>> have on the Ethernet.  I don't know if it is a DCHP server or not.  It
>> is an Ethernet card I added a few years ago.  All I would like is to
>> reduce the time it takes to connect the PC to Hermes (now approximately
>> a minute after power is applied to Hermes).  Since the software sets the
>> address of Hermes in Hermes, Hermes with a static IP must somehow make
>> itself quickly known to the PC (other that letting the PC try each
>> address to see which answer present), if this is to reduce the time.
>> Should I let PowerSDR find the IP address and just set that as a static
>> address with one of the programmers?  Or is there a better way?  Or am
>> way off course?
>>
>> Second, I may want to take the rig to our local ham club and run it on
>> someones laptop.  If Hermes does promote its address to the PC without
>> being asked, I'm assuming it will work on another PC that has PowerSDR
>> and the necessary .net files on it.  Is that correct, or will I need to
>> reset the IP address to 0.0.0.0 at let the other PC check every address
>> until it finds Hermes?
>>
>> Best regards,
>>
>> John,  WoGN
>>
>>
>>
>>
>> On 2/18/2013 3:32 PM, Ken N9VV wrote:
>>> Hi John,
>>> you probably wrote over the first megabyte of the EEPROM that contains
>>> the "Bootloader" code (the .pof file). The upper megabyte of the
>>> EEPROM contains the FPGA firmware code (the .rbf file).
>>> =====================================
>>> It is very easy now to fix both problems if you take a little care.
>>> Download the Bootloader *AND* the bootloader.pof file that goes with
>>> it.
>>> Execute that code and see if it reaches the rig. If it does not, then
>>> you will need to back up one step and use a ByteBlaster deice (USB to
>>> P2 on the Hermes board) to accomplish the bootloader operation.
>>> =====================================
>>> Second, download and install HPSDRProgrammer and the associated .rbf
>>> file that goes with it. Run the program and it will discover the
>>> Hermes board (with a bootloader properly installed) and then
>>> successfully load the upper 1MB of the EEPROM. Let the IP address
>>> DEFAULT TO WHATEVER DHCP address you have available from your router.
>>> I assume you have a DHCP server in your router(?).
>>> =====================================
>>> This is a video that I made for Hank K9LZJ may help you figure it out;
>>> http://www.screencast.com/t/0itauOkDzd3
>>> =====================================
>>> This is the Hermes manual that Phil skillfully edited and created:
>>> <URL:
>>> http://svn.tapr.org/repos_sdr_hpsdr/trunk/Hermes/Documentation/Hermes_User_Manual_V1.16.pdf
>>>
>>>
>>> >
>>> =====================================
>>> Here is the Bootloader manual that I tried to write:
>>> http://www.n9vv.com/Images/Apache-Labs/ByteBlaster-Instructions.pdf
>>> =====================================
>>>
>>> Keep those questions coming. I am sure we can help you get back on
>>> the air in just a few minutes.
>>>
>>> You can call me on Skype-ID "Apache-Labs" if I can help you over the
>>> phone, the direct phone number is 1-630-445-1194. This is a service
>>> that Apache Labs is pleased to provide to the OpenHPSDR community.
>>> BK de Ken N9VV
>>
>>
>
> --
> http://groups.yahoo.com/group/apache-labs/
> http://www.n9vv.com/
> Skype ID "Apache-Labs"
> [-GMT -5]
>
>

 1361246784.0