Re: One-stitch pattern uploaded - initial analysis
- I see that you are very advance in your project. I looked into forth
several times and it is a very powerful language. I never understood
why wasn't it picked up over C, but now I recall it was because of
documenting; forth is difficult to read if the programmer did not
I wrote couple of emails to different places and gor responce form
one that they are looking into helping us out. We'll see.
--- In email@example.com, "John R. Hogerhuis" <jhoger@p...>
> On Tue, 2004-11-30 at 06:42, mikezcnc wrote:got
> > It is a very interesting way of poking into the code and you've
> > great results.did
> Reverse engineering is a lot like science. You gather data (like I
> in this case), form hypotheses, and gather more data to test/verifythe
> hypothesis.and I
> > From what you are saying, you are using linux-is there
> > a reason for it other than personal interest?
> Well freedom is the #1 reason. Linux is not under monopoly control
> can change or fix any of the software because all of the sourcecode is
> But generally I run only Linux on my network because it is a
> secure, powerful OS and thousands of high quality Free Softwareprograms
> are available for download at places like SourceForge.net andboxes.
> Freshmeat.net. I run the Debian GNU/Linux distribution on all moy
> Furthermore there is no knitting software for these machines that
> under Linux. So any work I do on this platform could be picked up bybut
> someone else.
> I can run Windows stuff, and I do professional Windows development,
> I run it on W2K under VmWare.Disk
> > How are you getting
> > code-by connecting a FB100 to a PC and taking it from there.
> Well I have a laptop with two serial ports (one is a USB<->Serial
> adapter). One is connected via null modem adapter + Tandy Portable
> Drive (TPDD) cable to the km. The other is connected via TPDD cableto
> the Brother FB100 disk drive.passes
> I have a 'snooper' serial analyzer program that I run. It just
> traffic between the two ports and lets me view the data. I can savelogs
> of that, but they are ASCII text.the
> So to write the data I run
> snooper -b9600 /dev/ttyS0 /dev/ttyUSB0
> I have written a little bit of Forth code that lets me do a read of
> data just as the KM would.type
> So to read the data I run gforth test.fs and once at the prompt I
> READ-SECTOR. This runs a Forth script that reads the sector andwrites
> it out to disk as a binary file.cable
> I'll post this code soon just in case someone finds it useful.
> To really make this work though you need at least one TPDD or DAK
> and a KM.code
> I think there is a version of gforth for Windows. If not my test
> could be adapted to any modern Forth interpreter.how
> > Does
> > FB100 have any controls on it or is just that, an FDD. If so then
> > do you get data out of it? Just curious about your test bed.them
> Just a FDD. I write commands to it over its serial link and read
> via the serial link. These are fairly odd disk drives in that theyhave
> a serial interface rather than a parallel type of interface.a
> > Have you considered using Tandy 100 and Basic interface to use as
> > controller, since FDD connects to Tandy, as you have found out?the
> Yes some of my testing has been to use a Tandy 102 with short BASIC
> programs to try things out.
> > I was thinking of using a logic analyzer on the knitter I/O.
> Yep. In fact you could hook it to the processor bus and watch all
> instructions and we could actually trace execution that way.analyzer
> But for the serial port I'd suggest using a hardware serial protocol
> analyzer or a laptop with two serial ports and serial protocol
> software as I do. Otherwise you'll waste a lot of time setting up a
> logic analyzer to trace a serial link.
> -- John.
- On Tue, 2004-11-30 at 10:46, mikezcnc wrote:
> I see that you are very advance in your project.Well I have a setup for analysis, that's about it. If anyone can think
of good experiments to do, let me know and I'll report the results.
> I looked into forthI mostly just use Forth for prototyping. Basically forth "words" can be
> several times and it is a very powerful language. I never understood
> why wasn't it picked up over C, but now I recall it was because of
> documenting; forth is difficult to read if the programmer did not
> include comments.
stacked like Legos. You end up making a lot of very simple words that
can be strung together at the interpreter prompt to do more complex
stuff. So it's very useful for interactively trying things out, in order
to get a feel for the protocol or hardware you are dealing with.
It is probably more useful in embedded systems contexts, particularly on
constrained systems (8 or 16 bit CPUs or microcontrollers with very
I tend to rewrite the final application in C.
>Cool! Keep us apprised.
> I wrote couple of emails to different places and gor responce form
> one that they are looking into helping us out. We'll see.