Personally, I feel like it is working, just from the mods behavior.
Just gotta figure out the software end of it...
PS I wish I could find someone who has a working RSVE mod in
place and using it!
sporniket wrote: Thu Dec 08, 2022 8:20 am Here is a draft of a little guide to install the assembled rsve into the ST. Or more like "which MFP pin is wired to which point of the RSVE".
rsve-quick-install-guide--draft.pdf
I don't intend to be thorough but if you feel that a little clarification would be helpfull here and there, I am happy to amend this guide.
I totally missed that somehow. Very good PDF and clear instruction. I just tried pointing out that I think Darklord have installed his RSVE wrong? I might be mistaken though. I would like it to be working so that I can built one myself and try out.sporniket wrote: Fri Jan 06, 2023 12:05 pm @DoG thanks for the insights. I also previously wrote an installation guide (that's the one in the picture from @exxos, and @Darklord received it too) that details which wire goes to which pins. The mod is indeed wired to 2 signal pins on the MFP (Timer D out, Receiver Clock), plus the power supply (vcc + gnd), making 4 pins in total.
I've been using RTS/CTS on for a long time now. From way back when I got my first Lantronix UDS10 to theDoG wrote: Fri Jan 06, 2023 11:47 am
RTS/CTS-handshake is apparently need to be turned on in your software. Try selecting 110 baud to get 38400?
Some ideas.Darklord wrote: Fri Jan 06, 2023 3:58 am HSModem is supposed to be re-mapping all 19200 speeds to 38400 automatically, if I've
got the settings right.
The problem is, it appears that there is no communication between the RSVE equipped
Mega ST4 and the WiModem232 I use. I set the WiModem232 to 38400 and once I do that,
with the HSModem software set to RSVE aware, I can't access the WiModem232 from any
terminal software like TAZ, STalker, etc,...
Normally, if everything is working right, you can access the WiModem232 directly from a
comms package. Typing in ATI gives some basic info, AT&V will show the settings, AT*N
will scan for all available networks, etc. I can not get a prompt from any comms software
when the RSVE mod is turned on via HSModem. I can get the prompt and issue those commands
if I re-run the HSModem software and turn the RSVE part off (and the WiModem is set back to
19200).
I tried calling in with SyncTerm on a Win10 box and while the WiModem232 flashed the
"Incoming Call" message, the RSVE equipped Mega ST4, with my BBS software running,
never acknowledges/answers that call.
I tried running a bare AUTO folder with nothing but DRIVN.PRG andd MFP.PRG in it but
that didn't change anything.
I also disabled the SERIAL.CPX but that didn't make a difference either. I could not tell
from the documentation if the SERIAL.CPX was supposed to be left in place or not. I did
try it both ways.
Code: Select all
HSMODEM1 (compatibility)
------------------------
These drivers replace HSMODEM1. The BIOS function calls for MODEM1 are a
little bit slower than those in HSMODEM1, because of the support for
several interfaces. Those of you who use an old program together with the
last version (HSMOD105.LZH) of HSMODEM1 need not "update" to this version.
Code: Select all
Speeder-Recognition (RSVE, RSVECHIP amongst others)
---------------------------------------------------
The driver tries to automatically recognize if a interface accelerator is
installed. The result of its recognition will be displayed during
installation, currently in the third line directly under the "(C)...".
However this is not an intensive MFP UART test, so a faulty MFP or faulty
connections are not neccesarily recognised, or can lead to output of
messages other than "...defective???".
Here follows the possible displays:
"MFP-UART defective???"
"MFP without additions."
"Fixed speedup or Analog PLL."
"RSVE or compatible found."
Presumably it has a RSVE or RSSPEED or a compatible Baud rate changer
installed. The test at 1200 bps ran normally, 110 bps was however
strongly accelerated.
"RSVECHIP found."
I've not tried with the Lantronix. The WiModem232 is in operation right now with DarkForce!, so it is working.TheNameOfTheGame wrote: Fri Jan 06, 2023 11:47 pm
Some ideas.
Did you try with the Lantronix to make sure it is not a problem with WiModem232?
Do you have a null modem cable you can connect the Atari to a PC/MAC to test with to elimate the WinModem/Lantronix variable?
What about an older version of HSModem? The README says this:
Try with 110 baud (normal HSMODEM 38400 baud target) and virgin MFP.TOS with a program that accepts it (you said your BBS only goes to 300)?Code: Select all
HSMODEM1 (compatibility) ------------------------ These drivers replace HSMODEM1. The BIOS function calls for MODEM1 are a little bit slower than those in HSMODEM1, because of the support for several interfaces. Those of you who use an old program together with the last version (HSMOD105.LZH) of HSMODEM1 need not "update" to this version.
Try with FASTINT off to see if any communication is possible?
CoNnect supposedly provides native support for RSVE. Maybe try that as a terminal program when testing?
Just a few ideas after considering the effects you are seeing.