Itech address

Mike Diack

Mike Diack

Sophomore
Jan 12, 2011
135
0
16
New Zealand
I don't own any itechs, but as a repairperson, I see lots of broken ones. My problem is having fixed one, I like to run it via System Architect to check the network functions and here's where the difficulty lies. Inevitably SA detects the iTech but won't connect, and makes me put a new ip address in my PC. Then it works. This takes time. I feel like I'm cycling around the same few ip addresses. Is there any way around this ?.
M
 
Re: Itech address

Mike Diack said:
I don't own any itechs, but as a repairperson, I see lots of broken ones. My problem is having fixed one, I like to run it via System Architect to check the network functions and here's where the difficulty lies. Inevitably SA detects the iTech but won't connect, and makes me put a new ip address in my PC. Then it works. This takes time. I feel like I'm cycling around the same few ip addresses. Is there any way around this ?.
M
Click to expand...

That is the way most IP devices work. DSPs-amps etc.

Yes a pain-but just part of the "process".

If there is an easier way around-I would like to know it also-so that when I get to the office I don't have to change it again.
 
Re: Itech address

Mike Diack said:
I don't own any itechs, but as a repairperson, I see lots of broken ones. My problem is having fixed one, I like to run it via System Architect to check the network functions and here's where the difficulty lies. Inevitably SA detects the iTech but won't connect, and makes me put a new ip address in my PC. Then it works. This takes time. I feel like I'm cycling around the same few ip addresses. Is there any way around this ?.
M
Click to expand...

If you connect both your computer and an amp to a router with DHCP enabled, all devices will automatically get an IP in the same range and work fine.

If you do not connect either to a router and do not manually assign a static IP, then both devices will default to a static IP in the 169.254.x.x on the 255.255.0.0 subnet, and should work fine. It may way take a while for the devices to 'give up' on getting a DHCP IP.

If you assign a static IP address manually anywhere, then all other static IPs on the network have to be on the same subnet as well for the devices to see each other.

Your best bet is just buy a cheapo router and use DHCP.
 
Re: Itech address

My guess is you meen that you get amps from clients that have static IP addresses on them and don't have the DHCP feature enabled?

If that's the case then on the HD series you have a Networking menu on the front panel DSP that you can just enable DHCP and let the amp ask for an IP address so SA will find the itech on its own. If you have older, non HD series amps, you need to make sure you have firmware over version 2.0. Now let system architect find the amp first using READDRESS DEVICES from the TOOLS tab. Then it will ask you if you want to enable DHCP, when you press yes then the amp will reboot and the next time it's up it will try to find a DHCP server and get an IP address from it. I'm pretty sure you already have a DHCP server on your local worshop network unless you have a special configuration for some reason.

You need to take into consideration that you might be deleting user configuration of the static IP that was there before.
 
Last edited:
Re: Itech address

Sounds like you're doing it right (the op)

When I had issues and called Crown, theu had me readdress my pc, connect to the amp, then readdress the amp, the re-readdress my PC back to it's starting address.

Don't think there's a faster way.

HyQnet NetSetter makes readdressing the amp possible once ip addresses have th initial characters
matching.

(sorry about my ipad typing)
 
Last edited:
Re: Itech address

Steve Hurt said:
I bought a couple used i-Tech 4k's. Ststem Architect would not find them. Caled Crown. They had me download HyQnet Netsetter. With it i was able to see the IP address on the ITechs. I then had to change my netbooks IP address to match the first number of characters (the last numbers have to be unique to the device). Once I had one that, reboot and retry with Syetem Architect. It now found the amps. Then you can use NetSetter to change the ip address in the amp. After that, I changed the computer's ip address back.

Obviously, I am limited in my nerworking knowledge, and my explanation is probably missing steps you'll need. Just trying to say that this is not an uncommon issue and it is fixable. Call Crown and talk to tech support. My amps are out of warranty, but the tech support guy said: "We made them, we're not going to leave you hanging". Spent over an hour on the phone. No charge and got both amps working.

(sorry about my ipad typing)
Click to expand...

Well, in reality, it's not an issue, it's just how it is. IP networks have a subnet, and all devices on the network have to be on the same subnet to talk to each other.

This is why the first couple numbers need to be the same - the exact number of numbers that need to be the same is determined by the subnet mask. For instance, 255.255.0.0 means that the first 2 numbers have to be the same, and the last 2 numbers are allowed to vary, and they can vary in the full 1-254 range. If the subnet was 255.255.255.128, the first 3 numbers would need to be the same and the last number would have to be different for each device, and could vary from 1 to 127.

This is why a router is SO much easier. Just set everything to DHCP and forget about it!

The faster way is to not attempt to run Static IPs for your entire network and just use DHCP. Then you don't have to switch back and forth every time you use your computer for amps and for other things.

Also, if everything is DHCP, you can run much more than just amps on the network. At a show, I link all my computers, all my amps, all my UHFR, everything that can be networked gets connected so I have full control of everything from anywhere. It just makes sense once you get comfortable with it.
 
Last edited:
Top Bottom