manterola

I used my xm301 (once) with google voice thru a voip obihai adapter. It worked perfectly, modems might not work at higher speeds, but 300 baud should work thru VOIP. I also got a 830 , clean it and that 's it , I still need to get a power supply and a Bell telephone to try it.

I guess Ctrl j have some special purpose in Plato, that's why Ctrl j doesn't reach the esp-01. Try to get rid of the original firmware, install something else that recognize "Return".

I have a question regarding Plato latest version: I guess you need to load the handler thru DOS menú first, then after that (L)oad the Plato binary...right? I tried to load the Rverter handler and it loaded but it got stuck there, it never returned to the DOS menu. Then I turned off the computer and I tried loading Plato first, but I couldn't find a way to load the handler later from inside Plato program. Latest version, Plato alpha, worked perfectly, btw.

So lucky! Got this from a Chilean guy in Concepción: a XC11! I saw one when 10 y.o. and never again. Now I need to figure out how to bring the lot to USA. Or at least the cassette recorder.

Dropcheck: See? Return and then Ctrl j makes the trick! Congrats! These esp-01 are a bit tricky, but they work. BTW, you didnt do the AT+CIPMODE=1 so you got that IPD stuff. Follow the sequence posted. Now regarding questions about how to get connected using the original firmware: Check the thread, I already posted a list of commands I used to get connected to vintagebbs. edit: Here it is again: AT+GMR AT+CWMODE=1 AT+CIFSR AT+CWJAP_DEF="replace with wifi name","replace with password" AT+CWAUTOCONN=1 AT+UART_DEF? AT+UART_DEF=9600,8,1,0,0 set comm params AT+CIPMODE=1 transparent mode or everything get ipd prefix AT+CIPMUX=0 no multiplexing AT+CIPSTART="TCP","vintagebbsing.com",2325 this is one example AT+CIPSEND to start sending your stuff to the server Then I realized that getting connected using the original firmware is cumbersome. So I put another firmware. Stefan is also using another firmware. The coolest part is getting Plato alpha version working. It is amazing piece of software, but that is later.

If you make the Zimodem firmware work, the one I posted, you should try to connect @2400 baud rate. That the default. You can change it to your favorite value later

