PDA

View Full Version : C7000 not connecting to the controller


Custom Search


adeyemi
03-08-2020, 04:29 PM
The machine stopped connecting to the controller after an abrupt power failure. The controller (IC-413) was reloaded and tested fine on another machine. The memory control board upon which the controller data cable connects has been replaced. Data cable was replaced, the Overall Control board too replaced, still not connecting to controller.

Synthohol
03-09-2020, 02:08 AM
isnt there a bit switch to have it look for the fiery?
maybe it reverted?

methogod
03-09-2020, 10:45 AM
is there a mount kit that adapts the Memory Control board to the fiery? could be a fuse or something blown in that mounting bracket but is after the board you replaced.

also when you tested on another machine did you use the faulty machines fiery cable? or the known good???

seen cables fail and get damaged in a single remove and replace. (did it myself years back)

----

also after the above suggestions, i would make sure you don't have a fiery version conflict, if i remember the v1.0 was EOL and a windows 7 upgrade of 1.11.
If firmware is newer on the engine it may not see the OLD v1.0 version, i assume there is a version firmware that needs to be updated along with v1.11

just my two cents, let me know what you find...

adeyemi
03-10-2020, 10:11 PM
isnt there a bit switch to have it look for the fiery?
maybe it reverted?

No, Synthohol, i looked through every dip switch setting under systems setting, there none for the controller connectivity on C6000/7000. I know this exist for a C1070/C71hc, but not on a C6000/7000. Thanks

adeyemi
03-10-2020, 10:20 PM
is there a mount kit that adapts the Memory Control board to the fiery? could be a fuse or something blown in that mounting bracket but is after the board you replaced.

also when you tested on another machine did you use the faulty machines fiery cable? or the known good???

seen cables fail and get damaged in a single remove and replace. (did it myself years back)

----

also after the above suggestions, i would make sure you don't have a fiery version conflict, if i remember the v1.0 was EOL and a windows 7 upgrade of 1.11.
If firmware is newer on the engine it may not see the OLD v1.0 version, i assume there is a version firmware that needs to be updated along with v1.11

just my two cents, let me know what you find...

Thanks Methogod for your insights.
The data cable connector is directly mounted on the memory control board, no mount kit whasover. And yes, i tested with the same data cable to eliminate it. I would love to look into the software issue you mentioned and try to reload the machine firmware on the memory control board, not because i think it could be a version mismatch between engine firmware and controller firmware though. But because since it was working with this controller until the unfortunate event of an abrupt power failure, im thinking the power shut down could have caused a glitch and corrupted the firmware. I will get back on the outcome of this. Thanks

Synthohol
03-10-2020, 10:31 PM
hey, can you web into the fiery or at least see it in command workstation?
if its a bad video board in the fiery, i may have a couple. i usually toss them when i convert fierys into workstations.

adeyemi
03-11-2020, 03:34 PM
hey, can you web into the fiery or at least see it in command workstation?
if its a bad video board in the fiery, i may have a couple. i usually toss them when i convert fierys into workstations.
No, I don't think so, because the fiery worked on a different machine. And I also reloaded the machine image control firmware, it made no difference.

Synthohol
03-11-2020, 10:55 PM
hey, can you web into the fiery or at least see it in command workstation?
i dont care about the machine right now.
we are trying to see if the fiery is alive at all digitally.

adeyemi
03-12-2020, 09:08 AM
hey, can you web into the fiery or at least see it in command workstation?
i dont care about the machine right now.
we are trying to see if the fiery is alive at all digitally.

No I have not webbed into it or connect through CWS because these cannot be done until the IP address is set (I believe) and the IP cannot be set until it connects. But since it's connecting on another machine, I don't think the controller is the issue.

Synthohol
03-12-2020, 02:15 PM
if the fiery is functional it ALWAYS has an IP whether its 169.254.x.x 172..x.249.1 or the last static address.
i am just trying to follow a process of elimination but if you dont want to try my suggestions thats fine, i wont bother you anymore.
best of luck.

adeyemi
03-12-2020, 03:15 PM
if the fiery is functional it ALWAYS has an IP whether its 169.254.x.x 172..x.249.1 or the last static address.
i am just trying to follow a process of elimination but if you dont want to try my suggestions thats fine, i wont bother you anymore.
best of luck.

You don't seem to be getting me. I am saying I have tried the fiery on a different machine and it connected on that machine. But if I bring it back to this other machine upon which it was originally, it doesn't connect. Does that not eliminate the fiery enough??? Hope you get my argument this time. Thanks

Synthohol
03-12-2020, 04:53 PM
uggh, while its plugged into the trouble machine open CWS and see if it connects.
if there is a communication issue it will show the error in red in CWS.
use the last IP it was assigned or the search function.
may show "cable unplugged" or printing suspended or something that will help diagnose this.

adeyemi
03-16-2020, 06:58 PM
uggh, while its plugged into the trouble machine open CWS and see if it connects.
if there is a communication issue it will show the error in red in CWS.
use the last IP it was assigned or the search function.
may show "cable unplugged" or printing suspended or something that will help diagnose this.

I got an i-c306 with facci so that I could see feedback from cws. The controller boots completely and fully lunches cws. But it still doesn't connect to the machine, saying "establishing serial communication".

telip
09-01-2020, 11:02 PM
I see this is an old thread but can you check if your machine is an L...If that's the case you'll need a patch installed on your Fiery controller I order to be recognized from the machine.

Custom Search