|
After upgrading to Ubuntu 14.04 and latest Wine I am able to run Winmor TNC in Wine. Program come up and I can telnet to it using: telnet localhost 8500 Testing some command grom Winmor documentation give correcto result Issuing a CONNECT command show a connection trial and apparently correct sound. Now is time to program a wl2kwinmor command. Is someone in group able to do it? Regards Franco Spinelli IW2DHW |
|
On 02 Sep 2014 12:33:01 -0700
"frspin@... [paclink-unix]" <paclink-unix@...> wrote: After upgrading to Ubuntu 14.04 and latest Wine I am able to runInteresting idea. Not sure what the WinmorTNC expects, AX.25 packets? I have a kernel socket interface to the bottom of the AX.25 protocol stack for my UDR radio dev work which might work for connecting to a Winmor TNC. In case anyone is going to DCC in Austin, TX this weekend let's try & meet up & eat, drink & talk some. /Basil n7nix |
|
---In paclink-unix@..., <wa7nwp@...> wrote : >> Should work in LinBPQ... As in my post to BPQ32 group, LinBPQ installed on same machine give this error message: Connect Failed for WINMOR Data socket Port 1 - error code = 111 And RMS Express, also installed with Wine, don't find any COM port for rig control..... Winmor TNC control protocol is available on Internet and from Winmor author. Winmor binary data is undocumented (i suppose) but available from Winmor author Regards Franco Spinelli IW2DHW |
|
I need to correct this post
toggle quoted message
Show quoted text
Linbpq author have corrected software and now Linbpq is working with Winmor TNC. What is needed now is a connection from paclink-unix to Winmor TNC or to Linbpq Regards Franco Spinelli IW2DHW ---In paclink-unix@..., <frspin@...> wrote : ---In paclink-unix@..., <wa7nwp@...> wrote : > Should work in LinBPQ... |
|
On Thu, 2014-09-04 at 12:42 -0700, frspin@... [paclink-unix]
wrote: Hi Franco, I have looked at this before. As far as I understand it, there are really two parts to using Winmor. Of course, there is the Winmor modem which you have gotten to work under Wine. The second part is the proper protocol which follows the state machine shown in Rick's specification. It is not like AX.25. I think in order to make this work, the state machine has to be implemented. 73, -- Dana, KA1WPM |
|
---In paclink-unix@..., <ka1wpm@...> wrote : >Hi Franco, >I have looked at this before. As far as I understand it, there are >really two parts to using Winmor. Of course, there is the Winmor modem >which you have gotten to work under Wine. The second part is the proper >protocol which follows the state machine shown in Rick's specification. >It is not like AX.25. I think in order to make this work, the state >machine has to be implemented. I don't know if state machine is compatible with paclink. It is not AX.25. I can use Winmor TNC using Telnet and TNC send on control port (8500) PTT True, PTT False for PTT control , BUSY True or False and other info for program using TNC. WIthout an interface between Airmail and LinBPQ I am not able to do a real connect and see (with Wireshark) dialog on Winmor TNC data port (8501). For now I can see that a connect request from Telnet or BPQ terminal goes to control port and TNC try a connection. But LinBPQ use Winmor TNC, so have implemented this state machine. Any tip on more test I can do? Regards Franco Spinelli IW2DHW |
Basil Gunn