RJC

E6000 Console - Downloading + Memory Size RJC 03/10/13

Introduction:
We are quite frequently asked questions about the prospect of upgrading an E6000 Console
and/or how to determine what is necessary etc. Consequently, I have attempted to write a
standard script that covers most things; if some of this does not apply in your circumstance
then please bypass/ignore accordingly.
Please be aware that this is intended as a ‘general purpose’ overview and that we will still
attempt to answer any direct questions/queries.
The E6000 Knitting Machine was actually made by a company called Madag and effectively
‘badged’ with Passap or Pfaff!
Historical Facts:
Before going into any detail it is sensible to outline some basic history and facts about the
E6000 Console. Please appreciate that the dates included here are from personal memory and
may not be correct.
When launched in approx. 1988 the E6000 consoles had been designed to work with the
E6000 Knitting Machine components and little else. The possibility of employing an external PC
was not considered and hence the electronic design did not include an accessory serial data
communications port; also @ this date the physical size of semiconductor memory components
was limited and prices reflected this so only an 8 Kilobyte SRAM was employed.
Over the next few years, little changed for the E6000 Console other than the occasional
upgrade of its internal firmware (Program Chips) as particular program bugs were determined
and fixed.
In the early 1990’s Madag issued the Creation 6 Software Application – an MS-DOS based
package intended for use on x86-based personal computerson – the forerunners of today’s
typical PC running a modern version of Windows ©.
This software provided the user with the ability to make and store patterns on a local computer
and then when convenient ‘download’ them to the E6000 console. This launch also
necessitated a new issue of Program Chips for the E6000 Console as a serial data
communications port was now necessary. Although no dedicated hardware within the E6000
Console existed this was achieved by employing what is often referred to a ‘firmware uart’.
In about 1992 the most recent E6000 Console was launched; basically identical to the original
but now fitted with SRAM (memory chip) of 32 Kilobyte capacity. This change again required a
new issue of Program Chips.
No further serious changes were made to the E6000 Console unit from this date until its last
firmware update in 1995, presumably soon after this date manufacture of the E6000 ceased.
For reference, not including language difference, there have been a total of 6 issues of
firmware for the E6000 console. The Program Chips (Muster and Program) typically include a
10 digit sequence on their label (may also include ‘.’s as a separator) and the 1st 2 of the last 5
digits normally refer to that issue. Issues are:
03, 13, 23, 33, 43 & 53. Issue 23 relates to the ability to accept downloads and 33 and above to
the 32K capability. It should be appreciated that 33 and above are what might be considered
‘backward compatible’ – they will work fine in either the 8K or 32K SRAM hardware
environment (which is not the same). (note 33+ for 4600 53 for Form6)

Page 1 of 4
 RJC
E6000 Console - Downloading + Memory Size RJC 03/10/13

Use of Serial Numbers:

One approach to determine the age of your E6000 Console and its capabilities is to look at its
Serial Number. This however is not a reliable or definite indication of its status, simply as many
‘old’ consoles have been updated in various ways over the years and there is typically no
external indication of this. It is not unusual for us to see a very early console, but on internal
examination display the ‘guts’ of a much more recent one where it was ‘once’ updated by a
dealer etc. Theoretically:
If your Serial Number is anything below 6025980, when originally manufactured it was fitted
with Program Chips incapable of accepting downloaded patterns.
If your Serial Number is anything below 7037001, when originally manufactured it involved an
internal PCB only capable of employing an 8K SRAM.
If your serial number is higher than 7037000 then you almost certainly have a 32K unit that is
capable of accepting downloads. The version of firmware fitted will be .33 or above.
Internal Examination:
Again in theory, if you take the back of a console and display the internal PCB you can examine
what chips are fitted etc and determine its status. In practice this will not a definite indication of
its status, although better than the Serial Number approach. We have seen older, than
expected Program Chips fitted into units and 8K SRAM chips fitted where 32K is expected!
There are descriptive details of the difference of appearance between a ‘production’ 8K and
32K PCB, but again this is not a definite indication of status.
Download Test:
To determine if an E6000 Console is capable of downloading, the best thing to employ is a
simple download test which effectively employs the fitted firmware to carry out particular
operations related to downloading. If it cannot do these then it almost certainly is not fitted with
suitable Program Chips! This test is detailed in a later section.
Memory Capacity:
The most definite test to determine this is to download a sequence of identical patterns into the
E6000 – when the display indicates an ‘memory overflow’ error then the limit has been
reached. Unfortunately however this can only be carried out with an already download capable
console + download cable + PC etc.
One typically correct estimate is the Serial Number - If your serial number is higher than
7037000 then you almost certainly have a 32K unit.
Another option is to open the unit and examine the number upon the SRAM chip – although this
will not always indicate what the actual console is capable of, it should display what is actually
fitted. Details of this are detailed in a later section.
Is it Possible to Upgrade My E6000 Console:
The ‘good news’ here is that (in our experience) any E6000 Console that was ever
manufactured can be ‘upgraded’ to the latest standard!
The ‘not so good news’ is that the upgrade that you want may not be something you can do for
yourself!

Page 2 of 4
 RJC
E6000 Console - Downloading + Memory Size RJC 03/10/13

A large number of E6000’s in the field are from the early builds and are consequently 8K units
that are incapable of downloading @ present. These can easily be upgraded by the user, or
their associates, by simply replacing the original Program Chip set with one of the correct issue.
An 8K unit can be suitably upgraded by replacing 03 or 13 issue Program Chips with 23, 33, 43
of 53 issue Program Chips.
We, for example, at a reasonable cost supply users with the latest issue 53 Program Chips pre-
fitted with carriers and full instructions on how to fit etc.
It is also possible to upgrade all 8K units to become 32K ones – but this is not so easy! When
the E6000 was still supported dealers used to achieve this by replacing most of the ‘insides’ of
an ‘old’ unit with a replacement/new 32K PCB etc – and charged accordingly.
Today however, there are few dealers or components still available and consequently 10 years
ago I examined the situation and documented a method of actually modifying an 8K unit to
become a 32K one. This method has now been employed by a number of people around the
world, for example we in the UK have upgraded over 100 units this way.
This upgrade however involves quite a bit more than changing the Program Chips; from
experience we have seen that many who consider themselves capable of such work are
certainly not. Neglecting the necessity to employ a soldering iron, modify the PCB and similar
any minor mistake made can cause a failure and rectifying such often requires both a technical
understanding and test equipment. Consequently we cannot recommend that the user or their
associates try to implement this upgrade themselves
E6000 Download Capability Test Process:
This simple procedure will enable the user to determine whether their E6000 Console is fitted
with firmware capable of downloading data from PC applications such as Creation 6, Designer
Knit, Win_Crea or Journal 6.

Remove the DIN cable connection from the E6000 Console’s integral DIN socket mounted
upon the top left hand edge (when viewed from the front).

Power up the E6000 Console and if PROGR is not immediately displayed after a brief period
then select this display by manipulation of the keys.

When PROGR is displayed, press the ENT key. This will cause ERASE to be displayed.

Press the ENT key and a flashing CAST ON will be displayed.

Press the 3 key followed by ENT key and ALL & ST.PATT will be displayed alternately.

Press the NO key and a flashing ST.PATT A will be displayed.

Press the ‘UNMARKED’ key followed by the 0 key and the result will indicate the Console’s
capability.

If the result is a constant alarm tone and ERROR 213 upon the display then the unit is fitted
with firmware capable of downloading. (note press of ‘UNMARKED’ should result with a
response/beep in an updated unit)

Page 3 of 4
 RJC
E6000 Console - Downloading + Memory Size RJC 03/10/13

If the result is an alternating ST.PATT A and 0 upon the display, or some other error other than
213, then the Console is fitted with an early version of the firmware and will not accept
downloads.

E6000 Console and 8K or 32K Memory SRAM Chip:

The early E6000 Consoles were manufactured to include an 8K volatile memory, whereas the
later models include a 32K (4 times 8K) one.

The size of this memory is completely irrelevant to the unit’s download capability.

In most circumstances, memory capacity is not of great importance. The 8K memory size is
capable of holding considerably large patterns/designs and applications, such as DAK7, which
are capable of downloading such excessive patterns in stages or sections anyway.
One method of determining what size of memory is fitted within an E6000 Console is by
removal of the rear cover and examination of the contents.

a) The 28 pin IC above the PROGRAMM EPROM is the component of interest. This is a low
power SRAM and part of its identification number will indicate the size:
e.g. the 64 within 8464A-10L indicates 64 thousand bits or 8K bytes – or – the 256 within
D43256AC -10L indicates 256 thousand bits or 32K bytes.

b) An original, unmodified PCB capable of 32K has a small diode in close proximity to the Pin 1
end of the MUSTER EPROM.

c) MADAG PCB ARTWORK numbers alone are not a definite indication of the unit’s capacity!
An 8K unit cannot simply be upgraded/converted to a 32K unit my replacement of the SRAM!
A 32K unit cannot simply be downgraded/converted to an 8K unit my replacement of the SRAM!

What is the difference between an 8K & 32K E6000 Console?

This is something that is worth explaining as the figures/terms are misleading and it is important
for users to understand exactly what they have or want!
The 1st confusing factor relates to what memory components are fitted to what the total
memory capacity actually is. Yes 8K units are fitted with an 8K SRAM and similarly 32K units
are fitted with a 32K one. BUT the electronic design is such that, at most, only 3/4 of the 32K
chips can be physically addressed – hence 24K NOT 32K!
Secondly, for some reason the firmware has been written in such a way that the actual
difference in ‘pattern storage space’ between the 8K and 32K/24K is below the factor of 2.5 –
the 24K figure now looking more like only 20K!
The 32K unit has the capacity to store a single maximum sized pattern download (180 st wide *
255 rows long using 4 colours) whereas the 8K requires such a pattern to be spilt into two
sessions. However with smaller patterns this is no real problem – to test this capacity we
employ a pattern of 104 st wide * 180 rows long and 2 colours – an 8K unit can accommodate 4
of these, whereas a 32K unit can accommodate 10 of them.

Page 4 of 4