Re: UC300ETH not connecting
Where do you have the UC300 plugged in? Into the PC, or a router?
If the PC, did you configure the network as shown in the manual?
Re: UC300ETH not connecting
Did you run UCxxx Utility software? Did it confirm the presence of UC300ETH? To me it sound like a configuration of the card. The factory default is in my opinion wrong, but never the less, it is easy to change. No point trying with Mach3 if the UCxxx utility software is not recognizing the card.
Re: UC300ETH not connecting
Quote:
Originally Posted by
Andrew22
I recently received a new UC300ETH board, and have downloaded all the latest software to run this board through Mach3. When I load Mach3 there's a window that pops up asking me if I want to use the UC300 or a serial connection, and when I select the UC300 I get an error message saying the board can't be found and to check connections. I've checked the board has power and I've used several ethernet cables to make sure one wasn't damaged, but no matter what I can't get the board to connect. Has anyone experienced this who can offer some more troubleshooting advice. Google hasn't turned up anything relevant.
Did you manage to solve this issue?
Re: UC300ETH not connecting
Quote:
Originally Posted by
A_Camera
Did you manage to solve this issue?
As of this date, I have found that with a UC300ETH and the M45 board the current plugin on the UC page will not work with mach3.
I had to get the UC300ETH V1_015 plug in and the connection error message went away.
I was able to ping the UC300, the UC utility said everything was fine, but I got the connection error message in mach3.
I got the Plug in from Arturo at CNC4pc.
Hope this helps.
Re: UC300ETH not connecting
You can update the plugin from the plugin screen in Mach3, and it should find the latest version, which will usually be newer than the one on the website.
Re: UC300ETH not connecting
Anyone with a UC300ETH (or any CNC Drive controller, really) should really try UCCNC. It's only $60, and much better than Mach3.
Re: UC300ETH not connecting
I get this error when I run the UCCNC program.
“The application lost the connection to the motion controller device. Check the connection. The application is closing now! Save offsets?"
I can find the UC300-ETH-LPT5 with the utility on the network. UCCNC is licensed.
Any ideas?
Re: UC300ETH not connecting
Quote:
Originally Posted by
thesleepydog
I get this error when I run the UCCNC program.
“The application lost the connection to the motion controller device. Check the connection. The application is closing now! Save offsets?"
I can find the UC300-ETH-LPT5 with the utility on the network. UCCNC is licensed.
Any ideas?
The utility tool always find the UC300ETH or UC400ETH even if you setup your network incorrectly.
Did you setup the network card's IP address as shown in the manual?
What is the utility tool's answer when you press the test connection button? Does it show any errors and suggestions or it shows connection OK?
Re: UC300ETH not connecting
Does it find it when you first start UCCNC? If so, the cable may be loose, or have a bad connection?
If it never connected, UCCNC would start in demo mode.
I've only seen that message when I've powered off the UC300ETH with UCCNC still running.
Re: UC300ETH not connecting
Quote:
Originally Posted by
thesleepydog
I get this error when I run the UCCNC program.
“The application lost the connection to the motion controller device. Check the connection. The application is closing now! Save offsets?"
I can find the UC300-ETH-LPT5 with the utility on the network. UCCNC is licensed.
Any ideas?
I get this error message when the automatic backup task starts to run. No other software will notice this but UCCNC shuts down. It took me quite a while to understand that it was caused by the backup software start. I don't know why UCCNC is so sensitive.
Re: UC300ETH not connecting
Quote:
Originally Posted by
A_Camera
I get this error message when the automatic backup task starts to run. No other software will notice this but UCCNC shuts down. It took me quite a while to understand that it was caused by the backup software start. I don't know why UCCNC is so sensitive.
Because it needs to get answer in max. 20ms. If your backup works on network, it can easy slow down or hang the UCCNC connection. Check statistics window for latency while starting backup.
Re: UC300ETH not connecting
Quote:
Originally Posted by
dezsoe
Because it needs to get answer in max. 20ms. If your backup works on network, it can easy slow down or hang the UCCNC connection. Check statistics window for latency while starting backup.
Ok, thanks. The backup is done locally on a separate HD. No big issue for me, normally I disable it if I run UCCNC but annoying if I forget it.
Re: UC300ETH not connecting
https://www.cnczone.com/forums/image...quote_icon.png Originally Posted by thesleepydog https://www.cnczone.com/forums/image...post-right.png
I get this error when I run the UCCNC program.
“The application lost the connection to the motion controller device. Check the connection. The application is closing now! Save offsets?"
I can find the UC300-ETH-LPT5 with the utility on the network. UCCNC is licensed.
Any ideas?
The utility tool always find the UC300ETH or UC400ETH even if you setup your network incorrectly.
Did you setup the network card's IP address as shown in the manual?
What is the utility tool's answer when you press the test connection button? Does it show any errors and suggestions or it shows connection OK?
I did follow the setup manual. What I ended up finding is windows was assigning an auto configured ip address despite the fact I set it to static on my PC to 10.10.10.10. I found this when I ran the ipconfig command. I googled why and how to stop windows overriding my settings as I hadn't seen it do this before. Applied a regedit fix to stop windows changing my config and viola, it worked.
BTW - I also made up a cross over cable and direct wired the PC to the UC300-ETH at some stage in the trouble shooting process.
Re: UC300ETH not connecting
Quote:
I did follow the setup manual. What I ended up finding is windows was assigning an auto configured ip address despite the fact I set it to static on my PC to 10.10.10.10. I found this when I ran the ipconfig command. I googled why and how to stop windows overriding my settings as I hadn't seen it do this before. Applied a regedit fix to stop windows changing my config and viola, it worked.
BTW - I also made up a cross over cable and direct wired the PC to the UC300-ETH at some stage in the trouble shooting process.
Windows auto-fix the IP if there is an IP address collision.
If you have any other network cards in the computer or if you have any virtual cards then check their IP addresses (ipconfig /all), because it is likely that one of them is in the same range is why Windows fixing the IP for you.
Check also the IP of the UC300ETH, because Windows also fixes the IP of the card if there is a collision between the card IP and the IP of the device connected.
For example if you set the UC300ETH IP to 10.10.10.10 and the network card IP to 10.10.10.10 that is a collision.
