Posted February 3, 2020 I actually have a serial tool, an AVRT5 APRS amateur radio GPRS tracker. It is made in China and poorly documented. To configure this device there is a Windows software written it seems in visual primary that genuinely sends and reads the configuration by serial port. The device comes with a Prolific USB serial converter. The software turned into no more hard to run below Wine than Windows (both needed downloading DLL and OCX documents and registering them). The problem got here whilst I tried to opposite engineer the configuration protocol. Under Linux ordinarily, that might be easy. I attempted all the standard equipment and a few uncommon ones too. Here are a few examples socat strace slsnif https://linux.Die.Net/man/1/slsnif jpnevulator, http://jpnevulator.Snarl.Nl/ For some of them I made a virtual serial port and mapped that to COM3 on wine. (I also used WireShark that could intercept USB visitors and that worked best however I didn't apprehend the output, perhaps there were a number of manage bytes for the USB now not simply serial data) All had the identical problem (except WireShark). As soon as the sniffer became energetic the config software could not speak with the tool. I could intercept the command "SETUP" coming from the software however the tool did now not reply Then I attempted home windows port sniffer Serial Port Monitor https://www.serial-port-monitor.org/ (unfastened trial version) This said it couldn't find a serial port. So in the end I tried a Windows 7 laptop and Serial Port Monitor labored beautifully. It turned out the config application opened the port on 9600 N81 and despatched simple and obvious ASCII strings with a 0xD 0xA termination. But why should I no longer get it to work below Wine whilst a lot of these techniques work first-rate for everyday Linux programs? Link to comment Share on other sites More sharing options... Link to post Share on other sites More sharing options...
Posted February 3, 2020 20 minutes ago, Fin_Guns said: Wine It's possible that Wine does hardware translation and in the process, moves serial communications to elsewhere, (lets face it, no one uses serial comm any more unless you are running some kind of bespoke hardware, and even then, it's all run bare metal) thus interfering with com port tools. Dunno, I'm not a fan of Wine. Your best bet would be asking at the Wine forums, they'll probably have more info on how their software works NOTE: I no longer frequent this site. If you really need help, PM/DM me and my e.mail will alert me. Link to comment Share on other sites More sharing options... Link to post Share on other sites More sharing options...
Posted February 3, 2020 Author 34 minutes ago, Radium_Angel said: It's possible that Wine does hardware translation and in the process, moves serial communications to elsewhere, (lets face it, no one uses serial comm any more unless you are running some kind of bespoke hardware, and even then, it's all run bare metal) thus interfering with com port tools. Dunno, I'm not a fan of Wine. Your best bet would be asking at the Wine forums, they'll probably have more info on how their software works Thanks for the advice, most likely I will. Link to comment Share on other sites More sharing options... Link to post Share on other sites More sharing options...
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now