Hello Guest it is November 15, 2019, 01:17:40 PM

Author Topic: Communications error starting Mach3 with G100  (Read 8772 times)

0 Members and 1 Guest are viewing this topic.

Communications error starting Mach3 with G100
« on: July 31, 2007, 11:00:09 PM »
I'm getting the following error when starting Mach3 with the G100:

Error during RUN phase: Communication/programming error
1) Enumerator: inst=0 part=1 ecode=813
Unsupported partition number

I'm able to communicate with the G100 using Grex-Loader.exe and believe that I have everything configured correctly. Does anyone know what this error is about?

Offline Chaoticone

*
  • *
  •  5,628 5,628
  • Precision Chaos
    • View Profile
Re: Communications error starting Mach3 with G100
« Reply #1 on: July 31, 2007, 11:37:09 PM »
Where did you get the firmware and plug-in from?

Brett
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!
Re: Communications error starting Mach3 with G100
« Reply #2 on: August 01, 2007, 04:09:22 PM »
After seeing your post, it seems probable that I did load the wrong firmware. How do I get the Download Manager to work again? Whenever I try to connect to the G100 I get a message that says I can display the web page.

Offline Chaoticone

*
  • *
  •  5,628 5,628
  • Precision Chaos
    • View Profile
Re: Communications error starting Mach3 with G100
« Reply #3 on: August 01, 2007, 04:18:40 PM »
Have a look at this thread. Read the thread, I think it pertains to you too. You can download what I have of the G-100 set-up guide so far. Do you know the IP of your G100? If you have set it up and can't remember what it is, it can be troublesom. Try this, kill the power to the G100, Open the grex loader, power on the g100 and start hitting the find gecko button, not just once, about every 2 seconds. If it hasn't found it in 10 seconds, start over. Power down,etc.

http://www.artsoftcontrols.com/forum/index.php?topic=3797.0

Brett
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!
Re: Communications error starting Mach3 with G100
« Reply #4 on: August 01, 2007, 06:56:42 PM »
After powering down and starting Grex-Loader, I get an IP address of 192.168.1.31 and a subnet mask of 255.255.255.0 (See Image Grex1.jpg). If I set that IP address, refind the Gecko and "Launch Firmware Loader" a browser window pops up and says "Internet Explorer cannot display the webpage" (Browser1.jpg). I can ping the address 192.168.1.31 (Ping1.jpg).

The problem at this point is that I have no way to communicate with the G100 if I can't get to the web page.

Offline Chaoticone

*
  • *
  •  5,628 5,628
  • Precision Chaos
    • View Profile
Re: Communications error starting Mach3 with G100
« Reply #5 on: August 01, 2007, 07:02:58 PM »
Once you get the error page, try to cycle power to the G100 and launch firmware loader without closing the firmware loader. You have to be quick.

Brett
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!
Re: Communications error starting Mach3 with G100
« Reply #6 on: August 01, 2007, 07:35:25 PM »
Got it!!! Thanks much!!

I'll play with this and see if I can't get the correct firmware loaded..........
Re: Communications error starting Mach3 with G100
« Reply #7 on: August 01, 2007, 07:46:22 PM »
Worked like a charm once I loaded the right firmware.......

Offline Chaoticone

*
  • *
  •  5,628 5,628
  • Precision Chaos
    • View Profile
Re: Communications error starting Mach3 with G100
« Reply #8 on: August 01, 2007, 09:39:02 PM »
Good to hear Swainsk.  :) Did you look at the manual? If so, was it helpful?

Brett
;D If you could see the things I have in my head, you would be laughing too. ;D

My guard dog is not what you need to worry about!
Re: Communications error starting Mach3 with G100
« Reply #9 on: August 01, 2007, 10:19:08 PM »
Yes, I read the manual and it was very helpful. Reading the manual was how I installed the firmware and plugin the first time. I just installed the wrong firmware. After doing it wrong initially, though, it wasn't clear how to get back into the download manager. Once back into the download manager, it was just a matter of following the manual correctly.