NI3000 ICSNet Failure
hodeyp
Junior Member
in AMX Hardware
Hi,
I have just had my NI300 repaired after it was damaged after a power surge.
I am no longer able to connect netlinx devices over the ICSNet connection, nothing seems to be recognised.
Whilst I await technical supports response, does anybody know if there are diagnostic commands that will confirm if the is still a hardware fault?
Thx
Phil
I have just had my NI300 repaired after it was damaged after a power surge.
I am no longer able to connect netlinx devices over the ICSNet connection, nothing seems to be recognised.
Whilst I await technical supports response, does anybody know if there are diagnostic commands that will confirm if the is still a hardware fault?
Thx
Phil
Comments
-
Is really no device found on ICSNet in the online tree or by "show device" from terminal?
Depending on what was repaired, the devices maybe are just resetted to the dynamic range >32000 -
i'm afriad there is no sign of the devices in the SHOW DEVICE tree. I have tried setting the dip switched on the NXF-MINI to various addresses with no success.
I'm hoping this isn't another return to factory - beleive it or not it took a month last time... -
maybe new firmware or something?
-
good suggestion - I have tried the latest duet firmware and also the last of the non-duet firmware and still no joy.
Sounds like another trip back to the factory
-
Maybe the ICSNet port in your other devices got taken out at the same time as the 3000? I.E., the 3000 might be fine?
- Chip -
I had some problems with the ICSNet connections recently while upgrading from a Landmark system. Have you tried connecting just a single device to NI-3100 to see if it shows up? Some of my problems were due to a faulty ICSNet Hub, and some of the devices did not show up without the appropriate module being installed.
Which devices are you connecting to via ICSNet?
Jeff -
Sadly, I had a similar issue when an NI-3000 took a lightning hit. It was stone dead, and I sent it in for repair, but when it came back, though the master was working, about half my ports on the chassis itself were still dead, and it had to go back again.
Someone has to ferret out that one tech who isn't doing complete system tests on repaired units ...
-
good point again, any idea if I can chack for this without sending all the units back to AMX to test?
-
I'll chip in too. I had the same problem as Dave. Surge hit my 3000, so I pulled it out and replaced it with a 2000 to keep the client limping, and all my ICSNet devices worked fine (through a CF-10 yet!); but when I put the repaired 3000 back in...no ICSNet joy at all.
Jeff
Leave a Comment
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums