misio' original message at bottom.

I have used the "Realiser" by (actum solutions) on SGS Thomson 626x
parts; this is available with a windoze fishy logic package, sim-u-orta'
and kit programmer.

The realizer also has an excelent simulater with on screen probes. I do
not know what performance can be expected for the Realiser on PIC parts,
but I had a play with it and was able to put together a sliding
door/access control/PIR/magic eye/fire etc interface
in a concept to instaled and running PCB time of 2(two) days(ST62T60). I
also tried it on multiplexed 7-segment displays which proved a little
flickery (due to the ST6xxx very slow instruction execution speed.) I
can recomend the Realiser for SGS Thompson parts at least.  cd rom
available from arrow components NZ $13.00, "ST62 MCU family oct 1997"
(SGS Thomson subsidised price !?)

note that if you are performing custom coms applications or any other
very high speed inteligent algorithms then assembler is tops but at a
much increased programming time penalty.

PIC
I use WMOVF and WMOVL macros to take much tedium out of file to file and
literal to file transfers, also a BTG macro for bit inversions. I have
no In Circuit Emulator for Pics, but I get by with 3 to 5 eprom parts
for which ever part I am developing. By using lots of comments, big
descriptive variable names and descriptive address labels even on non
jump locations, also making tested portions into include files, i am
able to keep my bugs feeble. When I get a nasty it generally falls into
one of two categories:
1) crash: program stuck due to a jump destination error.
2) wrong results: unexpected/unwanted variable

usually these error types can be classified quickly and easily, in the
first case one or more pins can be set/cleared at key "check points" and
externally tested with LED or piezo(my number 1 & 2 test tools). if it
is a category 2) bug then my application has probably got some form of
coms routines in it already ie LCD/Infrared/RS232 and so I can utilise
this to output my problem number. On ocasion when I have had a realy bad
bug with multiple choice variable processing sections leading to a
common point from different locations i have defined a test variable and
written different values into it at the different program locations and
then output this via a coms routine.

I recently made a test application for the low-end motorola MC68HC05J1A
to put it through it's paces; if anyone is interested in a small PCB
with 6 x 7-seg display, DS1820 temperature sensor, tacho to approx
50KHz, 6 dig counter then reply by private  email. I am making
tacho5dg.pcb , .asm and .s19 available as freeware. uses 675 bytes of
the 1240 byte eprom on board.

misio wrote:
>
> On my CD Rom that came with Picstartplus there was a part about third party
> software and hardware.
>
> One of them Was "The Realizer" from Actum company from Netherlands.
>
> Does anybody have any experience with it?
>
> Michal Gluszczak
> Studio 7
> Slubica Dobra 2
> 96 311 Skuly
> POLAND
> tel. +48 602 623 301
> studio7@kki.net.pl
> http://www.kki.net.pl/studio7
> We connect to internet once a week, so please be patient waiting for reply.