pcmhacking.net

antus wrote: ↑Fri Jan 19, 2024 9:07 am You're on the right track, you can see the comments around the baud setting, some of the other devices need it, and that is where it is done. If its not on 57600 to add support in the public app you'll need to try more than once and try again after the first failure at a different baud rate for the cable you have, to keep support for the whole family of interfaces. More than 2 seconds is strange, I think that might be the whole init process, setting protocol, figuring out whats on the bus, not just the response to the init command which should be milliseconds. I agree with using a com port sniffer to see what the working tools, as well as pcmhammer where its not logging the init bytes are doing.

When I wrote the original implementation I used this old attached version sudt accessport which works nicely on a 32 bit operating system. I'd recommend win 7 32 bit in a VM. They added a 64bit version of the app later, but its not stable and causes system crashes (as it loads as a driver). So the old one in 32 bit is better. Else there is other similar software around.

antus wrote: ↑Fri Jan 19, 2024 9:07 am You're on the right track, you can see the comments around the baud setting, some of the other devices need it, and that is where it is done. If its not on 57600 to add support in the public app you'll need to try more than once and try again after the first failure at a different baud rate for the cable you have, to keep support for the whole family of interfaces. More than 2 seconds is strange, I think that might be the whole init process, setting protocol, figuring out whats on the bus, not just the response to the init command which should be milliseconds. I agree with using a com port sniffer to see what the working tools, as well as pcmhammer where its not logging the init bytes are doing.

When I wrote the original implementation I used this old attached version sudt accessport which works nicely on a 32 bit operating system. I'd recommend win 7 32 bit in a VM. They added a 64bit version of the app later, but its not stable and causes system crashes (as it loads as a driver). So the old one in 32 bit is better. Else there is other similar software around.

antus wrote: ↑Sat Jan 20, 2024 11:44 am Set it up something like this, and then start monitoring. I havn't used it for a while and don't have an interface on this pc, but from memory the order of when you start monitoring and start using the port matters. If it doesn't work monitoring before starting the other app, do it the other way around. You might have to try it a couple of ways. Its possible the latest FTDI drivers don't work on XP. It'd be general windows trouble shooting to see if the interface is working, and there might be something specific to whatever VM software you are using, if you are using a VM.