Date   

Re: Just getting Started

N5IB
 

I just re-uploaded a pair of example parameters files into the "Windows PHSNA" folder. Be sure to rename to "parameters.txt" and make whatever edits are appropriate for your unit.

These **should** open with Notepad, or preferably with the editor inside the WinPHSNA app, and display with proper line breaks.

Jim, N5IB


Re: Just getting Started

Tim
 

Tnx Will
I was using the parameter editor in the Windows program.
Tim


Re: Just getting Started

William Kimber
 

Hi,

I seem to recall that came up before or maybe in the Nat group. It is
result of using wrong type of word processing program.

You want a programmers type rather than an authors type.

It has to put in the Cr and Lf characters rather than run lines together.

Cheers,
Will
.

On 05/06/15 15:35, w4yn@... [PHSNA] wrote:


Have hardware working and trying to get handle on Windows program

I am looking at Parameters file and it seems to be one long line.

I do not see any line separators in file? However if I change Comport
setting it seems to recognize change.

Sorry for easy question but I am not seeing something.

Tim W4YN


Just getting Started

Tim
 

Have hardware working and trying to get handle on Windows program

I am looking at Parameters file and it seems to be one long line.

I do not see any line separators in file? However if I change Comport setting it seems to recognize change.

Sorry for easy question but I am not seeing something.

Tim W4YN


Re: Test

Nick Kennedy
 

Quiet, but still breathing.
(Working CQ WPX CW)

73-

Nick, WA5BDU

On Sun, May 31, 2015 at 12:36 AM, cfarrougia@... [PHSNA] <PHSNA@...> wrote:
 

Is the group still alive ?

Camille.



Re: Test

William Kimber
 

Probably everybody is so busy using they haven't got time to email.

Cheers,
Will
ZL1TAO

On 31/05/15 17:36, cfarrougia@... [PHSNA] wrote:


Is the group still alive ?

Camille.


Re: Test

William R Maxwell
 

Certainly still alive at this end.

On 31/05/2015 3:36 PM, cfarrougia@... [PHSNA] wrote:
 

Is the group still alive ?

Camille.



Test

cfarrougia@...
 

Is the group still alive ?

Camille.


Re: PHSNA at Ham-Com

Nick Kennedy
 

Looking forward to it.  I'll be there!

73-

Nick, WA5BDU


Re: PHSNA Revision 1.40 uploaded

vasilyivanenko@...
 

Good work guys -- thanks
Todd


PHSNA at Ham-Com

N5IB
 

For those of you planning on attending Ham-Com in Irving TX June 12 & 13, I'll be giving a presentation about the PHSNA at 10:00 am, Saturday June 13, in room 11.

The talk will be based on the one that Jerry, Nick, and I gave at OzarkCon 2014. (you can find that one in the Files area) but with some more info about developments since spring of 2014.  We did a tag-team performance there in Branson. Worked out fine, though I think all three of us were a bit breathless when done  :^))

This time I guess I'll do most of the presenting, but I hope that Jerry and Nick will be able to be there also to comment and field questions. I'm hoping Dave can come too and show off the newest NAT.

I'll have a table in the swap meet area and will have some example PHSNA setups and accessories for show and tell, as well as a calibration station if anyone wants to bring their PHSNA to check out. I'll also bring along any PC boards still on hand  It's my plan to be there both Friday the 12th and Saturday the 13th.


Hope to meet some of you next month in Irving.


Jim, N5IB




PHSNA Revision 1.40 uploaded

Nick Kennedy
 

Here is a summary of the revision 1.40 changes to PHSNA for Windows.  A number of these changes were made by Ignacio Cembreros, EB4APL or by the two of us working together.

 

Stopping an endless sweep

 

This is one of the “rough edges” Ignacio wanted to fix.  It’s easy to specify sweep parameters that result in many thousands of points and take forever to complete.  The only remedy before now was to close the program.  Now you can interrupt the sweep for the most often used functions:  Response Sweep, SWR / Return Loss Sweep, Crystal characterization.  Typically you click the button that initiated the function to stop it, but instructions in the text give specifics.

 

Also, buttons that are not applicable to a function are now “turned off” during that function’s operation to prevent inadvertent conflicts.

 

