Yeah, RAM is the issue in there, isn't it. They intercept the "--" prefix from the Nuvi's FMI mode, but that's all FMI support code. Inspecting the KISS packets for a message and then locating the recipient call and then matching against MYCALL might be asking for too much.
Oh well, someday I'll remember to ask that a single dash followed by a space from the FMI mode sends a message to the station that last sent one to me. If you leave off the dash altogether, it sends to the last station sent to. A single dash followed by a callsign sends to that call. I'd like a single dash with space to be "send to the person that last sent to me" to avoid needing to remember the call and key it to start a QSO. After the first one, of course, the call would be remembered so not even a dash would be required to send to the last station I sent to. Lynn (D) - KJ4ERJ Fred Hillhouse wrote: > > > Hi Lynn, > > In theory, you can send the escape KISS command, the OT2 command and > then follow up with "AMODE KISS" to re-enter normal operations. You > may need to do a simple test to make sure the OT2 is not in KISS. > > One of the reasons I requested a TERMINAL option in APRSIS32 was so I > would not have to exit APRSIS32, start Hyper Terminal, etc. > > Parsing out a possible command sequence appears to be straight forward > on the GPS port. On the KISS port, I think there is the issue of a > character sequence that could be real data. I am not too sure about > that though. > > Hmm, thinking about the overall scheme, I suspect the APRS data from a > PC currently goes straight to the APRS engine for sending. IT I have > your thoughts correct, if a message sent from APRSIS32 to an local > callsign-ssid, such as N7FMH-T2, a simple check for "T2" would > intercept the command. I bet it requires some of that valuable RAM. > > Best regards, > Fred > > > > > ------------------------------------------------------------------------ > *From:* [email protected] [mailto:[email protected]] > *On Behalf Of *Lynn W. Deffenbaugh (Mr) > *Sent:* Wednesday, July 28, 2010 15:07 > *To:* [email protected] > *Subject:* Re: [tracker2] OT2m Commands via KISS? > > > > But wouldn't just sending APRS messages to the OT2m be so cool? I > know > I like being able to re-configure from the Nuvi, why not via KISS? > > Lynn (D) - KJ4ERJ > > Fred Hillhouse wrote: > > > > > > Hi Lynn, > > > > I had to exit KISS to send commands, then re-enter KISS when I was > > using the PDA. I continue to do the same with APRSIS32 as well. > > > > Best regards, > > Fred > > > > > > > > ---------------------------------------------------------- > > *From:* [email protected] > <mailto:tracker2%40yahoogroups.com> > [mailto:[email protected] <mailto:tracker2%40yahoogroups.com>] > > *On Behalf Of *Lynn W. Deffenbaugh (Mr) > > *Sent:* Wednesday, July 28, 2010 14:37 > > *To:* [email protected] <mailto:tracker2%40yahoogroups.com> > > *Subject:* Re: [tracker2] OT2m Commands via KISS? > > > > > > > > I don't know if it's supposed to work, but it doesn't. The first two > > command methods work, but commands via KISSed APRS message don't. > > > > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 > > > > Lynn W. Deffenbaugh (Mr) wrote: > > > Short question: Can I send an OT2m commands via APRS message > > directly > > > into a KISS port? > > > > > > Longer description: I have an OT2m connected to a Nuvi 350 on > > port B > > > (BMODE GARMIN) and a PC connected on port A (AMODE KISS). I know > > I can > > > send commands from the Nuvi (via "--info" for instance) and via > > APRS > > > messaging over RF ("cmd info" as an APRS message). > > > > > > If I send an APRS message into the OT2m via the KISS port, > > addressing > > > the OT2m's callsign with a body of "cmd info", will it send a > > response > > > back or would the message have to be transmitted and heard back > > from a > > > digipeater? > > > > > > This is all assuming that the KISS-originated message actually > > comes > > > from an authorized callsign just like the same command via RF. > > > > > > Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and > Win32 > > > (and hoping that I can send commands to the OT2m from that > software) > > > > > > > > > > > > > > > > > >
