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
Hi Phil,
I'm attempting to connect myT41U5XBB board to my network.
Have generated and loaded firmware as per your instructions: https://www.grbl.org/single-post/networking-the-t41u5xbb, with Ethernet/telnet/Websocket all checked, and attempted to connect to the board via the network, unfortunately unsuccessfully. As far as I can tell USB connection is working OK. (machine homes and can move with gcode)
The board is connected to the network, and the network connector led is flashing. It successfully obtains an IP address, but there is no message indicating a NETCON connection. I can ping the ip address from my Windows laptop, but am unable to open a connection using telnet from the laptop.
When starting ioSender, the program shows the message "Unable to open connection (ws://192.168.XXX.XXX:80)" showing the correct IP address.
Could you be able to either point me in the right direction or suggest any further diagnostic moves?
Thanks,
Dave.
The text was updated successfully, but these errors were encountered:
Hi Phil,
I'm attempting to connect myT41U5XBB board to my network.
Have generated and loaded firmware as per your instructions: https://www.grbl.org/single-post/networking-the-t41u5xbb, with Ethernet/telnet/Websocket all checked, and attempted to connect to the board via the network, unfortunately unsuccessfully. As far as I can tell USB connection is working OK. (machine homes and can move with gcode)
The board is connected to the network, and the network connector led is flashing. It successfully obtains an IP address, but there is no message indicating a NETCON connection. I can ping the ip address from my Windows laptop, but am unable to open a connection using telnet from the laptop.
When starting ioSender, the program shows the message "Unable to open connection (ws://192.168.XXX.XXX:80)" showing the correct IP address.
Could you be able to either point me in the right direction or suggest any further diagnostic moves?
Thanks,
Dave.
The text was updated successfully, but these errors were encountered: