• Please review our updated Terms and Rules here

WIFI232 with LCOMM in LDOS 5.1.3

wheagy

Experienced Member
Joined
Apr 10, 2010
Messages
101
Hi,

I have a WIFI232 that I'm trying to get working with my TRS-80 Model 1. I have the serial board in the EI and level II. For the most part, I think everything is working ok. After messing with LDOS 5.3.1 for a day and finally discovering that when you load the RS232R driver in LDOS 5.3.1, that it actually loads the RS232T driver, I sourced a copy of LDOS 5.1.3. (Found this in a forum...maybe here) That loads the proper RS232R driver and I'm able to display the startup message from the WIFI232 after a WIFI232 reset.

Once the driver was correct, the TRS-80 started receiving data from the wifi232 right away. However, for some reason I can't send commands from the TRS-80 to the WIFI232. If I enter ATI, it seems to accept it, but nothing happens. If I go to the wifi232 web server, I can issue commands from there and connect to BBSs, and after I connect, I can type commands from the TRS-80 and it seems to work.

Here's what I figured so far that is necessary to configure the model 1 and start LCOMM for serial comm through the WIFI232 at 300 baud:
SET *KI TO KI/DVR
SET *CL TO RS232R/DVR B=300,P=OFF,S=1,W=8
LCOMM *CL
My guess is that somewhere in there, there is some configuration that isn't quite right. There's a bunch of LCOMM things you can configure after it starts up that might be an issue too, but I tried a number of things. Once in LCOMM, I also set for 8-bit.

Anyone have any idea why I might be seeing this behavior? You can see some screen shots here that show that the WIFI232 startup is being displayed, and after I connect to a BBS using the WIFI232 web server, I can enter commands directly from the TRS-80, but if I try to send commands to the WIFI232, nothing happens.

http://imgur.com/a/IADY3

Thanks,

Win
 
Its reminding me of my fun with getting tcpser working on my raspberry pi. Its really CTS/RTS/DTR that is the challenge to get right with these emulators. Also ECHO needs to be right on the modem end. ATE0 or ATE1. I think they need +++ATE1 to turn it on, tcpser I set all of that on the command line so I don't have to program it.

I looked at that and thought about it, but since I can hang four off my PI I just went that route instead.

Fiddle with the CTS/RTS/DTR jumpers and make sure everything is in sync. Remember it does not support CD.

Also, be sure your serial port is working. I've run into 9 out of 10 that are dead and need a 1488 or 1489 replaced. One I needed just about the whole circuit replaced.
 
Back
Top