That strange baud rate is 74800 or something like that. I wrote about it already in this thread. It is the "native" low level baud rate if the esp-01. Put it in programming mode again and flash it again (at any baud rate, like 115k or 9600, it doesn't matter). Dropcheck, you already made it: you got echo, and could listen the high pitch sound. The only thing you have to do is to figure out how to make the module (with original firmware) to recognize the "enter". I almost sure you just need to write a valid command and then press return and then press Ctrl j. Now wrt the atascii translation and the source I don't know how to do it right. I just downloaded the source from GitHub and made changes. Now I am not sure it is ok to redistribute the source code changed. Please explain, how to do it right.

Just as I said yesterday. Enter then Ctrl j

Just to keep it the same... First 130xe s then sio2bt os Edit: changed the order

Thanks for the quick response. I check and recheck the OS selection circuit and it is OK. I tried with other eprom from other compu with sio2bt and it worked, so I assume the circuit is OK. The circuit connects the pin 27 (A14) with pin 28 (VCC) with a pull up resistor, to keep the A14 high, when it is in SIO2BT mode (alternative OS). When I move the switch it connects A14 to GND (and at the same time power off the BT module). In this position (A14 low) the original atari XE OS is visible. Since it is a m27c512 four OS version are in the eprom: QMEG / QMEGBT / XE / XEBT . I am ok with just 2: XE/XEBT (in that order, BT is bluetooth) so a m27c256 should be enough. The ROMs are attached. Now I have a nice problem, I don't know who to ask to do this more me. Thank you guys for offering help. I will send PM with my address. Thanks again, Mauricio ps: TL866 is still >$80 right? or I am searching the net wrong? 130xeos.rom siobt2os.rom

speed dialing .. I would say yes. It i a dialing directory in which you enter the internet address and some options and then you assign a number. For example, irata online is assigned the number 300. Later you just "dial" atd 300 and connect to plato irata. OLED not sure, check zimodem in github: https://github.com/bozimmerman/Zimodem

Come on don't give up. I am sure enter+Ctrl j will work. But anyway, who wants to do all of that and that long series of commands, just to get connected, when you can flash zimodem in 1 step, and then enjoy a much better and simple implementation of an at compatible modem. Ditch the original firmware.

Hi guys and gals, I am having problems with my OS EPROM. The EPROM has 4 OS version but I toggle b/w 2 of them with a switch. The first is the one for SIO2BT (it includes cold reset with Shift+Reset and modified timing for disk access), and the second is a regular unaltered OS XE version (it came with my 65XE and it include the self test for the extra memory). Now The second one start random fails that send me directly to the self test, o just green or black screen, but sometimes work... I've been looking for a EPROM writer but they are still out of my budget and in my case will be barely used. If someone can create one for me, it will be greatly appreciated. If it is in USA is better so I can pay a decent postage and the price of the materials.. Thanks in advance.

I guess if you received echo, and the error... So is working! Right? Your input goes to the esp-01... And your circuit with LS00 and diode is not wrong.. try typing AT+ and then Ctrl j. It should work. Do not use Ctrl m Then try lowercase. Or just "at" Everytime follow with Ctrl j another option: at+ press enter and then Ctrl j. It should work with some combination... I am almost sure enter and then Ctrl j after each command will work

a8isa1, I don't know why, but I guess you just discovered the answer to all of this. Crtl j will make it

Just one idea left from me: retry the esp-01 and adatper but without LS00 and diode. Tx-->Din. And Dout-->RX. Just that. And power supply, of course. It should work, if the terminal program and the Rverter handler are driving the Sio Dout line.

uh ooh.... I tried to edit and make the correction... Too late... I will need to accept the consequences.

but i told him to try without additional circuit, just the "adatper" board. So connect directly: rx<---Dout, tx--->Din, to rule out the esp-01 and adatper board. if it work is the diode or 74ls00. maybe you try again. if it doesn't work, but it work in a PC, then the only option left is a broken Adatper.

Not 100% sure, but I guess this firmware and command made my esp-01 come back to life. After that I was able put Zimodem in my esp-01. cd ESP8266_NONOS_SDK-2.1.0/bin/ sudo esptool.py --baud 115200 --port /dev/ttyUSB0 --before no_reset --after no_reset write_flash --flash_mode qio 0x00000 boot_v1.7.bin 0x01000 ./at/512+512/user1.1024.new.2.bin 0xfc000 esp_init_data_default.bin 0x7e000 blank.bin 0xfe000 blank.bin In my case esp-01 was crazy throwing error mesages and rebooting. So the led didn't stop blink when power up. I got it to boot normally with this AT firmware. I tried to use this firmware, but it was so cumbersome. Then I switched to Zimodem. This is different to what you described in your case (mr-atari problem) but it might work. ESP8266_NONOS_SDK-2.1.0.zip

Esp-01 sends at every boot a message at 74880 rate (which is very very unusual baud rate). Every time I boot mine I see a few garbage characters and then zimodem kicks in at the right rate. It is a very basic low level message. My esp-01 was also "bricked" when arrived or I bricked it when tried to connect, and in my case that low level messages at 74880 told me that it could not load the program or something like that, kind of nothing at address XYZ. That is why I ended up trying other firmwares. The nice thing about that low level message is that it tells you if your device is in programming mode. So I opened minicom, then used something called anybaud to set the baud rate to this weird number (not possible with minicom), then with the right pins to Gnd or 5v I put the esp-01 in programming mode and power it up. In minicom I saw the device was in programming mode, then I close minicom, and used esptool to flash a new firmware, at 115 or 9600, etc, any rate worked. I tried several firmwares, up to a point in which I was able to make it work again. I will check my history in the Linux machine to see I could find the exact command and firmware that unbrick mine. But you can try meanwhile with the Zimodem bin I posted before. Edit: corrected low level baud rate of ESP-01

Maybe you can draw the nand gates "inside box" to make circuit idea.more evident and less prone to errors

31VA=9V x 3.45A

This is the little add-on for Atari 1030 for turning the "ready" led on using the esp-01

Now regarding the Zimodem firmware. The way I did it was just send a pre-compiled version to the esp-01. It turned out that the version has problems saving changes (like wifi pasword or address book). This is a known bug of some esp-01s: https://github.com/esp8266/Arduino/issues/4061 So I ended up installing arduino and compiling Zimodem by myself. I also took advantage of having the code and set the default baud rate to 2400 and changed the Pet-ascii translation tables to Atascii-Ascii. All the menus and options still refers to pet-ascii translation (like atdp), I did not change that. It was pretty straight forward to write the firmware to esp-01 if you don't need to compile. In Linux I used esptool.py. Not sure how it will work on windows or macosx, probably it will work. Find all about esptool.py in the website: https://github.com/espressif/esptool You need to do something like this to write the firmware (first you need to put the esp-01 in programming mode) sudo esptool.py --baud 115200 --port /dev/ttyUSB0 --before no_reset --after no_reset write_flash --flash_mode qio 0x00000 zimodem.ino.generic.bin I hope this help you guys in your endevoir ps: not sure if this forum accept .bin, hopefully it will work. zimodem.ino.generic.bin

Ok.. This is what - I guess - needs to be done to connect using the original at firmware: AT AT+GMR AT+CWMODE=1 AT+CIFSR AT+CWJAP_DEF="replace with wifi name","replace with password" AT+CWAUTOCONN=1 AT+UART_DEF? AT+UART_DEF=9600,8,1,0,0 set comm params AT+CIPMODE=1 transparent mode or everything get ipd prefix AT+CIPMUX=0 no multiplexing AT+CIPSTART="TCP","vintagebbsing.com",2325 this is one example AT+CIPSEND to start sending your stuff to the server