15547Re: [tracker2] Re: Tracker3 / OT3m - next steps for a new owner (after the manual)?
- May 9, 2013You get the same no-op effect if you use a Simply(KISS) port which is
recommended for devices that can be locked into KISS mode like the
USBKISS port on the T3. The (original) KISS mode in APRSISCE/32 will
automatically provide Kenwood-type open and close commands which will
drop the Tracker2 family ports out of KISS mode when APRSISCE/32 is closed.
I'm glad you figured that out and apologize for having been away from
e-mail for a while. Only about 200 more unread messages to go.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 5/8/2013 3:57 PM, Willie M wrote:
> Hi James, I have traffic passing between the tracker and the PC now. The
> root of the problem was the port setup performed by APRSISCE/32,
> specifically the OpenCmd and CloseCmd which were interfering with the
> tracker's functioning in KISS mode. I solved it by setting the tracker's
> mode to be USBKISS with the Windows config program, so no further config
> was needed for the module to function, then I manually edited the XML
> config for APRSISCE/32 and remove the configuration steps of the open and
> close - basically deleting all but one OpenCmd and CloseCmd, which I set to
> be the null commands (it's mentioned in the APRSISCE/32 wiki).
> If anyone is interested, the resulting XML for my serial port (it's the
> USBKISS one) is below. The USB port has already been set to USBKISS, so on
> power-up / attachment to the PC, you don't need to do any further config of
> the port.
> <RFPort Name="OT3m">
> Thanks for your help,
> Willie . AC0UK
> On Mon, May 6, 2013 at 7:22 PM, James Ewen <ve6srv@...> wrote:
>> On Mon, May 6, 2013 at 9:52 AM, wmacris <wmacris@...> wrote:
>>>> How are you enabling USBKISS on the OT3?
>>> COM7, and enabled it using two different methods at different times.
>> First tried
>>> USBKISS checkbox in GUI. Then after no progress in the APRS program,
>>> in over console, did some debugging (eg look at settings, watch packets
>>> in, etc), re-enabled it via commandline and tried again.
>> Okay, so after you enabled USBKISS, you shut down OTWINCFG, and or
>> your terminal program, and then connected with APRSISCE/32? DId you
>> get any errors in the port log?
>> Yahoo! Groups Links
> Yahoo! Groups Links
- << Previous post in topic Next post in topic >>