Quote Originally Posted by Neale View Post
I'm just pleased that I now have a system where I can just switch on the PC and while I'm fiddling about retuning the radio and so on, the PC is booting directly into myCNC. And it waits for the controller to be switched on and doesn't bitch about the IP/M not being ready yet - which usually meant stopping and starting Mach3 once the control box was powered up. The homing button now homes all axes and squares the gantry all by itself - another Mach3/CSMIO issue fixed. All good fun, even if I'm not expecting wonders from the improved S-curve trajectory planner with my machine's somewhat limited performance. But we'll see in due course.
Nah that's not fair Neale.!!. . . . . The ET would complain just the same if you hadn't turned on the control box before the software started. If the card isn't powered it can't connect so it's going to bitch. Or are you saying it will startup and bitch but when the controller comes online it just connects.? . . . If I could get it to work then I'd obviously know this.!! . . . I'm on 3rd win10 PC now it won't work with.??

RANT WARNING.!! . . . I'm starting to get slightly pissed off with this card now.!... I've wasted another 4hrs... It's advertised as being able to run on Win10 and it won't or won't reliably.
I don't want to use Linux based PCs or mess around with dual booting etc. I need Windows-based Pc's so my users can use software packages like Vectric etc on the same PC. Plus if I wanted to use Linux based Pc's and mess around writing Macros then I'd use LinuxCNC with Mesa cards and save my self a lot of money.

This isn't really acceptable to me for a Card costing $700.!. . . . . I'm very disappointed to be honest because while it may work reliably on Linux OS it feels like they are selling a Beta version for Win OS and it's still got bugs clearly.