Just built an Altmill with a gcontrol running gsender 1.5.5. Everything thing seems good when the gcontrol is connected to the SLB-EXT via USB. However, when I use the ethernet cable, motion is rough and stutters. Homing is still smooth, but jog commands and gcode motion are not. I’m assuming homing is executed on the SLB-EXT, which is why it’s smooth. So it seems the gcontrol can’t send motion commands fast enough when jogging or executing gcode motion.
The gcontrol is connected directly to the SLB-EXT. Both the SLB-EXT and gcontrol are using static IP configuration. Is a shielded ethernet cable required? I’m using an unshielded CAT 6 cable at the moment. Any other settings on the SLB-EXT or Windows config that might be causing this problem?
Dang, I wish I could remember but I had that exact problem some time back. I tried searching my old messages but could not find anything.
Double check IP numbers and anything related to IP numbers including in the gSender config/setup areas.
Edit: I used a standard ethernet cable (cat5 I believe)
Edit 2: Way in the back of my head I seem to recall that there was something in the gSender setup/configuration that specified an IP number. I believe I was on the same subnet but the last number didn’t match and gSender ended up trying all the IP addresses on that particular subnet which introduced a time delay.
I didn’t change any of the SLB-EXT settings from factory. I did have to change the window IPv4 settings. This morning I came out and checked all settings and didn’t find anything wrong (made no changes). I tried the ethernet connection again and it worked. All I can think of is that windows didn’t apply all of the IPv4 changes correctly until after a reboot.