Such a tedious and time consuming job.SimSER SRX not working on BBQL
-
vanpeebles
- Commissario Pebbli
- Posts: 2853
- Joined: Sat Nov 20, 2010 7:13 pm
- Location: North East UK
-
martyn_hill
- QL Wafer Drive
- Posts: 1101
- Joined: Sat Oct 25, 2014 9:53 am
Re: SimSER SRX not working on BBQL
...not unlike troubleshooting serial connection problems!
Bit more 'news' from my testing...
My last tests results (using SRX1H would only receive after closing and reopening the channel) haven't resurfaced, although it still doesn't work... I'll park that oddity for now.
This time I used the terrific open-source RealTerm Windows utility to send data to the BBQL, whilst watching the signal lines through the software.
Using the default SER driver (SER1H) showed the expected (HERMES) behaviour for the CTS line - namely not rapidly toggling the moment the port was opened, but only flickering intermittently during transmission. Receiving on the QL at 19k2 happily - no discernable errors.
Loading the SimSER driver and again opening a SER1H channel also works, CTS again toggling as expected (only during transmission) BUT RealTerm showed that the Backspace character was being returned by the QL for every linefeed sent! How odd!
Switching to SRX1H (as needed by SERNET) and no data received at all.
Watching the CTS line, it would go Active upon opening the port as expected, but the moment data is sent, it gets Negated and refuses to toggle any further during the transmission attempt from RealTerm to QL.
Derek - you mentioned something earlier in this thread about SimSER 'directly accessing the IPC' - if this is the case, I'm even more inclined to think that differences between the 8049 (as tested by Derek) and HERMES render the SimSER SRX driver incompatible with HERMES.
I wonder if SimSER's author could be persuaded to share The Source (tm). I'd happily compare against Minerva's default SER driver code.
Thoughts on any of the above?
I'll keep playing in the meantime... Night-night!
Bit more 'news' from my testing...
My last tests results (using SRX1H would only receive after closing and reopening the channel) haven't resurfaced, although it still doesn't work... I'll park that oddity for now.
This time I used the terrific open-source RealTerm Windows utility to send data to the BBQL, whilst watching the signal lines through the software.
Using the default SER driver (SER1H) showed the expected (HERMES) behaviour for the CTS line - namely not rapidly toggling the moment the port was opened, but only flickering intermittently during transmission. Receiving on the QL at 19k2 happily - no discernable errors.
Loading the SimSER driver and again opening a SER1H channel also works, CTS again toggling as expected (only during transmission) BUT RealTerm showed that the Backspace character was being returned by the QL for every linefeed sent! How odd!
Switching to SRX1H (as needed by SERNET) and no data received at all.
Watching the CTS line, it would go Active upon opening the port as expected, but the moment data is sent, it gets Negated and refuses to toggle any further during the transmission attempt from RealTerm to QL.
Derek - you mentioned something earlier in this thread about SimSER 'directly accessing the IPC' - if this is the case, I'm even more inclined to think that differences between the 8049 (as tested by Derek) and HERMES render the SimSER SRX driver incompatible with HERMES.
I wonder if SimSER's author could be persuaded to share The Source (tm). I'd happily compare against Minerva's default SER driver code.
Thoughts on any of the above?
I'll keep playing in the meantime... Night-night!