03-03-2023, 06:23 AM
(This post was last modified: 03-03-2023, 06:26 AM by Bungo Pony.)
(03-01-2023, 08:22 PM)admin Wrote: You stated you have a WiModem232, not a WiModem. What you show is a C64 screen with the WiModem's display. Whatever you are using for a terminal program, it is in a PETSCII mode instead of an ASCII mode. How can I tell?... the character case is reversed (upper and lower case characters are backwards). An ASCII mode is *required* while entering the router's name and password... no exceptions.
Update... I got it working. The C64 has two sets of alpha-numeric characters, and the shifted characters use a set that looks fine to the C64, but looks like a completely different character set to the WiModem. When it echoes back, it looks fine on the C64. I offset the shifted characters to the proper character set which PCs understand, and I was able to catch the WiModem in a happy moment where it was willing to connect.
The flakiness of the WiModem has made this an absolute time-consuming nightmare to debug, especially when it won't connect using either the C64 nor the PC on the same bench. The only thing that clued me in is that it absolutely never connected with the SSID command from the C64. Narrowing that down sooner would have saved me a lot of headache and time.
Anyway, here's a picture of it working. As you can see, the case is still inverted. But now that I actually have Crapterm communicating properly with the WiModem, I can write routines to fix the inverted case and resume working on the software I was writing to interface with it.
image