Have just installed the latest release, Version 1.12.1.0
I have imported my ADIF file but the TX Power column does not get populated. Reviewing the ADIF file I used shows TX power for each contact. For example, <TX_PWR:4>20.0.
Any suggestions?
Thanks.
Jim W1RET
TX Power not being imported
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: TX Power not being imported
Hi Jim,
Please email me you ADIF bt email so that I can replicate the problem
Please email me you ADIF bt email so that I can replicate the problem
73 Terry G4POP
Re: TX Power not being imported
Thanks Terry. It's on the way.
Jim W1RET
Jim W1RET
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: TX Power not being imported
For the benefit of other users here is an explanation of the problem.
DXKeeper record TX power with a decimal point like 20.0 whereas most of us use the ADIF format without the decimal point like 20
Its one of those situations where the ADIF spec says the decimal point is optional and so far this is the first time I have encountered this issue of a software developer actually using it.
Quoted from the ADIF Specification.
"a sequence of Digits optionally preceded by a minus sign (ASCII code 45) and optionally including a single decimal point (ASCII code 46)"
I have asked Daniele to modify our ADIF import to recognise the decimal value so that the TX Power in a DXLabs ADIF's are no longer ignored.
Meanwhile we are fixing Jim's file so that it imports correctly..
DXKeeper record TX power with a decimal point like 20.0 whereas most of us use the ADIF format without the decimal point like 20
Its one of those situations where the ADIF spec says the decimal point is optional and so far this is the first time I have encountered this issue of a software developer actually using it.
Quoted from the ADIF Specification.
"a sequence of Digits optionally preceded by a minus sign (ASCII code 45) and optionally including a single decimal point (ASCII code 46)"
I have asked Daniele to modify our ADIF import to recognise the decimal value so that the TX Power in a DXLabs ADIF's are no longer ignored.
Meanwhile we are fixing Jim's file so that it imports correctly..
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: TX Power not being imported
Obviously from next release...
If someone has the same needs we can fix the ADIF log easily from DXLABS format.
Just send it to me or Terry.
In the next release Log4OM will automatically detect this behaviour and fix it
73
Daniele
If someone has the same needs we can fix the ADIF log easily from DXLABS format.
Just send it to me or Terry.
In the next release Log4OM will automatically detect this behaviour and fix it
73
Daniele
Daniele Pistollato - IW3HMH
Re: TX Power not being imported
Thank you. A very fast response!
Jim W1RET
Jim W1RET
Re: TX Power not being imported
Same problem seen with a recent import from HRD Logbook v6.1....power is save as ##.###. As a result, nothing is saved in the power field.
73
Dave
K3DCW
73
Dave
K3DCW
K3DCW
Elecraft K3
Elecraft K3
- G4POP
- Log4OM Alpha Team
- Posts: 10815
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: TX Power not being imported
Hi Dave,k3dcw wrote:Same problem seen with a recent import from HRD Logbook v6.1....power is save as ##.###. As a result, nothing is saved in the power field.
73
Dave
K3DCW
Send me the HRD ADIF by email and I will fix it for you
73 Terry G4POP
- IW3HMH
- Site Admin
- Posts: 2927
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: TX Power not being imported
Next release will deal with this issue.
In the meanwhile we can support you case by case
73
Daniele
In the meanwhile we can support you case by case
73
Daniele
Daniele Pistollato - IW3HMH