Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - billskeen63

Pages: [1]
1
Thanks 12strings. I appreciate you taking the time to respond.

As it is in most cases in using new h/w & s/w, it was a stupid user error.

I was changing the Input#15 on the Configure/Control/Inputs tab. I needed to scroll down to the E-Stop input and select SmartBobUSB pin 15. Figured it out when I looked carefully at my old Mach3.

The Pin10/EStop label on the SmartBob I/O status confused me too.


2
Okay, been working fine for over an hour now.

No ferrite ring, no changes to Windows Defender, Power Settings, holding my tongue in a certain position or waiting for the second blue moon of the month.

Time to move on.


3
It may be the Asus Laptop.

Tried installing Mach4 Demo on another Laptop. Installed PMDX drivers. Opened Mach4, setup motors, checked PMDX. Everything looked good.

Been running for about 20 minutes now without loss of comm to PMDX.

More to come.

5
Found this error in EventViewer. It appears to have occurred eveytime Mach4 lost comm with PMDX.

The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
Windows.SecurityCenter.WscCloudBackupProvider

Disabled Windows Defender in registry, rebooted and waiting to see if it dies again.

6
Reinstalled and did not work at first.

Noticed in Add/Remove programs, there was a 1.30 version of the Virtual Comm driver. It was for the wireless mouse. Uninstalled it, v1.4 and PMDX driver. Then only ran the PMDX driver install. Got both install screens and completed second one before first one.

Now working. Jogged continuously for several minutes across all 3 axis. Going to try putting the wireless mouse back on to see if that kills it again.If so, I'll remove everything again and only install the PMDX drivers.

Cancel that. Went back to test installing wireless mouse and lost comm error message was on screen again.

And yes, I've disabled the helpful USB power saving settings, too.

I've run out of ideas. Any help appreciated.

7
Well, it is totally not working at all now. Same error message.

Tried powering everything off, getting laptop, G540, power supply all on same circuit. Added Ferrite ring over USB cable. No joy.

Deleting all drivers and attempting to reinstalled them now.

Old Mach3/PC using parallel still works. So that, to me, eliminates G540 and everything beyond.


9


Mon Dec 17 07:20:19 2018
Mach4 Version: 3804
Screen Set: wx4.set
Device: PMDX-411 [Rev A PCB] on COM3
Serial Number: SN36604 (A1 )
Plug-in Version: 0.52.254
Bootloader Version: 1.13.73
Firmware Version: 0.58.205

---  End  ---

Running Windows 10 64bit on Asus G501J laptop

Mach4 History
PMDX: Communication error 'Lost Sync'PMDX: Could not disable the PMDX-SmartBOB-USB, error 'Cannot communicate with device'


10
Same scenario. On old Mach3, windows 7 PC with parallel port connected to G540, can jog at will.

On new Windows 10 laptop, latest Mach4v2 and PMDX-411 drivers, using USB port, PMDX-411 and G540, I can jog a few times on any axis and then get error about cannot communicate with Smartbob.

Requires complete restart of laptop and power off/on of G540 to get it to jog again, but then loses comm. again.

Any ideas?

11
I was using Mach3 on an old Windows 7 machine, connected to G540, with real emergency stop button connected to pins 10 and 12/ground.

On new Windows 10, 64bit system, setup using latest versions of Mach4 v2 and drivers for PMDX 411, created new profile, selected PMDX-411 motion controller in Mach 4. Tried everything I know to clear the emergency stop with no joy. Then connected emergency stop to pin 1 on G540 and ground. Could now clear estop and enable.

Do I have to use 411 pin 10/G540 pin 1 for estop?


Pages: [1]