Progress bars

 

This goes with the above concern.  While waiting for a function to complete, you may wonder if anything is happening at all. I’ve added a progress bar below the info text box for the Response Sweep and SWR / Return Loss Sweep functions.  I’ve found that having that information makes the perceived wait seem shorter.

 

With crystal testing, it’s hard to implement a progress bar because the number of points in each scan is unknown.  However, the crystal function consists of three sections:  Find peak, Find lower -3 dB point, and Find upper -3 dB point.  In revision 1.40, RED text in the crystal filename text box tells you which section is currently working.  A crystal scan that “gets lost” can now be interrupted as described above.

 

View graph while sweeping

 

This is something Ignacio added.  Now you can click “show graph” after starting a sweep and the graph will be displayed as it is being created.  It’s a very nice feature similar to the progress bar to keep you informed (and entertained) while the program is gathering the data.

 

Fixing some formatting

 

Ignacio noticed that the descender part of commas sometimes get cut off, making them look like periods or decimal points.  I’ve seen that too.  He increased the font size in the VFO and Upper Limit boxes and maybe elsewhere.  There are some compatibility issues.  I have Windows set up for one step larger text than the default small fonts due to my eyesight.  That made 12 pt type too large for some of the display boxes.  Currently we’ve compromised at 11 points.  Also changed to bold in several places for improved readability.

 

Also, Ignacio enabled comma separators for numbers in the VFO and Stop boxes, which improves readability a lot. Now instead of 10000000 you get 10,000,000.

 

And he discovered that the X-axis of my graphs claimed to be in kHz units but I was sending Hertz to the graph.  Changed to actual kHz which makes the graph a lot easier to read.

 

Return loss / SWR invalid numbers

 

If return loss gets to 0, SWR becomes infinite.  The C# language handles that by showing “INFINITE”, but graphs blow up.  Also, negative return losses are invalid and shouldn’t normally be seen, but might be if the entered open/shorted value for your bridge is incorrect.  Ignacio added a change to substitute 0 for return loss values <= 0.  I kept that but also substitute a value of 0.1 for the return loss used in the SWR calculation, preventing the infinite result and giving a maximum SWR of 173.  I also have the program print a warning saying that the substitution has been made.  Ignacio suggests testing your RLB with both a shorted and an open condition over the frequency range of interest and then picking the highest (most positive) value measured for your open/shorted value in parameters.txt.  (Note that -11.0 dBm is larger than -11.2 dBm.)

 

CSV files, decimal separators and international conflicts

 

Ignacio made some more changes to resolve these issues.  Remember that we already have a CSV separator character in the parameters.txt file.  But that doesn’t fix everything.  Each of us has Windows set up for some country’s standard, which figures in as well.  Some testing will reveal how well it’s working for non-U.S. users now. 

 

I also found that I’d introduced an error in writing out CSV files for the SWR / return loss sweep, making them incorrect regardless of your home country.  I fixed that bug.

 

Response sweep CSV file output bug

 

In the Response Sweep, you can choose compensated dBm, uncompensated dBm or both.  The graphs displayed the selected data OK, but the CSV file always gave both compensated and uncompensated values regardless of what you checked.  I fixed that so now you get only what you requested.

 

Added crystal loss to information displayed

 

This might help folks having difficulty with the crystal function.  The program uses the crystal loss at resonance (difference between dBm at resonance and shorted fixture dBm) to calculate the series resistance Rs, which is then used to figure Q.  Now I print this value to the information text box along with the calculated parameters.

 

Added information on the crystal measurement process to the User’s Guide

 

I’ve added the equations used by PHSNA for crystal parameter calculations so users can know what’s going on “under the hood”.  This could also be useful to users having problems with crystal measurements.  One can manually scan for peak, bandwidth and loss and perform the calculations to see how the values compare with those generated automatically.

 

I also added a couple of schematics and a photograph of a crystal measurement fixture.

 

This information is Appendix I of the User’s Guide.

 

Crisper operation in general

 

It took me quite a while in C# to find the way to make the program allow other events to update while certain code was running.  To update the VFO window during a scan for example, or allow the user to click a button and get the expected response in real time.  Ignacio pointed out that this method allows a lot of things like interrupting an endless task.

 

I now can update status windows, progress bar, and so on while tasks are in process.  Another thing I’ve found is how to make the text window scroll to the bottom when new text is added.  Previously you might not be aware that the latest text is at the bottom, such as when testing multiple crystals.  Or a warning message might not be seen.  Much of that has been improved.

 

Is the serial port working?

 

I sometimes see messages from users with PHSNA problems speculating on whether or not the serial link between the PC and the Arduino is working.  I’ve changed some of the message reporting to make this clearer. The serial port window will show COM# if the link is good and will show NONE if it is not, where # is the number of the port in use.

 

You can click the Setup/Calibrate button to make a “refresh” button appear under the COM port window.  It does two functions.  First, it refreshes the list of available ports in the drop-down.  Second, it performs a test of the serial link by sending an Enquiry byte to the Arduino and then listening for ACK byte in return.  If the ACK is received, a message saying communications has been verified GOOD is shown in the info box.  If the ACK is not received, a message saying that the serial link has FAILED is shown.

 

Also note that after you click the Reset Arduino button and wait out the 5 second delay period, a message showing the Arduino’s software version should appear.  If it does, that’s proof that the serial link is working.

 

Be aware that some system errors related to serial communications aren’t “handled” by PHSNA.  If you unplug the USB cable after establishing the link for example, the program will probably blow up and require restarting.

 

Stop CW sending now!

 

Previously, CW sending would stop after the current message completed when requested. Now it stops after the current character completes.


*********


Quite a few changes and corrections.  I've left version 1.39 up for now in case some serious bug should reveal itself.  I'll delete it in a week or so.  The new PHSNA User's Guide has also been uploaded.


73-


Nick, WA5BDU



Programmable Attenuator and Splitter/Combiner boards

Dave WB6DHW
 

The boards have been shipped from the board house in Hongkong. Should be here next week before I leave for Dayton on Sunday the 10th.
I made a mistake on the boards and had to resubmit the Gerber files. So, I was able to include the capacitor on the output.

Dave - WB6DHW
<http://wb6dhw.co>


Re: Valid COM Port

Dennis Rogers
 

Word to the wise. ONLY get it from sourceforge otherwise malware with come with it.

Dennis
N5VRP


On Sat, Apr 25, 2015 at 11:10 PM, 'K5ESS' k5ess.nothdurft@... [PHSNA] <PHSNA@...> wrote:
 

Just to put in my 2 cents worth;  Notepad++ is super.  I highly recommend it.

Mike

K5ESS

 

From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 11:05 PM
To: PHSNA@...
Subject: RE: [PHSNA] Valid COM Port

 

 

Ed, Nick and the group,

 

I gave up on Notepad and WordPad and I now use Notepad++ for all of my text file editing.  It is a free download and it works!

 

To see non-printable characters, after the file is opened, select

 

     

     

     

 

And you can see ALL characters that are in the file.

 

FYI – The CR|LF sequence is a holdover from TTY days.  When a carriage return character (hex 13) is sent, it was ALWAYS followed by a line feed character (hex 10).  This prevented a character from being printed as the type box was moving from right to left.

 

Anyhow, using Notepad++ will show ALL unprintable characters that are included in the text file.

 

Jay

AJ4AY

Mobile, AL

 

From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 10:04 PM
To: PHSNA@...
Subject: Re: [PHSNA] Valid COM Port

 

 

Nick:

     While groping around in the file I noticed several things that I did not understand. One was when I viewed the downloaded file before saving it in its proper folder the lines were all strung together but when I saved it to its folder and then viewed it the lines were separate. When I copied/pasted the file into an e-mail so you and Jim could view it the lines were double spaced.

     I think my problems started when I edited the strung together version so that it looked like samples I have seen. My real problem was having the wrong filing system which you and Jim corrected for me, but I muddied the water by messing with the files and when the filing method was solved the format was now wrong. When I got the properly formatted file and everything worked I again muddied the waters further by editing out the end comma to test the suggestion that was the problem. It was part of the problem for sure, and when I re-inserted the comma I once again had a improperly formatted file; only I could not see it.

    The lesson I have learned is to use notepad for viewing only and even then I can not trust what I see. I am much better with antique motorcycles, there I can see what is wrong; no smoke and mirrors there.

     Thanks again.

