This question has come up several times. As I understand it, the file interface only supports the following interface. · LINE 1 = Main VFO Frequency in Mhz, with a single decimal point. &middo
Tom, The file interface as I understand it is a way to get N1MM to run through the N4PY software and control the Orion. There is another interface called the N4PY interface that could be used as well
<snip> I would suggest that an even better way to interface N1MM with Carl's sofware would be to use a programing API. This is how the interface between Carl's software and WriteLog is done. It avoid
<I would suggest that an even better way to interface N1MM with Carl's software would be to use a programing API...... Duane Works for me. As to the programming interface standardization, I agree wit
It's a shame that somebody (not me) hasn't defined an interchange specification between the types of software that we use. Some use DDE on Windows, others N4PY's virtual COM port solution. A common g
Agree, though it should be complicated enough to be able to accomodate things like you've described below and much more. Yupp. And integration with SSTV/PSK/RTTY/WSJT etc. etc. types programs as well
One way to send messages from one program to another is to use the LAN protocol with socket connections. This method is very fast and allows messages to be sent between any two programs residing on t
Author: "David W LeJeune, Sr" <lejeuned@centurytel.net>
Date: Fri, 1 Oct 2004 06:38:04 -0500
That would be a neat idea, Carl. Would complement some of the stuff I've been working on in terms of remote access. Your memory resident interface works fine, but is a bit slow, for what I want to do
I'd go out and buy another Pegasus to replace the one I sold last year, just to play with that feature if it were available Carl. Gary, AA2IZ I interface _____________________________________________