search

t-oster / VisiCut

A userfriendly tool to prepare, save and send Jobs to Lasercutters
https://visicut.org
Other
230 stars 114 forks source link

Error: connection timed out #386

Closed mdcummings closed 7 years ago

mdcummings commented 7 years ago

I'm trying to drive and Epilog Helix from a Mac via ethernet. I set the IP address to the match my Epilog. Ethernet indicates that it is connect in system settings. However, when I press execute it tries and fails to connect. I've tried a regular ethernet cable and also a "crossover" ethernet cable as mentioned in the epilog manual. Can you give me any ideas about what's wrong?

t-oster commented 7 years ago

Hi, can you ping your epilog from the command line? can you netcat to port 515? You probably need to configure your Mac to be in the same subnet as the (static?) ip of your epilog.

mdcummings commented 7 years ago

yes, i ping 192.168.3.4 successfully (zero packet loss, 10 ms typ) I don't know how to netcat. what's that do? subnet mask for both is 255.255.255.0

mdcummings commented 7 years ago

do you know anything about epilog saying I should use a "crossover" ethernet cable? Is that required?

t-oster commented 7 years ago

if you can ping it, the ethernet cable is fine. Most current network-cards detect crossover anyway and automatically switch it, so it probably is not necessary, but it does not hurt. You may have a firewall, which is blocking traffic to port 515? netcat is a command line utility, which just connects to tcp ports. Just open the command line and try netcat 192.168.3.4 515 or nc 192.168.3.4 515. I am not sure if it is installed by default though.

mdcummings commented 7 years ago

Thanks you for your help Thomas. I figured out my problem. I hadn't changed "Hostname" in the manage lasercutters menu to my epilog's IP address. I had left the default as shown below. Doh! As soon as I fixed that, it worked! If that was documented somewhere, I must have missed it. Thanks again!

On Thu, Oct 27, 2016 at 12:53 PM, Thomas Oster notifications@github.com wrote:

if you can ping it, the ethernet cable is fine. Most current network-cards detect crossover anyway and automatically switch it, so it probably is not necessary, but it does not hurt. You may have a firewall, which is blocking traffic to port 515? netcat is a command line utility, which just connects to tcp ports. Just open the command line and try netcat 192.168.3.4 515 or nc 192.168.3.4 515. I am not sure if it is installed by default though.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/386#issuecomment-256750887, or mute the thread https://github.com/notifications/unsubscribe-auth/ASrEwkEFZnh8e2ikQAgMrdm9vtejCt4dks5q4QEmgaJpZM4Kiqct .

t-oster commented 7 years ago

Please feel free to update the wiki. So we can consider this as closed?

t-oster commented 7 years ago

...but what did you mean by I set the IP address to the match my Epilog if not changing the hostname?

mdcummings commented 7 years ago

In Apple Network Settings, I set ethernet to the range 192.168.3.X. I thought this was all I needed to do since Ethernet showed "connected" and ping test worked. What I didn't realize is that Visicut needed the proper Hostname/IP for the cutter. It would be good to say in your manual, " Set the IP address of your laser cutter in the Hostname field of Visicut's Manage laser cutter settings."

Also, in your downloads area, I used the older "tested" builds. I noticed that the newer "untested" builds actually had the right default IP for Epilog. Now I'm using your newest build. I like it!! I'd suggest you tell newbies to use the newest builds but if they experience problems, try the older "tested" builds. Your new builds have lots of nice features.

All the best

On Fri, Oct 28, 2016 at 4:44 PM, Thomas Oster notifications@github.com wrote:

...but what did you mean by I set the IP address to the match my Epilog if not changing the hostname?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/386#issuecomment-257054070, or mute the thread https://github.com/notifications/unsubscribe-auth/ASrEwjSuv7hlsEyExFlSKdoiulwAWi9Aks5q4ojBgaJpZM4Kiqct .

mdcummings commented 7 years ago

Will do

On Fri, Oct 28, 2016 at 4:43 PM, Thomas Oster notifications@github.com wrote:

Please feel free to update the wiki. So we can consider this as closed?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/t-oster/VisiCut/issues/386#issuecomment-257053966, or mute the thread https://github.com/notifications/unsubscribe-auth/ASrEwm81AWpRm9xhb3Cd77V_6spoMmxcks5q4oiPgaJpZM4Kiqct .