You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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
The text was updated successfully, but these errors were encountered:
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.
As initial test I configured DOS/MTCP to use slip/etherslp - which did work fine with the following config:
DOS
CONFIG.BAT
MTCP.CFG
on the Linux/armbian-Side
Then I flashed the ESP8266-SLIP-Router successfully with the
NodeMCU Flasher
Then I did connect to the slip-router via the follwing commands:
The show command did work, so I did reconfigure the configuration:
CMD>
On another armbian-system I did connect successfully to the slip-router via the commands:
And the "show" command does show my configuration fine:
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):
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
The text was updated successfully, but these errors were encountered: