Echolink does not record lat and lon

Echolink connections are being made and my echolink station is registered, but apparently the supplemental information, most critically lat and lon is not being captured by the echolink system.

Nothing showed up in search.

As requested for other questions, the echolink.conf file is below:

[el0]
confmode=no
call=AB1PH-R ; Change this!
pwd=****** ; Change this!
name=Don Rolph ; Change this to your real name!
qth=East Walpole, MA, US ; Change this to your actual QTH!
email=don.rolph@gmail.com ; Change this!
maxstns=20
rtcptimeout=10
node=665560 ; Echolink node number - Change this!
recfile=/tmp/recorded.gsm
astnode=53345 ; Change this to your active Allstar node number!
context=radio-secure
server1=server1.echolink.org
server2=server2.echolink.org
;server2=server3.echolink.org
server3=server3.echolink.org
;
;
; Change following setting to your parameters
freq=146.895
tone=123.0
lat=42.1475
lon=-71.2268
;;;
;;; For power, height, gain and dir, use the digits 0 thru 9:
;;;
;;; DIGITS 0 1 2 3 4 5 6 7 8 9 Equation
;;; -------------------------------------------------------------------
;;; POWER 0, 1, 4, 9, 16, 25, 36, 49, 64, 81 watts SQR(P)
;;; HEIGHT 10,20,40, 80,160,320,640,1280,2560,5120 feet LOG2(H/10)
;;; GAIN 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 dB
;;; DIR 0,45,90,135,180,225,270, 315, 360, . deg (D/45)
;;;
; power: 25W, height: 80ft, gain: 6dB, dir: 180 deg
power=1
height=20
gain=1
dir=0
;
; Message about your Echolink node. Up to 256 characters All in
; one line. Use \n for newline. Uncomment to use.
;
;message=This is my message\nand another line\n
;
; Deny-permit - Only use one, either whitelist using permit or
; blacklist using deny Echolink stations. Wildcards can be used
; Example - permit WA3DSP*,W3XYZ* would allow these calls
; by themseleves or with -L or -R suffix. Uncomment to use.
;
;deny=
;permit=

After some more testing:

deleting the fry and tone lines allow lat and lon to be recognized by the echo link system.

adding freq and tone below the lat and lon entries does not provide them to echo link.

No matter what the power height, gain, and dir fields are not read.

There seems to be something odd killing these entries in the echo link.conf file.

I seem to be very confused.

Thanks in advance!

Ok deleting and retyping the freq and tone lines seems to have fixed it.

This is the second time I have had this problem after editing echo link.xxx file on two different builds.

I think there may be some bad hidden characters in the Echlin.xxx file on the freq and/or tone lines.