[DXLog.net - Support] Failure CAT

EC7AKV Fonsi ec7akv at gmail.com
Sat Oct 5 11:44:45 CEST 2013


yes chris i have the last version 2.0.17

9A5K <9a5k at 9a5k.com> escribió:
>Hi Alfonso..
>
>Did you try this with v2.0.17 now?
>I've found a bug with CI-V code in previous version and it was fixed in
>2.0.17.
>Rin, JG1VGX had similar problem with previous version and he confirmed
>that
>2.0.17 works ok now with his IC-706.
>I've checked also with mine IC-756PROIII, and was OK too now.
>
>
>
>
>
>
>On Sat, Oct 5, 2013 at 11:23 AM, EC7AKV Alfonso <ec7akv at gmail.com>
>wrote:
>
>> **
>> my CAT on my IC-706MKIIG no work, when work is during... 4 or 5
>second, or
>> ... i can't move dial, when i turn dial CAT is lost.
>>
>> I use Omnirig, and no use Omnirig, all possible configuration, ports,
>both
>> radio, radio 1..... diferent Baudrates... and nothing i can't connect
>the
>> CAT
>>
>> Dates is Fisical Ports RS-232 (9Pins)
>>
>> COM Port1 for CAT (DTR) and PTT (RTS)
>> COM Por2 only CW (DTR)
>>
>> 9600 8N1 Address is 58H (Default and Fine work on all softwares)
>>
>> I configure the Omnirig  with all version of 706 = on DXL
>> I Configure DXL with all version of 706
>>
>> I configure COm1 with PTT, Without PTT, Radio1, Both...
>>
>> With this configuration i testing all baudrates (too modify in TRX)
>>
>> Test in: Wintest, RadioGes, Logger32, VQLog, N1MM Logger, HRD Log,
>> Mixw.... in all work fine, i haven't problem, in TRX, Interface or
>any wire
>> or COM port, inclusive the same configuration in all software.
>>
>>
>>
>---------------------------------------------------------------------------------------------
>>
>> J. Alfonso Navas - EC7AKV (AkA ED7T - EF7T)
>> Correo E-mail ec7akv at gmail.com
>> Tlf: 655.075.252
>>
>> *Cláusula de Confidencialidad:* Este mensaje, y en su caso, cualquier
>> fichero anexo al mismo, puede contener información confidencial o
>> legalmente protegida (LOPD 15/1999 de 13 de Diciembre), siendo para
>uso
>> exclusivo del destinatario. No hay renuncia a la confidencialidad o
>secreto
>> profesional por cualquier transmisión defectuosa o errónea, y queda
>> expresamente prohibida su divulgación, copia o distribución a
>terceros sin
>> la autorización expresa del remitente. Si ha recibido este mensaje
>por
>> error, se ruega lo notifique al remitente enviando un mensaje al
>correo
>> electrónico ec7akv at gmail.com y proceda inmediatamente al borrado del
>> mensaje original y de todas sus copias.
>>
>> Gracias por su colaboración.
>> Siempre mirando por el Medio Ambiente, NO imprima este correo si no
>es
>> necesario.
>> NOTA: Los acentos han sido omitidos de forma intencionada.
>>
>>  ----- Original Message -----
>> *From:* 9A5K <9a5k at 9a5k.com>
>> *To:* rin JG1VGX <jg1vgx at jarl.com>
>> *Cc:* Bob Wilson, N6TV <n6tv at arrl.net> ; DXLog.net
>Reflector<support at dxlog.net>
>> *Sent:* Friday, October 04, 2013 8:21 PM
>> *Subject:* Re: [DXLog.net - Support] Failure CAT
>>
>> Hi again.
>>
>> Just to inform you that solution is found. There is a method in
>> System.Runtime.InteropServices on Marshal class called:
>ReleaseComObject.
>> :-)
>>
>> So, in the code this one needs to be called before closing the
>object.
>>
>> Checked in task manager, everything seems fine now.
>>
>> That will be OK in release 2.0.18.
>>
>> 73,
>> 9A5K
>>
>>
>>
>> On Fri, Oct 4, 2013 at 7:57 PM, 9A5K <9a5k at 9a5k.com> wrote:
>>
>> > Hi all.
>> >
>> > I will check OmniRig documentation once again, object somehow stays
>> active
>> > even there is no dispose method on it so I can't
>> > kill it on that way from application.
>> >
>> > QRX.
>> >
>> >
>> >
>> >
>> >
>> > On Fri, Oct 4, 2013 at 7:54 PM, rin JG1VGX <jg1vgx at jarl.com> wrote:
>> >
>> >> Sorry no, I can't now test with Omni-Rig because it's not working
>in
>> >> my environment.
>> >>
>> >> I also found that if I kill Omni-Rig in Task Manager, the port
>will be
>> >> released and become usable.
>> >>
>> >> 73 rin JG1VGX
>> >>
>> >> On Sat, Oct 5, 2013 at 2:41 AM, Bob Wilson, N6TV <n6tv at arrl.net>
>wrote:
>> >> > Does split mode work properly with FT-450 if you use Omni-Rig?
>> >> >
>> >> > I saw the same issue when using DXLog with Omni-Rig.  Somehow it
>> doesn't
>> >> > release the Omni-rig connection immediately upon exit.  Maybe it
>times
>> >> out
>> >> > after a while.  But if I switch from Omni-rig to "native"
>support,
>> that
>> >> > seems to work immediately, so it is very mysterious how that
>happen if
>> >> > there is no code to release the Omni-Rig connection.
>> >> >
>> >> > 73,
>> >> > Bob, N6TV
>> >> >
>> >> > On Fri, Oct 4, 2013 at 10:29 AM, rin JG1VGX <jg1vgx at jarl.com>
>wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> Today I did a test of CAT via Omni-Rig. Unfortunately it's NOT
>> working.
>> >> >> With exactly the same cable, PC, port settings etc, CAT via
>Omni-Rig
>> >> >> works with other software eg. 5MContest, AATest, but not with
>DXL.
>> >> >> It appears that DXL takes hold of the com port and won't
>release it
>> >> >> properly on exit. To use that virtual COM port with other
>software,
>> >> >> releasing the hold by unplugging the USB adaptor is required.
>> >> >> This phenomenon happens with another rig and a cable as well (I
>> tested
>> >> >> with a Yaesu FT-450).
>> >> >> It's OK for now because at least proprietary CAT works for both
>> radios.
>> >> >>
>> >> >> Another glitch I have found with FT-450 is that the SPLIT
>status is
>> >> >> not handled properly.
>> >> >> FT-450 has only one "split" but DXL somehow has two split
>status, one
>> >> >> each for VFO A and B.
>> >> >> On startup where actually no split is engaged in the rig, DXL
>already
>> >> >> shows split on for A, off for B. If I press SPLIT button on the
>rig
>> >> >> while it's still in VFO A, split is now turned on in VFO B (not
>A) in
>> >> >> DXL. Apparently something is messed up in the code. Please put
>this
>> >> >> also into the list.
>> >> >>
>> >> >> Will try to break some more in the weekend ;-)
>> >> >>
>> >> >> 73 rin JG1VGX
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Thu, Oct 3, 2013 at 11:03 PM, rin JG1VGX <jg1vgx at jarl.com>
>wrote:
>> >> >> > Did a quick test while driving back home.
>> >> >> >
>> >> >> > Now DXL rocks!!! The version 2.0.17 takes freq and mode
>flawlessly
>> >> >> > with either CI-V Transceive off or on.
>> >> >> >
>> >> >> > I chose proprietary rig control, but forgot to check through
>> >> Omni-Rig.
>> >> >> > Maybe later in the weekend. IC-706mk2, 9600 8N1, with a
>> >> >> > less-than-ideal obscure USB-Serial cable, Win7 64bit
>Japanese.
>> >> >> >
>> >> >> > Domo arigato!
>> >> >> > 73 rin JG1VGX
>> >> >> >
>> >> >> >
>> >> >> > On Thu, Oct 3, 2013 at 9:56 AM, rin JG1VGX <jg1vgx at jarl.com>
>> wrote:
>> >> >> >> Chris,
>> >> >> >> Thanks for all your effort. I'm glad to hear the problem was
>now
>> >> >> tracked down.
>> >> >> >> I'll test with new version later this week.
>> >> >> >>
>> >> >> >> Bob,
>> >> >> >> Thanks for comprehensive instructions. I hope I've followed
>them
>> >> >> >> correctly. I picked IC-7000 (hex 70h) because it's easy to
>> remember.
>> >> >> >> You addressed all points we need to check in case of CAT
>> problems. I
>> >> >> >> should have switched on and off CI-V Transceive to see if
>that
>> >> >> >> matters.
>> >> >> >> As to USB-Serial, I used all varieties including FTDI and
>ICOM's
>> >> >> >> built-in (Silicon Labs), but not legacy DB9 because I
>operate
>> mobile
>> >> >> >> with a laptop. I don't want to imagine being with a tower PC
>in a
>> >> >> >> car!!
>> >> >> >>
>> >> >> >> 73 rin JG1VGX
>> >> >> >>
>> >> >> >>
>> >> >> >> On Thu, Oct 3, 2013 at 7:21 AM, 9A5K <9a5k at 9a5k.com> wrote:
>> >> >> >>> Huh...
>> >> >> >>>
>> >> >> >>> I've got it working now in debug version..
>> >> >> >>> Because CI-V transceive was always turned on here, I didn't
>> notice
>> >> the
>> >> >> >>> problem.
>> >> >> >>>
>> >> >> >>> So, just short explanation..
>> >> >> >>>
>> >> >> >>> DXLog in polling process ask radio some information:
>> >> >> >>> VFO A frequency
>> >> >> >>> VFO A mode
>> >> >> >>> VFO B frequency
>> >> >> >>> VFO B mode
>> >> >> >>> Active VFO
>> >> >> >>> Split status..
>> >> >> >>>
>> >> >> >>> Some radios return this info with just one command, other
>needs
>> >> more
>> >> >> >>> commands to get all responses needed.
>> >> >> >>>
>> >> >> >>> Usually, you can query radio in any order to get response,
>or you
>> >> can
>> >> >> post
>> >> >> >>> more commands in a row and then
>> >> >> >>> process responses as they are received from radio.
>> >> >> >>>
>> >> >> >>> With ICOM CI-V protocol, there is a small problem.
>> >> >> >>> When you post a command to radio, it will respond with echo
>of
>> this
>> >> >> command
>> >> >> >>> and after it there will be possible info response,
>> >> >> >>> the actual data you've asked for.
>> >> >> >>> But, if you post more commands in a row, for example ask
>for
>> >> frequency
>> >> >> and
>> >> >> >>> immediately after that ask for mode,
>> >> >> >>> you will get two echos back, first one for frequency,
>second one
>> >> for
>> >> >> mode..
>> >> >> >>> and only one response with data, usually second one (mode).
>> >> >> >>>
>> >>
-- 
Enviado desde mi teléfono con K-9 Mail.


More information about the Support mailing list