janbredenbeek wrote: ↑Sun Oct 15, 2023 11:23 am
Device I/O is controlled by the scheduler loop which executes at least every 20 ms if the machine is in user mode.
Hmmm... if that leads to just one character received per 20 ms, it might explain the problem. But there should be not much CPU load and the loop should run much more frequently.
Are you sure the OS really checks for pending input in the scheduler loop, even if the driver provides no scheduler task?
The scheduler task is provided by the IOSS, so always running. It checks all channels that have pending operations and calls the driver's I/O routine. If this returns OK (or anything apart from 'not complete') the I/O operation is deemed to be finished and a return made from TRAP #3.
Note that on issuing a TRAP #3 the I/O routine is called immediately and only if it returns 'not complete' (and was called with nonzero timeout in D3) the scheduler tasks comes into play.
janbredenbeek wrote: ↑Sun Oct 15, 2023 11:41 am
How much slower is the SERnet receive compared to two Q68s, or a Q68 and a PC?
The QL sending data feels similar as Q68 and the likes. E.g. getting the QL directory from the Q68 with DIR s2_win1_ feels fine.
Receiving looks like slowing down to a few characters per second, e.g. when the QL tries to receive a Q68 directory with DIR s1_win1_.
The best is to try yourself. Definitely not a performance issue as such. Something is utterly wrong.
From the SERnet manual I read that it needs flow control, either by hardware or XON/XOFF. The current driver supports neither (and if it has to be implemented, this has to be on the miniQ68 side). However your observation that there was no overrun puzzles me.
Which version of SERnet are you using, and how are the devices configured?
janbredenbeek wrote: ↑Sun Oct 15, 2023 1:36 pm
From the SERnet manual I read that it needs flow control, either by hardware or XON/XOFF.
This is most likely just to avoid buffer overrun. On Qzero, Q68 and PC I always use SERNET without flow control at 115200 Baud. No problem at all.
janbredenbeek wrote: ↑Sun Oct 15, 2023 1:36 pm
Which version of SERnet are you using, and how are the devices configured?
Can't find the version at the moment. Likely the most recent one. If it is very important, I need to download some versions and compare the binaries.
Configured to SRX1 and STX1, according to your driver.
janbredenbeek wrote: ↑Sun Oct 15, 2023 1:36 pm
Which version of SERnet are you using, and how are the devices configured?
Can't find the version at the moment. Likely the most recent one. If it is very important, I need to download some versions and compare the binaries.
Configured to SRX1 and STX1, according to your driver.
I believe the latest version is v2.25 (see JOBS command after starting SERnet). There is also a v3.01 without any documentation, which has different commands and doesn't allow the serial device to be configured. It also doesn't work on QPC2.
janbredenbeek wrote: ↑Sun Oct 15, 2023 9:34 pm
I believe the latest version is v2.25 (see JOBS command after starting SERnet).
Thanks for the hint. Yes I have version 2.25, too. Did you already find the time to make a serial cable?
I could also make it for you, but afraid of shipping to Netherlands again...
Peter wrote: ↑Sun Oct 15, 2023 10:26 pm
\Thanks for the hint. Yes I have version 2.25, too. Did you already find the time to make a serial cable?
I could also make it for you, but afraid of shipping to Netherlands again...
Plenty of cables here, I just need to find a DB-9 connector (I've had plenty of them, just have to do some searching through piles of cabling stuff...).
BTW, just today I found your cable in the mailbox
Peter wrote: ↑Sun Oct 15, 2023 12:54 pm
The QL sending data feels similar as Q68 and the likes. E.g. getting the QL directory from the Q68 with DIR s2_win1_ feels fine.
Receiving looks like slowing down to a few characters per second, e.g. when the QL tries to receive a Q68 directory with DIR s1_win1_.
The best is to try yourself. Definitely not a performance issue as such. Something is utterly wrong.
Just tested SERnet on QIMSI with both QPC2 and Q68. It works fine in both directions at 115200. From QPC/Q68 to QIMSI is somewhat slower (loading a 32K screen takes 6 or 7 seconds compared to 4 the other way round), but a DIR on the other machine works fine.
I'm using your latest Q68_ROM.SYS file with overrun indicator.
Peter wrote: ↑Mon Oct 16, 2023 6:24 pm
Did you try to receive a directory of Q68's filesystem from the QL side? It crawls extremely here. (More than one page length, SGC, both sides SMSQ/E)
Yes, I did DIR s1_win1_ from the QL where the Q68 was station 1 and the QL station 2.
janbredenbeek wrote: ↑Mon Oct 16, 2023 6:32 pm
Yes, I did DIR s1_win1_ from the QL where the Q68 was station 1 and the QL station 2.
I'm surprised you can not see the same effect. Which hardware and OS are you using on the QL side?
In my case Issue 5 QL motherboard, Minerva ROM, QIMSI, SuperGoldCard running SMSQ/E.
