Closed mullenba closed 4 years ago
here are my network settings.
.## Network settings .# See http://smoothieware.org/network .network.enable true # Enable the ethernet network services .network.webserver.enable true # Enable the webserver .network.telnet.enable false # Enable the telnet server .# network.ip_address auto # Use dhcp to get ip address .# Uncomment the 3 below to manually setup ip address .network.ip_address 192.168.1.222 # The IP address .network.ip_mask 255.255.255.0 # The ip mask .network.ip_gateway 192.168.1.1 # The gateway address .#network.mac_override xx.xx.xx.xx.xx.xx # Override the mac address, only do this if you .have a conflict
I gave it a static ip of 192.168.1.222 I enter http://192.168.1.222 in my browser and there it is. it works for me disconnect from the network before printing - mine crashes
At least yours lights on activity leds, mine is total dead on LAN, was like that from day zero, looks like I got a not so quality tested board...
I have the same problem. This is my config:
`
network.enable true # Enable the ethernet network services network.webserver.enable true # Enable the webserver network.telnet.enable true # Enable the telnet server network.ip_address 192.168.2.2 # The IP address network.ip_mask 255.255.255.0 # The ip mask network.ip_gateway 192.168.2.1 # The gateway address network.mac_override D1.C8.A1.F1.AE.CB # Override the mac address, only do this if you have a conflict`
It doesn't even boot without the .mac_override. The leds on all ethernet jacks stay silent. ethtool tells me the link is down. I've tried a raspberry pi and a router.
I've checked my board and I have the updated crystals, i.e. the flat SMD version.
Someone seems to have it fixed in issue 48: https://github.com/makerbase-mks/MKS-SBASE/issues/48
The 3.3V supply was forgotten. Connect C43 and C46 for an easy fix
I've got a LUME printer with MKS SBASE v1.3 Here's my default network config:
# network settings
network.enable true # enable the ethernet network services
network.webserver.enable true # enable the webserver
network.telnet.enable true # enable the telnet server
#network.ip_address auto # use dhcp to get ip address
# uncomment the 3 below to manually setup ip address
network.ip_address 192.168.3.221 # the IP address
network.ip_mask 255.255.255.0 # the ip mask
network.ip_gateway 192.168.3.1 # the gateway address
#network.mac_override xx.xx.xx.xx.xx.xx # override the mac address, only do this if you have a conflict
ipconfig after just connecting the ethernet cable to the computer:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek Gaming 2.5GbE Family Controller #2
Physical Address. . . . . . . . . : D8-...-A2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::...17(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.249.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 316193729
DHCPv6 Client DUID. . . . . . . . : 00-...-A2
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
ipconfig after manually setting 192.168.3.221 for IPv4:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek Gaming 2.5GbE Family Controller #2
Physical Address. . . . . . . . . : D8-...-A2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IPv4 Address. . : 169.254.249.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IPv4 Address. . . . . . . . . . . : 192.168.3.221(Duplicate)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.3.1
NetBIOS over Tcpip. . . . . . . . : Enabled
ping 192.168.3.221 returns connection timed out (no response)
ping 169.254.249.150 returns
Reply from 169.254.249.150: bytes=32 time<1ms TTL=128
Reply from 169.254.249.150: bytes=32 time<1ms TTL=128
Reply from 169.254.249.150: bytes=32 time<1ms TTL=128
Reply from 169.254.249.150: bytes=32 time<1ms TTL=128
but the LEDs on the MKS SBASE board ethernet socket do not blink.
I already bridged the two contacts on the PCB per https://github.com/makerbase-mks/MKS-SBASE/issues/48
I'm rather desperate to not have to run to the printer with an SD card tens of times per day :/
Do I post it as a new issue or is this one going to be re-opened?
Try to join Makerbsse FB group
On Sat, Nov 4, 2023 at 15:04 otede @.***> wrote:
Do I post it as a new issue or is this one going to be re-opened?
— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-SBASE/issues/82#issuecomment-1793554525, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYWWXOROR2DS7OK27JJ6UTYC2UV3AVCNFSM4FEFT3MKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZZGM2TKNBVGI2Q . You are receiving this because you are subscribed to this thread.Message ID: @.***>
Try to join Makerbsse FB group … On Sat, Nov 4, 2023 at 15:04 otede @.> wrote: Do I post it as a new issue or is this one going to be re-opened? — Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYWWXOROR2DS7OK27JJ6UTYC2UV3AVCNFSM4FEFT3MKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZZGM2TKNBVGI2Q . You are receiving this because you are subscribed to this thread.Message ID: @.>
My thoughts after checking out the FB groups: can a board be more dead? 😀
is your ethernet connection directly between MKS and PC or do you have a switch in between? Normally, you need a cross-over ethernet cable for 1-to-1 direct connection if you network card can not detect this.
Also, you are maybe running into a smoothieware (firmware) issue and not an MKS hardware problem.
is your ethernet connection directly between MKS and PC or do you have a switch in between? Normally, you need a cross-over ethernet cable for 1-to-1 direct connection if you network card can not detect this.
I have a modem router so I could do away without crossover. I monitored the network log after plugging in the cable. All quiet.
"Also, you are maybe running into a smoothieware (firmware) issue and not an MKS hardware problem." I only found this https://forum.makerforums.info/t/network-problem/77058 and I give up at this point. Re-flashing/updating firmware is a no go for me. I had problems flashing even the manufacturer-supplied firmware update.
Thank you for your input, I really appreciate it @Quas7 Hit me if you have any further fool-proof ideas but firmware juggling is not for me. I already spent 3 times more time fixing the printer than actually printing.
Progress? https://pastebin.com/JYuq0bcS
I used a crossed ethernet cable directly, printer-PC.
I think guys need to know that this board has been discontinued. All documentation should refer to the Smoothieboard.
On Thu, Nov 9, 2023 at 12:30 otede @.***> wrote:
Progress? https://pastebin.com/JYuq0bcS
— Reply to this email directly, view it on GitHub https://github.com/makerbase-mks/MKS-SBASE/issues/82#issuecomment-1804491188, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYWWXLQEPPBPWHKH5Y5E2LYDUVOBAVCNFSM4FEFT3MKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBQGQ2DSMJRHA4A . You are receiving this because you commented.Message ID: @.***>
I recently bought a 1.3 card and updated to the most recent stable firmware. When I connect it to the network, the activity lights flash, but it doesn't appear on my DHCP clients list. If it's not getting an IP I can't connect to it to use it.
Config is set properly ( as far as I know)
What troubleshooting can I do, or things can I look for before just sending it back?