G100 communication problem

[henkb]

Hi,

I managed to upload all the firmware to the g100 just fine. It has received an IP address and I can ping it on the network. So far so good.
Now I try to connect with Mach :no luck. Mach does not see the G100.
The latest plugin also installed properly.
The only thing I haven’t got yet is the licence for the G100. Is this the reason Mach does not see the G100?
Any help appreciated.


Henk

[123CNC]

lots of problems in this category, most likely is you are having trouble with the Rabbit IC. How old is your GRex?

you might want to read some of the G100 threads on the Mach website.

you might check with Gecko to see if you can get a replacement Rabbit for $50 (may have changed)

[Clockwork]

You didn't post any details of your problem.

Did you run the Grex Loader?

What are the IP addresses of the Grex and your computer? What is your Subnet Mask set to on your computer and the Grex?

What is the specific error in Mach 3?

Are you using the latest version of Mach 3?

[henkb]

Hi,
Thanks for your reply's. The problem is this:
My grex-loader never detects the g100. If I enter the Ip address manually and click launch firmware loader it will open a internet explorer page and I can upload the firmware without any problems. The grex loader will never detect the g100, not on the network via a router and not when connected with a cross cable. In both situations I can ping the g100 without problems and I can reach the upload page with internet explorer. Mach also never connects to the G100, it times out.
I get the feeling that something may be wrong with the G100. It was bought more then one year ago and never used until now. i can think of anything more to try.
All your suggestions are more then welcome. I like the get this thing running. (it's to expensive as an paperweight!)

Thanks

[Clockwork]

I have 6 Grex controllers working with dedicated older laptops and crossover cables. Here is the setup I'm using for all my machines:

Laptop:

Using a hardcoded IP address
192.168.1.1 - Subnet Mask 255.255.255.0

Grex:

Datecode - 060210
Default FPGA - 1
Auto-Boot Time - 10
Firmware Size - 190806
Free Space - 991232
Current Network - 192.168.1.250 255.255.0.0
DHCP Timeout - 0
Core - RCM 3720/RCM 3750


FPGA Config

FPGA1 - 55632


When the Grex is powered on you have a 10 second window to launch the Grex Loader "Find Gecko" function. Also - once the browser page is accessed the Grex must be reset and allowed to run for 10 seconds before Mach can access it.

There are 2 sets of firmware for 10 or 100 MB links. I use the one for 10 MB. Don't think the 100 MB firmware works. This is defined in the README text file.

Hope this helps

[henkb]

Hi Clockwork,

Thanks for your reply. When I saw it I thought that’s it! In my configuration the Default FPGA =0 and in yours it =1! So I changed it to 1 and tried again. but no luck. Both the Grex loader and Mach do not see the G100.
When I start the Grexloader program and switch on the G100, click Discover several times during the first 10 seconds nothing happens, the g100 is not found. The Run led has not come on : so to me it seems they are communicating. If I then enter the IP address manually and press Launch, a internet explorer opens and shows the firmware upload page.
Apart from the FPGA=0 setting everything else is as you described.
If I click the run button the RUN led comes on as it should. So that seem to work normal
I even set the IP address to 192.168.1.1 to see if that would help but no luck.
I just cant understand why I get the setup page in IE (surely it must communicate with the G100 to do so) but cannot connect with the grex-loader or Mach.

On my G100 there a written label that says E7. Don’t know if this means anything to anybody?

Well I am open for bright ideas………

Henk

[Clockwork]

In the Default FPGA field a 0 and 1 mean essentially the same thing if you only have 1 FPGA image installed.

The only time I couldn't get the Grex Loader to see the device is when the IP addresses weren't coordinated to the same subnet. I would suggest trying a different computer but you probably already thought of that.

You could try downloading some free sniffer software and comparing the transactions that occur with the Grex Loader to those with direct browser access. Analyzing this data requires a bit of knowledge but it sounds like you're a pretty smart guy.

You could try sending an email to Art over at Mach 3. He usually responds within a few hours - be specific.

The guys over at Gecko won't be of much help on this type of problem. I did have a problem with my oldest box and sent it back to Gecko. They fixed a bonehead configuration issue and sent it back within one day - didn't charge me anything.

"E7" means your box was built in the 5th month of 2007. My boxes were built both before and after this date.

One guy suggested that you replace the rabbit. Don't know if he was shooting in the dark or if he has insight into this specific problem. I don't know the symptoms of the rabbit problem since I haven't had it on any of my boxes.

Still trying to help

[Clockwork]

I just remembered that a year ago when I was experiencing problems with my first Grex install I ran a sniffer to analyze what was going on. The Grex Loader and Mach 3 initate communication on a high numbered port - as I recall was in the 1300 range.

Your browser is connecting on port 80.

You could have some firewall issues blocking access on the higher numbered ports.

[henkb]

Hi Clockwork,

Well its not going to work. I tried different computers and different IP addresses in my home network; No luck. I tried several computers with a fixed IP and a cross cable No luck.
Problem is always the same: Grex-loader and Mach cannot detect the G100.
If the Grex-loader program is running theG100 will not go into RUN state. So they communicate! Still the G100 is not found. IE connects without problems with the G100. When I activate the RUN command the green led comes on and the web pages closes. As it should! Now I open Mach, tell it to look for the G100 and it says Not Found!

I am going to ask Mariss if he can help.
Clockwork thanks for your support, I appreciate it!

Henk

[123CNC]

not a complete shot in the dark. the Rabbit handles the TCP/IP communications and Mariss could probably confirm or clarify, but I think there was a little history there with quality control issues from the Rabbit mfg and a few bad chips making there way into G100's. I thought I read it somewhere and perhaps a little conjecture as replacement or sole Rabbits were listed on their website for awhile (didn't see it more recently though).

Firsthand, it definitely cured my sick G-Rex. Still have the bad Rabbit, although my communication troubles were more intermittent.

[henkb]

Well things are looking better right now. Both the Grex-loader and Mach detect the G100 and communicate! Problem was the firewall. I disabled it and now things look much better. It really a pity there is no mentioning of this in the manual.

I expected to see the G100 setup menu appear in Mach but it didn't. So the question is what to do next? How do I get into the setup page for the G100?

Henk

[CoAMarcus]

Henk,

Try setting your subnet mask to 255.255.0.0 and an IP of 169.254.1.0. That should work, and make sure your firewall is shut off. I am going to be revising the G100 manual to reflect that a firewall can interfere with the operation of the G100.

Regarding the Rabbits, we did have a problem about a year ago. What happened was the switch to RoHS, and Rabbit had cold solder joints on some components. The situation has been rectified, and we have not had a single Rabbit problem for over 6 months.

Whatever problems you are having, it sounds like it is a software problem. Because the G100 is a fairly dumb piece of electronics, if it shows up on your computer then the hardware is working just fine.

-Marcus Freimanis