The EditorGT is probably the most integrated inkjet controller in the market. Reason being, that the tracker board, encoder boards and I/O-boards are all plug-in cards, everything in the PC !!!. For comparison: remember the tracker box of the Editor2, the big military connectors of an SR50 ?
But this miniaturization comes at the reasonable price of using standard connectors and cables.
Each I/O board has two 26pin D-SUB connectors that connect to the gray connection boxes through special cables.
Each encoder board has 2 encoder inputs with mouse-like connectors and 4 inkjet ports with Ethernet-like connectors RJ45. The user port receives print-go and encoder, and gives back print-done signals.
Pins on RJ 45:
1 Shaft Encoder or Motion or Tach (shaft encoder divisible by 2 to inkjet)
3 Print-go or Cue or Inkjet Trigger (tracked output from controller to inkjet)
4 Print-done or Print confirmation (from Inkjet to controller). Resistor !
7 VCC (it is very important to get the power either from controller or inkjet !)
Use the inkjet test unit (PN 83231) from Graph-Tech to determine or troubleshoot above signals. Please see also I/O converters in TechnicalManualiss3 in every controller and on GT’s FTP server.
Care has to be taken to connect the Ethernet cables coming from the inkjet user ports to the encoder board and NOT TO THE CPU Ethernet connector.
The CPU Ethernet chip gets destroyed if you do connect an inkjet cable coming from the user port !!!
The user port of Domino inkjets carries 12 VDC or 5 VDC depending on the jumpering inside the inkjet. Either way, by connecting an inkjet to the CPU Ethernet chip, the chip is destroyed because of this voltage.
There are 3 things you can do:
1. You never connect an inkjet cable to the CPU Ethernet. Easiest way.
2. If you did, you can exchange the plug-in CPU board.
3. You can buy an ISA (not PCI) Ethernet card (10-20 bucks), de-install the old drivers, load the drivers, and have the Ethernet from there.
Remember that you can always check an Ethernet connection by pinging another computer (if you know the IP number or PC name) from a DOS command shell:
· ping 220.127.116.11 <Enter> or
· ping cpserver <Enter>
If you get a reply, you’re good. If you get a timeout, you have a bad chip, cable, hub, etc.