Need help with ADA Mach IV! - Page 2

i had the same problem and finally figured it out. You have to replace the last three digits by 255 on the gateway configuration. so if your ip address of the rhapsody is 192.168.1.199 then in the gateway you need to say 192.168.1.255. Problem solved for me. i think irules needs this to indicate udp port vs tcp/ip port.

Give us a screen shot of how you entered a command in irule. Showing the command on the left side.

Do you see green arrows on the bottom left hand side every time you hit a button on irules? if they are red, or nothing, then you are still not connecting or you are not sending the right command, but if they are green then you are transmitting correctly. On the bottom right hand side, there should be a green icon for the gateway. it it is yellow, then it did not connect to some of your gateways. if it is red, then it connected to none.

make sure you are sending the right command on the button you are sending. Once I got a green connection to the gateway, the Mach iv started responding right away. It did take a reboot of the mach iv though...

is your HD Suite software talking to the Mach IV with total feedback too?

I had to change my mask to 255.255.255.255 (on iso-e) to make this work with the same settings you have.

Rock on!

Finally!!!

ah the power of search. this thread just helped me to connect via iRule. So thanks guys!
Now to get feedback set up and to get the SuiteHD software to work again (it can't connect after changing my Suite 7.1 HD's IP settings with the ISO tool

NaTT , glad to hear your problem solved , that prompts me to solve mine and I need help from members here .

I have a Suite HD 7.1 1.4 for almost 8 months and despite how hard I tried - despite all that I read from forum on this same subject - I still cannot speak to my Suite - I am not that proficient on this subject . I installed all necessary ADA software on XP - Service pack 2 and installation is successful but whenever I try to open the software , it indicates "ADA Ethernet - WSAIoct1 failed 0 " and I cannot even speak to my Suite . I set my Suite from the front and control my Suite through Harmony 1000 . I have given up as it costs me a lot of time by trial & error .

I wish to ask for help as following ; I now want to turn on TEQ but that can only be done from PC , so I wish I can solve this problem with helps from members .

And if that is beyond my capability to work through , I would like to know ;

I have WiFi running 24 hours , I can connect a Lan cable from my Suite to the TP - Link router , I have iPads that is WiFi connected , not yet ordered i-Rule , I need to know if it is possible for me to control my Suite only with this availability - no PC talking to my Suite .

I only need a better remote than my Harmony 1000 , iPad is ideal to me .

Helps and advice appreciated .

Larry

so what are you saying Natt, can you not connect to the ADA via the PC suite program since using the ISO tool?

I too am struggling to connect via ISO-e program on a hardwired network. When I run that program, with both my laptop and the ADA on the exact same hub, and find devices it returns:

Internal Ethernet card is 192.168.1.244 with subnet of 255.255.255.0

Found ADA of 255.255.0.0 with address of 169.254.255.255

When I use ISO-e to reprogram the ADA I give it a subnet mask of 255.255.255.0 and an address of 192.168.1.254. I know from my router's devices table that 254 is empty/available.

(ps -- I can connect directly using a cross connect cable, but not via my ethernet network)

The ADA never shows up on my network, even after a reboot. I tried both Windows 7 64 bit and XP on two different laptops.

What's odd is that after using ISO-e, if I use a cross connect cable again, the ADA shows the original address, indicating the new address never got written.

Any suggestions?
Edited by Brucemck2 - 12/9/12 at 1:50pm

I too struggled. Read from post 1781, it may help? http://www.avsforum.com/t/1196455/ada-mach-4-wow/1770#post_22347891

It seems that everyone are/were having problems in setting up their ADA to talk to PC , I too struggled with no success and I have given up . Reading threads does help to understand what could be wrong but to those just with general knowledge , it is still not easy . ADA's software could be made more user friendly , why not an built in VNC like MC ? Just do not understand why ADA do not work to improve on this , it shouldn't be difficult for ADA .

MC is also intended for professional installation but an novice like me can still got it installed within several hours with satisfactory result and no reason why ADA couldn't achieve the same !

Larry