Downloading problems with WiModem 232 and a UDS-10
So, it turns out that the latest Espressif core has a known issue accessing the time server under some WiFi circumstances. We need the latest core, so I am looking at some other options for working around this until it is fixed.
Reply
Oh, hey - missed this post somehow...

So there's a potential explanation for what's going on with my UTC problem, eh?

Cool - thanks for looking into it, appreciated. Smile
Reply
The issues with the Espressif core was fixed and is part of the v5.10 of the WiModem232 firmware.
Reply
Okay, thanks.

Well, I tried checking IP addresses this morning (hadn't really fooled with this since the last time I posted),
and the IP address list given by ATI5 was there, but with that funky timestamp. AT*TIME was also showing
that weird time format.

So I did the usual AT*NET= dance, switching from static to DHCP and once I did that, it shows the correct
time now. So I switched back but this time it's still showing the correct time. Go figure. That didn't work the
last time I tried it but it seems to be working okay now.

One other thing and this is odd to me...when I switch from STATIC to DHCP then back to STATIC it totally
clears the ATI5 listing. Blank. Nada, after that. (no power off involved).

Thanks and hope you had a great Christmas! Smile
Reply
I will take a look at that. It should clear the data for ATI5, but it still should show *something*.
Reply
Nope, goes to a totally blank field, just like if you powered the WiModem232 completely off.

Gotta say, loving the ATI5 and correct time stamp combo.

Here, with my Mega ST4, I open up STalker which allows you access to your drop-down ACC's,
(desk accessories) and do an ATI5. Then I use the Editress, an ACC text editor, to pull up my
caller log and directly match it up against the list from ATI5 in real time. Very cool and very handy
for getting what you need to ban the 'bots.

That sounds like something from I, Robot - Ban the 'Bots! Maybe we can start a meme... Smile
Reply
LOL! Smile
Reply
Okay, still got a few downloading issues so I thought I'd run them past you.

I honestly don't think it's a WiModem232 problem at all but I was hoping that
maybe you could shed some light on what's happening.

Callers can login to my BBS at 19.2k and the downloads are flawless. Anyone
who calls in less than that, it errors out. So I setup my Atari STacy at 9600
baud with its' WiModem232 and it also errored out. I checked the buffer using
the ATI3 command - it said YES (attaching screenshot).

So I took the BBS down and checked the WiModem232 there, also checking the
buffer and it said NO (screenshot attached again).

Any idea, thought, random or otherwise Smile as to why it won't work correctly at
anything other than 19.2k speeds? I realize this is a bit vague.

Thanks.

   


   
Reply
Oh, just thought I'd mention - this is using Zmodem. If I switch
to Xmodem, or Xmodem-1k, the downloads work at the slower
speeds.

Thanks.
Reply
Baud rates have to be same always. Zmodem bases its timing windows on the baud rate, so it is not surprising you would have a problem.
Reply




Users browsing this thread: 2 Guest(s)