Nothing says you're  serious like using a cart to shop in a liquor store.

 

Ed Miller




--
------------------------------------------------------
Dennis, N5VRP
n5vrp.satx@...

Near Hemphill, Texas


Re: Valid COM Port

K5ESS
 

Just to put in my 2 cents worth;  Notepad++ is super.  I highly recommend it.

Mike

K5ESS

 

From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 11:05 PM
To: PHSNA@...
Subject: RE: [PHSNA] Valid COM Port

 

 

Ed, Nick and the group,

 

I gave up on Notepad and WordPad and I now use Notepad++ for all of my text file editing.  It is a free download and it works!

 

To see non-printable characters, after the file is opened, select

 

     

     

      <Show All Characters>

 

And you can see ALL characters that are in the file.

 

FYI – The CR|LF sequence is a holdover from TTY days.  When a carriage return character (hex 13) is sent, it was ALWAYS followed by a line feed character (hex 10).  This prevented a character from being printed as the type box was moving from right to left.

 

Anyhow, using Notepad++ will show ALL unprintable characters that are included in the text file.

 

Jay

AJ4AY

Mobile, AL

 

From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 10:04 PM
To: PHSNA@...
Subject: Re: [PHSNA] Valid COM Port

 

 

Nick:

     While groping around in the file I noticed several things that I did not understand. One was when I viewed the downloaded file before saving it in its proper folder the lines were all strung together but when I saved it to its folder and then viewed it the lines were separate. When I copied/pasted the file into an e-mail so you and Jim could view it the lines were double spaced.

     I think my problems started when I edited the strung together version so that it looked like samples I have seen. My real problem was having the wrong filing system which you and Jim corrected for me, but I muddied the water by messing with the files and when the filing method was solved the format was now wrong. When I got the properly formatted file and everything worked I again muddied the waters further by editing out the end comma to test the suggestion that was the problem. It was part of the problem for sure, and when I re-inserted the comma I once again had a improperly formatted file; only I could not see it.

    The lesson I have learned is to use notepad for viewing only and even then I can not trust what I see. I am much better with antique motorcycles, there I can see what is wrong; no smoke and mirrors there.

     Thanks again.

Nothing says you're  serious like using a cart to shop in a liquor store.

 

Ed Miller


Re: Valid COM Port

Jay Henson
 

Ed, Nick and the group,

 

I gave up on Notepad and WordPad and I now use Notepad++ for all of my text file editing.  It is a free download and it works!

 

To see non-printable characters, after the file is opened, select

 

     

     

     

 

And you can see ALL characters that are in the file.

 

FYI – The CR|LF sequence is a holdover from TTY days.  When a carriage return character (hex 13) is sent, it was ALWAYS followed by a line feed character (hex 10).  This prevented a character from being printed as the type box was moving from right to left.

 

Anyhow, using Notepad++ will show ALL unprintable characters that are included in the text file.

 

Jay

AJ4AY

Mobile, AL

 

From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 10:04 PM
To: PHSNA@...
Subject: Re: [PHSNA] Valid COM Port

 

 

Nick:

     While groping around in the file I noticed several things that I did not understand. One was when I viewed the downloaded file before saving it in its proper folder the lines were all strung together but when I saved it to its folder and then viewed it the lines were separate. When I copied/pasted the file into an e-mail so you and Jim could view it the lines were double spaced.

     I think my problems started when I edited the strung together version so that it looked like samples I have seen. My real problem was having the wrong filing system which you and Jim corrected for me, but I muddied the water by messing with the files and when the filing method was solved the format was now wrong. When I got the properly formatted file and everything worked I again muddied the waters further by editing out the end comma to test the suggestion that was the problem. It was part of the problem for sure, and when I re-inserted the comma I once again had a improperly formatted file; only I could not see it.

    The lesson I have learned is to use notepad for viewing only and even then I can not trust what I see. I am much better with antique motorcycles, there I can see what is wrong; no smoke and mirrors there.

     Thanks again.

Nothing says you're  serious like using a cart to shop in a liquor store.

 

Ed Miller


Re: Valid COM Port

