Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOS/MTCP doesnt recognize the esp8266-slip-router #29

Open
guidol70 opened this issue Nov 8, 2023 · 1 comment
Open

DOS/MTCP doesnt recognize the esp8266-slip-router #29

guidol70 opened this issue Nov 8, 2023 · 1 comment

Comments

@guidol70
Copy link

guidol70 commented Nov 8, 2023

As initial test I configured DOS/MTCP to use slip/etherslp - which did work fine with the following config:

DOS
CONFIG.BAT

SET MTCPCFG=C:\MTCP\MTCP.CFG
SET MTCPSLIP=TRUE
ETHERSL 0x60 4 0x3f8 115200

MTCP.CFG

HOSTNAME dellfx
PACKETINT 0x60
IPADDR 192.168.6.40
NETMASK 255.255.255.0
GATEWAY 192.168.6.41
NAMESERVER 8.8.8.8
MTU 1500

on the Linux/armbian-Side

stty -F /dev/ttyUSB0 -clocal -crtscts 115200
slattach -d -v -L -m -p slip -s 115200 /dev/ttyUSB0 &
ifconfig sl0 192.168.6.41 pointopoint 192.168.6.40 mtu 1500 up
arp -s 192.168.6.40 02:42:4c:aa:1b:68 pub
echo 1 >/proc/sys/net/ipv4/ip_forward

Then I flashed the ESP8266-SLIP-Router successfully with the
NodeMCU Flasher

Then I did connect to the slip-router via the follwing commands:

stty -F /dev/ttyUSB0 -clocal -crtscts 115200
slattach -d -v -L -m -p slip -s 115200 /dev/ttyUSB0 &
ifconfig sl0 192.168.240.2 pointopoint 192.168.240.1 mtu 1500 up
arp -s 192.168.240.1 02:81:5b:0c:5e:1b pub
echo 1 >/proc/sys/net/ipv4/ip_forward
telnet 192.168.240.1 7777

The show command did work, so I did reconfigure the configuration:
CMD>

set ssid Masallah_TT
set password MyPassword
set addr 192.168.6.40
set addr_peer 192.168.6.41
set use_ap 0
save
reset

On another armbian-system I did connect successfully to the slip-router via the commands:

stty -F /dev/ttyUSB0 -clocal -crtscts 115200
slattach -d -v -L -m -p slip -s 115200 /dev/ttyUSB0 &
ifconfig sl0 192.168.6.41 pointopoint 192.168.6.40 mtu 1500 up
arp -s 192.168.6.40 02:81:5b:0c:5e:1b pub
echo 1 >/proc/sys/net/ipv4/ip_forward
telnet 192.168.6.40 7777

And the "show" command does show my configuration fine:

CMD>show
ESP SLIP Router V1.1.1 (build: Sun Feb 23 23:34:52 2020)
SLIP: IP: 192.168.6.40 PeerIP: 192.168.6.41
STA: SSID: Masallah_TT PW: MyPassword [AutoConnect:1]
External IP: 192.168.6.82
DNS server: 8.8.8.8
Clock speed: 160
Serial bit rate: 115200

But when I try to use the slip-router with DOS/MTCP it doesnt seems to be recognized :(
For PING (like 192.168.6.41 or 8.8.8.8) and TELNET I do get TimeOuts only.
But the blue LED is blinking when MTCP did try to send some packets to the slip-router.

I did test the RS232-Connection successfully with TELIX (a Terminal-Programm) so my cable/pinout is OK and with another simple-serial-sketch the serial Connection doesnt have problem with 115.200Baud.

When I restart the slip-router while connected with TELIX at 115.200Baud I do get always the same chars, but they arent readable (doenst know if there should something readable from the slip-protocol) :(

[EDIT]
the unreadable chars in TELIX are the Bootloader Messages of the ESP8266 at 74880 Baud
(and TELIX cant handle this Baudrate in DOS):

 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 31016, room 16
tail 8
chksum 0x07
load 0x3ffe8000, len 2068, room 0
tail 4
chksum 0x2f
load 0x3ffe8820, len 3132, room 4
tail 8
chksum 0xac
csum 0xac
rf cal sector: 1019
freq trace enable 0
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 3.0.0-dev(c0f7b44) compiled @ Jun 26 2018 16:54:37
phy ver: 1136_0, pp ver: 10.2

You could see TELIX and my ESP8266-NodeMCU-Pinout here

@martin_ger
Danke schon mal fuer reinbschauen. Evtl. hast Du eine Idee, auch wenn DOS/MTCP nicht Dein FAchgebiet ist - aber per seriellem USB-Kabel klappt DOS/MTCP.

Liebe Gruesse aus Mudany/BUrsa/Tuerkei - bis 2016 hatte ich in Frankfurt/Main gewohnt - also nicht weit weg von Wiesbaden.

Guido Lehwalder

@cshunt
Copy link

cshunt commented Jan 7, 2024

Have you tried to lower the baud rate? Some older uarts can only handle 38400 reliably. I run 1200 on a couple older serial cards. you have already proven that esp works with a pi.

I have also seen power issues where supplying 5volts from the same power supply on the computer (and ground) has made the esp transmit without error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants