Yeah, those are my old settings.
I put it back to those, and then connected via.
C184.108.40.206/9640 fills the screen with garbage.
Camera Capture Compressed as it was huge.
Edited by slinkeey, Tue Apr 4, 2017 7:57 PM.
Jump to content
Posted Wed Apr 5, 2017 1:08 PM
The last time I used my UDS-10 (and it was a while ago) I remember that Stuart & InsaneMultitasker got on the same page and made it so the same settings could be used for both the browser and TIMXT. When I checked mine a couple of minutes ago, I noticed the settings are slightly different from you folks.
Of course if you use a modem... ignore this post.
With the D4 connection mode is really what keys it off (if i recall) to be compatible between TIMXT and Stuarts browser. Of course you do not see anything echoed i believe when using this mode. I use the D6 as the old school method of ATDT works and I can see what I type..
Posted Wed Apr 5, 2017 9:05 PM
Yeah weird that stuart's browser works perfectly..I did switch from D4 to D6 in order to use legacy hayes commands, as it is easy to toggle back to D4, for the browser.
I just get jumbled junk. Does the nano need a lower baud rate? I lowered UDS-10 to 9600. I am wondering if my cable is wrong..
Mine is like the NanoPEB layout.
Edited by slinkeey, Wed Apr 5, 2017 9:27 PM.
Posted Wed Apr 5, 2017 9:56 PM
If you set the connection type for modem, and use the ATDT commands, are the characters echoed properly?
Are you using a standard, unmodified console? (edit: besides the F18A, that is)
Edited by InsaneMultitasker, Wed Apr 5, 2017 9:56 PM.
Posted Wed Apr 5, 2017 9:58 PM
Yep, the chars are echoed properly.
Typing [ATDT220.127.116.11,9640] shows up as [ATDT18.104.22.168,9640] on my screen.
My Console has a Speech Synth, F18, and NanoPEB.... That's it.
That's a good point. If it is echoing back, then we know the terminal is interpreting what the UDS-10 is sending.
Edited by slinkeey, Wed Apr 5, 2017 10:00 PM.
Posted Wed Apr 5, 2017 10:01 PM
If your console crystal speed was different than most, the ATDT string would not echo back properly.
The cable appears to be working properly.
Are you able to telnet to the address via a PC?
Posted Wed Apr 5, 2017 10:03 PM
Yep, no problem.
Heat Wave BBS
Posted Wed Apr 5, 2017 10:55 PM
have you trtied to lower your baudrate on the UDS device as well as in TIMXT just to rule out anything else, say lower to 9600 if still bad go down to 2400, still bad then it has to be something else.
Possible issue with the RS232 card you are using. Maybe it's flaked out ?
Edited by Shift838, Wed Apr 5, 2017 10:55 PM.
Posted Wed Apr 5, 2017 11:06 PM
I lowered them both to 9600.
I wouldn't think that the web browser would be more forgiving to problems.. I will mess with it later... Thanks
Posted Wed Apr 5, 2017 11:13 PM
After updating to v1.8, it looks much better... Just need to figure out how to get the UDS to respond. I know that the terminals does recognize the serial port. When I toggle the power on the UDS, I get some symbols on the screen.
if the baudrate, parity and stop bits are set to 19200b[s 8N1 on TIMXT and the UDS is set the same with a D6 connection type you should see 'NO CARRIER' come up wihen powered on.
Posted Thu Apr 6, 2017 11:34 AM
See if you can connect to any other telnet BBSs. What firmware revision and model are you using (i.e., UDS-10-IAP)?
Posted Thu Apr 6, 2017 4:43 PM
I kept dropping the speed, and it would get a little better with each drop.
2400 baud works great.
UDS-10-IAP Rev B20
I will need to lookup the firmware..
Posted Thu Apr 6, 2017 5:26 PM
Once you've checked your firmware, just for giggles, we should check your TI clock speed.
From Thierry's website : "Fortunately, the clock speed is specified in the console ROM, at byte >000C: if this byte is >30 the console has a 3 MHz clock, if it's >28 the clock is 2.5 MHz."
We can check this somewhat easily from Extended BASIC. Type the following three lines:
100 CALL INIT
120 CALL PEEK(12,A)::PRINT A
If the program prints 48, you have a 3.0Mhz clock; if it prints 40, you have a 2.5Mhz clock. TIMXT is only configured for the common 3.0Mhz clock.
Posted Thu Apr 6, 2017 5:51 PM
Software version 05.2 (031113) LTX
The program yielded 48
Maybe something related to my NanoPEB?
Edited by slinkeey, Thu Apr 6, 2017 6:23 PM.
Posted Tue Apr 11, 2017 10:51 AM
Posted Tue Apr 11, 2017 11:00 AM
Known 2400 Baud limitation? If so, that's cool. I'll know to stop goofing with higher rates.
38.4K is the current limit. I know of at least two nanopeb users, three including myself, who are using TIMXT at this speed. It feels like we are missing something obvious, since Stuart's browser is working properly at the same speed. I just don't know what that might be...
Posted Tue Apr 11, 2017 10:47 PM
Posted Wed Apr 12, 2017 5:32 AM
Off topic, but for some reason, I cannot get over 1200 BAUD via Telco and my 56k US Robotics modem.
Do you have an old fashion analog line or a VoIP one? VoIP doesn't play well with modems or faxes.
0 members, 0 guests, 0 anonymous users