Ed Miller
 

     I knew I could edit files within the program but did not realize how important it was to use the feature, I know now. Notepad is not my friend.
    Thank you for your response.

Nothing says you're  serious like using a cart to shop in a liquor store.

Ed Miller

On Apr 25, 2015, at 7:34 PM, EB4APL eb4apl@... [PHSNA] <PHSNA@...> wrote:

 

Ed,

The text editor that you are using is inserting extra characters. 
Probably you don't know yet but the PHSNA program has an editor just for showing/editing the configuration file.  Go to Setup/calibrate, Show Parameters File, edit there (use care, whatever is on the window will be written, in doubt click Clear and start all over again) and the Write Parameters File.

Ignacio EB4APL


El 26/04/2015 a las 1:26, 'Ed Miller' kc4mhm@... [PHSNA] wrote:
 

Nick:

            You are correct about the lack of a comma in the last line. I had the program working and edited out the comma, it quit working, I inserted the comma, saved the edit but it did not start to work again. I do not know what a linefeed is, I do not see anything that looks out of place. Is it possible for some characters/symbols to be hidden when the file is viewed in notepad?

 

            I just went back to my “downloads” and re-saved the file I downloaded from the web as N5IB suggested earlier and all is working again. I edited and saved the COM port and freq and program opened as expected. I plan to leave well enough alone.

            Thank you for your help.

                        Ed

 


From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 7:05 PM
To: PHSNA@...
Subject: RE: [PHSNA] Valid COM Port

 

 

Wow, you have a strange looking parameters.txt file indeed.  

 

Some text files have a linefeed (10) and a carriage return (13) character at the end of each line.  Some have only a linefeed (I think).  Your file has two linefeeds at the end of each line.

 

Also, there are linefeeds inserted within your polynomical cofficients after the first digit.

 

Also, there should be either a comma or a semicolon at the end of the file (Comma for U.S. users.) Your file doesn't have either.

 

I could patch your data into a workable file if needed.

 

73-

 

Nick, WA5BDU




Re: Valid COM Port

Ed Miller
 

Nick:
     While groping around in the file I noticed several things that I did not understand. One was when I viewed the downloaded file before saving it in its proper folder the lines were all strung together but when I saved it to its folder and then viewed it the lines were separate. When I copied/pasted the file into an e-mail so you and Jim could view it the lines were double spaced.
     I think my problems started when I edited the strung together version so that it looked like samples I have seen. My real problem was having the wrong filing system which you and Jim corrected for me, but I muddied the water by messing with the files and when the filing method was solved the format was now wrong. When I got the properly formatted file and everything worked I again muddied the waters further by editing out the end comma to test the suggestion that was the problem. It was part of the problem for sure, and when I re-inserted the comma I once again had a improperly formatted file; only I could not see it.
    The lesson I have learned is to use notepad for viewing only and even then I can not trust what I see. I am much better with antique motorcycles, there I can see what is wrong; no smoke and mirrors there.
     Thanks again.

Nothing says you're  serious like using a cart to shop in a liquor store.

Ed Miller

On Apr 25, 2015, at 8:16 PM, Nick Kennedy kennnick@... [PHSNA] <PHSNA@...> wrote:

 

No, you can't see those line control bytes, which does make it hard when a plain text file is messed up.  It's nothing you could have seen.

You have to look at the file with something called a hex editor to see the hidden codes.  I use one called FRHED.EXE, which stands for "free hex editor".  Such editors will show the plain text (if printable) of your file and next to it, the actual bytes (in decimal or hex format) that make up the file.  

Those codes are archaic, telling a printer to move the print head to the left staring position and advance the paper roller one line.  Some software (text editors) want both codes and some just need the line feed.  Some are smart enough to display properly with either.

Notepad wants both characters and mushes everything together if you don't have both, although it will word wrap at the end of its visible page.  I sometimes use a free programmers editor called Programmer's Notepad that will show correctly with 10 13 or just 10 at the end of each line.  BTW, if viewed in hex, these 10 and 13 decimal characters are 0A and 0D.

So, I told you more than you need to know but I'm glad you seem to be making progress.

73-

Nick, WA5BDU



On Sat, Apr 25, 2015 at 6:26 PM, 'Ed Miller' kc4mhm@... [PHSNA] <PHSNA@...> wrote:
 

Nick:

            You are correct about the lack of a comma in the last line. I had the program working and edited out the comma, it quit working, I inserted the comma, saved the edit but it did not start to work again. I do not know what a linefeed is, I do not see anything that looks out of place. Is it possible for some characters/symbols to be hidden when the file is viewed in notepad?

 

            I just went back to my “downloads” and re-saved the file I downloaded from the web as N5IB suggested earlier and all is working again. I edited and saved the COM port and freq and program opened as expected. I plan to leave well enough alone.

            Thank you for your help.

                        Ed



Re: Valid COM Port

Nick Kennedy
 

No, you can't see those line control bytes, which does make it hard when a plain text file is messed up.  It's nothing you could have seen.

You have to look at the file with something called a hex editor to see the hidden codes.  I use one called FRHED.EXE, which stands for "free hex editor".  Such editors will show the plain text (if printable) of your file and next to it, the actual bytes (in decimal or hex format) that make up the file.  

Those codes are archaic, telling a printer to move the print head to the left staring position and advance the paper roller one line.  Some software (text editors) want both codes and some just need the line feed.  Some are smart enough to display properly with either.

Notepad wants both characters and mushes everything together if you don't have both, although it will word wrap at the end of its visible page.  I sometimes use a free programmers editor called Programmer's Notepad that will show correctly with 10 13 or just 10 at the end of each line.  BTW, if viewed in hex, these 10 and 13 decimal characters are 0A and 0D.

So, I told you more than you need to know but I'm glad you seem to be making progress.

73-

Nick, WA5BDU



On Sat, Apr 25, 2015 at 6:26 PM, 'Ed Miller' kc4mhm@... [PHSNA] <PHSNA@...> wrote:
 

Nick:

            You are correct about the lack of a comma in the last line. I had the program working and edited out the comma, it quit working, I inserted the comma, saved the edit but it did not start to work again. I do not know what a linefeed is, I do not see anything that looks out of place. Is it possible for some characters/symbols to be hidden when the file is viewed in notepad?

 

            I just went back to my “downloads” and re-saved the file I downloaded from the web as N5IB suggested earlier and all is working again. I edited and saved the COM port and freq and program opened as expected. I plan to leave well enough alone.

            Thank you for your help.

                        Ed



Re: Valid COM Port

EB4APL
 

Ed,

The text editor that you are using is inserting extra characters.�
Probably you don't know yet but the PHSNA program has an editor just for showing/editing the configuration file.� Go to Setup/calibrate, Show Parameters File, edit there (use care, whatever is on the window will be written, in doubt click Clear and start all over again) and the Write Parameters File.

Ignacio EB4APL


El 26/04/2015 a las 1:26, 'Ed Miller' kc4mhm@... [PHSNA] wrote:

�

Nick:

����������� You are correct about the lack of a comma in the last line. I had the program working and edited out the comma, it quit working, I inserted the comma, saved the edit but it did not start to work again. I do not know what a linefeed is, I do not see anything that looks out of place. Is it possible for some characters/symbols to be hidden when the file is viewed in notepad?

�

����������� I just went back to my �downloads� and re-saved the file I downloaded from the web as N5IB suggested earlier and all is working again. I edited and saved the COM port and freq and program opened as expected. I plan to leave well enough alone.

����������� Thank you for your help.

����������������������� Ed

�


From: PHSNA@... [mailto:PHSNA@...]
Sent: Saturday, April 25, 2015 7:05 PM
To: PHSNA@...
Subject: RE: [PHSNA] Valid COM Port

�

�

Wow, you have a strange looking parameters.txt file indeed. �

�

Some text files have a linefeed (10) and a carriage return (13) character at the end of each line. �Some have only a linefeed (I think). �Your file has two linefeeds at the end of each line.

�

Also, there are linefeeds inserted within your polynomical cofficients after the first digit.

�

Also, there should be either a comma or a semicolon at the end of the file (Comma for U.S. users.) Your file doesn't have either.

�

I could patch your data into a workable file if needed.

�

73-

�

Nick, WA5BDU



1181 - 1200 of 3088