Jerrold tech info Pt 2: DIY Data Logger Project
johnw...@my-dejanews.com
Here is part 2 of our information series on Jerrold cable boxes.
This is a DIY suitable project for those with moderate experience of
electronics / PICs.
The project is to build a data logger that will capture the outband command
channel data coming from either the Head End subscriber management system
controller or from any cubes / testchips attached to the cable box.
This data logger uses a PIC 16F84 (c84's will also work) to capture the
manchester encoded data from the output of the FSK radio receiver inside the
cable box. The PIC decodes the data and outputs it in PARALLEL format on the
PICs PORT B. This is then connected into the PC via the parallel printer port
and logged on the PC via the supplied software. Finally the PIC pulses the
Acknowledge line on the printer port triggering an interrupt telling the PC
to read the presented byte.
PIC Power supply / oscillator connection pinout :-
pin 4 (reset) connected to +5v
pin 5 (ground) connected to ground
pin 14(Vcc) connected to +5v
pins 15 & 16 connected to each of the pins on a 4 Mhz crystal
PIC to PC printer port connections :-
PIC pin 5 (Gnd) ---- > PC parallel printer port pin 25 (Ground)
PIC pin 18 (RA1) ---- > PC parallel printer port pin 10 (ACKnowledge)
PIC pin 6 (RB0) ---- > PC parallel printer port pin 2 (data 0)
PIC pin 7 (RB1) ---- > PC parallel printer port pin 3 (data 1)
PIC pin 8 (RB2) ---- > PC parallel printer port pin 4 (data 2)
PIC pin 9 (RB3) ---- > PC parallel printer port pin 5 (data 3)
PIC pin 10 (RB4) ---- > PC parallel printer port pin 6 (data 4)
PIC pin 11 (RB5) ---- > PC parallel printer port pin 7 (data 5)
PIC pin 12 (RB6) ---- > PC parallel printer port pin 8 (data 6)
PIC pin 13 (RB7) ---- > PC parallel printer port pin 9 (data 7)
PIC to Cable box connections :-
PIC pin 5 (Ground) This pin is connected to a suitable ground point inside
the cable box. The shielding cans on the inductors are suitable.
PIC pin 17 DATA INPUT. This pin is connected to the data output of the box's
FSK data receiver. This is the hardest pin to describe the connection for.
Inside the box is a data line that runs from the radio receiver output to the
control microprocessor. If you install a testchip then you break this line
and connect the testchip so that it feeds it's data into the microprocessor
instead of the radio receiver. What we are looking for is this data line.
The easiest way to find it is to look at how you would install a testchip for
your particular model of Jerrold box. Suitable diagrams can be found at a
number of testchip seller's websites
http://www.test-chip.com/i-dpv7.htm
has very good instructions for their testchips installation. The box's DATA
LINE is the point that they connect WIRE #2 to on their testboards. DO NOT
CUT THE DATA LINE AS THEY SAY IN THE DIAGRAMS - TESTCHIPS HAVE TO BLOCK THE
INCOMING DATA WE ONLY WANT TO READ IT !
NOTE: The above website is a COMMERCIAL COMPANY selling test chips THEY HAVE
NOTHING TO DO WITH THIS PROJECT, IT JUST HAPPENS THAT THEY HAVE GOOD DIAGRAMS
WHICH ILLUSTRATE THE CONNECTION POINT ON THE BOARD WE ARE LOOKING FOR. DO NOT
EMAIL THEM IF YOU HAVE ANY PROBLEMS - THEY WON'T HAVE A CLUE WHAT YOU ARE
TALKING ABOUT !!!
Two source files are included here. The first is the code that is programmed
into the PIC. The second is for the logging program that runs on the PC. The
PIC code is also supplied pre-assembled as a hex file suitable for direct
programming.
The PC logging program is written in assembly language and will need
assembling into a .COM file before use. A suitable assembler is MASM 5 or
later. The PC logger is designed to run in DOS however it WILL RUN QUITE
HAPPILY IN A WIN 95 DOS WINDOW. It will NOT work under windows NT as direct
hardware access is not possible.
The PC logger reads the data from the parallel printer port, THIS MUST BE SET
IN THE SYSTEM BIOS TO ADDRESS 0x378, IRQ 0x07, ECP ONLY MODE. IT WILL NOT
WORK IF THE PRINTER PORT MODE IS SET TO ECP+EPP NOR IF IT IS SET TO STANDARD
MODE. IF THE PRINTER PORT MODE IS SET INCORRECTLY THE LOG FILE WILL CONSIST
OF ALL ZEROS OR ALL 0xFFs.
When the PC logger is run it will simply display a hex count of how many
bytes it has captured. Once a minute it will save all of its memory buffer
onto disk, into a file called DATA.LOG in the current directory.
To QUIT the PC logger program press the RIGHT SHIFT KEY. This is the only key
that the program will respond to. DO NOT QUIT BY CLOSING THE DOS WINDOW UNDER
WIN 95 OR YOU WILL LOSE THE INFORMATION YOU HAVE LOGGED.
The output file (DATA.LOG) is a raw binary byte dump of the data received.
YOU CANNOT VIEW THIS FILE IN A TEXT EDITOR SUCH AS NOTEPAD ! YOU MUST USE A
HEX VIEWER. Suitable HEX editors / viewers may be downloaded from most
shareware sites. I suggest UltraEdit 32 as being very easy to use.
If the project is working correctly you will see the Counter on the PC logger
spinning rapidly ! This shows that you are logging data.
If you have a look at the output file (DATA.LOG) you should be able
to see the individual commands separated with groups of 0xFF's.
Remember the first byte of each command is the following length in bytes of
that command, and the last byte is the checksum.
Enjoy, Any problems feel free to email for help, we may be slow at replying
but WE WILL REPLY to anyone who asks for help.
John
Ben.
--------------- PIC 16F84 Data logger asm file starts ------------------
list p=16F84
radix dec
include "p16F84.inc"
__FUSES _CP_ON & _WDT_OFF & _XT_OSC & _PWRTE_ON
RA0 equ 0
RA1 equ 1
cblock 0x0C ;Store variables above control registers
delaycount ; delay loop counter
loopcount ; bit read loop counter
recv ;Receive data holding register
endc
org 0x00 ;Start of code space
goto start
nop
nop
;
; Support delay routines
;
delayhalfbit ;2+4+2+3w-1=34 cycles
nop
nop
movlw 9
movwf delaycount
halfbitloop
decfsz delaycount
goto halfbitloop
return
delayqtrbit ;6+3w-1=17 cycles
movlw 4
movwf delaycount
qtrbitloop
decfsz delaycount
goto qtrbitloop
return
; Main program loop.
;
;
start
bsf STATUS,RP0 ;Set up control register
movlw b'00000010' ;Set TMR0 prescaler = 1:8 (f_osc=4MHz)
movwf OPTION_REG ;/
movlw b'00000001' ;Port A, RA0 input, RA1-3 outputs
movwf TRISA
movlw b'00000000' ;RBn are all port B outputs
movwf TRISB
bcf STATUS,RP0 ;Back to normal
checkstart
btfsc PORTA,RA0
goto checkstart ; check RA0 for 0
waitforrise
btfss PORTA,RA0
goto waitforrise ; check RA0 for 1
call delayqtrbit ; 17 cycle delay
btfss PORTA,RA0 ; 18uS in to waveform,
goto checkstart ; check SA1 @ 1/4 through start bit
call delayhalfbit ; 2+34+18 cycles, 54 uS = 3/4 start bit
btfss PORTA,RA0 ; check SA1 @ 3/4 through start bit
goto checkstart
waitforfall
call delayhalfbit ; 2+34+54 cycles, 90 uS = 1 1/4 startbit
btfsc PORTA,RA0 ; check SA1 @ 5/4 through start bit
goto waitforfall
; REM'd to try to compensate for variation in start bit length
; call delayhalfbit ; 2+34+90 cycles, 126 uS = 1 3/4 bit cells
; btfsc PORTA,RA0 ; check at ZERO for D0 clock transition
; goto checkstart
movlw 9
movwf delaycount
alignloop
decfsz delaycount
goto alignloop
movlw 4
movwf loopcount
readbyte ; 2+27+2+126 cycles, 158 uS
movlw 21
movwf delaycount
rrf recv,F
bcf recv,7
btfsc PORTA,RA0 ; 157uS + 4 uS = 162 uS first time = 2 1/4 bit cells
bsf recv,7
nop
fullbitloop
decfsz delaycount
goto fullbitloop
decfsz loopcount,F
goto readbyte ; 72uS in loop
movlw 4
movwf loopcount
bcf PORTA,RA1
readbyte2
rrf recv,F
bcf recv,7
btfsc PORTA,RA0 ; 72uS to here entering loop confirmed
bsf recv,7
nop
movlw 21
movwf delaycount
fullbitloop2
decfsz delaycount,F
goto fullbitloop2
decfsz loopcount,F
goto readbyte2
movf recv,W
xorlw 255
movwf PORTB
bsf PORTA,RA1
goto start
end
--------------- PIC 16F84 Data logger asm file ends ------------------
--------------- PIC 16F84 Data logger hex file starts ------------------
:100000000F28000000000000000009308C008C0B5D
:100010000728080004308C008C0B0C28080083167D
:1000200002308100013085000030860083120518FF
:100030001728051C19280A20051C17280320051C51
:10004000172803200518212809308C008C0B26283E
:1000500004308D0015308C008E0C8E1305188E1711
:1000600000008C0B31288D0B2A2804308D00851060
:100070008E0C8E1305188E17000015308C008C0B1B
:100080003F288D0B38280E08FF3A860085140F286C
:02400E000100AF
:00000001FF
.386
--------------- PIC 16F84 Data logger hex file ends ------------------
------------------ PC data logger source code ASM ----------------------
; Compile to .COM file using MASM or TASM
target EQU 'M5' ; Target assembler: MASM-5.1
seg_a segment para public use16
assume cs:seg_a, ds:seg_a
org 100h
dlog proc near
start:
mov ah,3ch
xor cx,cx
mov dx,offset filename
int 21h ; create / truncate output log file
mov ah,09h
mov dx,offset startmsg
int 21h
mov word ptr dataoffset,0000
mov ax,ds
add ax,1000h
mov word ptr datasegment,ax
mov ax,350Fh
int 21h
mov int07hoff,bx
mov int07hseg,es ; save old int 07h ISR
push cs
pop es ; restore es from ds
mov ax,250Fh
mov dx,offset int07hisr
int 21h ; install int 7h ISR
in al,21h
and al,01111111b
out 21h,al
mov dx,037ah
mov al,00110000b
out dx,al ; set port to input, INT on ACK
;------------------ MAIN SAMPLING HOLDING LOOP ----------------
wait4sampling:
cmp fdreq,0
je nofileservice
call filedump
inc numbuffers
mov fdreq,0
nofileservice:
mov cx,dataoffset
cmp cx,dispsamp
je noupdate
mov ax,0e0dh
mov bx,0000
int 10h
mov cx,numbuffers
mov al,ch
call printhex
mov al,cl
call printhex
mov cx,dataoffset
mov al,ch
call printhex
mov al,cl
call printhex
mov dispsamp,cx
noupdate:
mov ah,02h
int 16h ; get shift status
and al,01 ; is right shift pressed ?
jz wait4sampling ; no, sit and wait
endsampling:
mov dx,037ah
mov al,00100000b ; disable int 07h in LPT1 PCR
out dx,al
in al,21h
or al,10000000b
out 21h,al ; disable int 07h in 8259 IMR
mov ax,250Fh
mov dx,int07hoff
mov ds,int07hseg
int 21h ; restore old int 07h ISR
push cs
pop ds
call filedump
mov ah,09h
mov dx,offset endmsg
int 21h
mov ax,4c00h
int 21h ; QUIT TO DOS
int07hisr:
push ax bx cx dx ds
mov dx,037ah mov al,00110000b ; port to input, IRQ enabled out dx,al
mov dx,0378h in al,dx ; read the printer port mov bx,word ptr
cs:dataoffset ; get current ptr index mov ds,word ptr cs:datasegment; get
current ptr segment mov byte ptr [ds:bx],al ; save byte into ptr
destination inc word ptr cs:dataoffset ; inc current ptr index cmp word
ptr cs:dataoffset,0ffffh jne endint ; if new dataoffset /= 0 quit int mov
word ptr cs:dataoffset,0000 mov byte ptr cs:fdreq,1 mov cx,ds mov
ax,cs sub cx,ax add word ptr cs:datasegment,1000h cmp cx,1000h je
endint sub word ptr cs:datasegment,2000h endint: mov al,020h out 20h,al
; Send nsEOI to 8259 PIC pop ds dx cx bx ax iret
proc printhex near
mov ah,al
shr ah,4
and al,0fh
add ax,3030h
cmp al,39h
jna allt39
add al,7
allt39:
cmp ah,39h
jna ahlt39
add ah,7
ahlt39:
xchg ah,al
mov dx,ax
mov ah,0Eh
mov bx,000
int 10h
mov al,dh
int 10h
mov al," "
int 10h
ret
endp printhex
filedump proc near
cmp fdreq,1
jne filenotservice
mov fileoff,0ffffh
mov ax,datasegment
mov fileseg,ax
add fileseg,1000h
mov bx,cs
sub ax,bx
cmp ax,1000h
je openfile
sub fileseg,2000h
jmp openfile
filenotservice:
mov ax,dataoffset
mov fileoff,ax
mov ax,datasegment
mov fileseg,ax
openfile:
mov ax,3d02h
mov dx,offset filename
int 21h ; open file
jc abortfile
mov bx,ax ; move file handle into BX
mov ax,4202h
xor cx,cx
xor dx,dx
int 21h
mov ah,40h
mov cx,fileoff ; number of bytes to write
mov dx,0000 ; zero offset of start of data buffer
push ds
mov ds,cs:fileseg
int 21h
pop ds
mov ah,3eh
int 21h
abortfile:
ret
endp filedump
; data segment starts here
fdreq db 00
filename db "data.log",0
fileseg dw 0000
fileoff dw 0000
startmsg db 13,10,"Number of bytes logged :-",13,10,"$"
endmsg db 13,10,"Finished logging, log file written.",13,10,"$"
numbuffers dw 0000
dispsamp dw 0ffffh
dataoffset dw 0000
datasegment dw 0000
delayflag db 00
int07hoff dw 0000
int07hseg dw 0000
dlog endp
seg_a ends
end start
------------------ PC data logger source code ends ----------------------
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
diesc...@painfully.org
>
>
>Here is part 2 of our information series on Jerrold cable boxes.
>
>This is a DIY suitable project for those with moderate experience of
>electronics / PICs.
code and hardware confirmed working. a little noise on the input but
thats easily fixed.
your turn Jim, lets see something.
John Wigley
diesc...@painfully.org wrote in article
<35f9b305...@news.indigo.ie>...
> On Fri, 11 Sep 1998 01:00:57 GMT, johnw...@my-dejanews.com wrote:
>
> >
> >
> >Here is part 2 of our information series on Jerrold cable boxes.
> >
> >This is a DIY suitable project for those with moderate experience of
> >electronics / PICs.
>
> code and hardware confirmed working. a little noise on the input but
> thats easily fixed.
>
Anybody else that's having problems with noise - which might manifest
itself as partially corrupted data - should just slap a 10K resistor across
the input pin and the ground pin.
> your turn Jim, lets see something.
Cheers for your positive feedback!
Bee.
John.
diesc...@painfully.org
<johnw...@my-dejanews.com> wrote:
>> >This is a DIY suitable project for those with moderate experience of
>> >electronics / PICs.
>> code and hardware confirmed working. a little noise on the input but
>> thats easily fixed.
>Anybody else that's having problems with noise - which might manifest
>itself as partially corrupted data - should just slap a 10K resistor across
>the input pin and the ground pin.
I was about to suggest a fix but as you got here first with a valid
solution, nuff said.
>Cheers for your positive feedback!
only being honest for all the others out there wanting to know who is
posting crap and who is telling the truth. so far its all one sided
and I`m not too happy about it either!
the reason being is that Jim keeps telling us all about some great
products but so far is unwilling to post anything here tangable which
certainly myself and others can take to bits and see once and for all
if his abilities are real or otherwise.
ok Jim, its up to you now. lets see something posted here in this
thread which tells us all you are indeed knowledgable.
magic...@magicboxes.com
Mr. Jerbust, your posting from Ireland, Jerbust happens to be in North Ireland
and run by John Wigley and Chris (whom has e-mailed me).
cable...@hotmail.com
eepr...@hotmail.com
johnw...@my-dejanews.com
stonec...@my-dejanews.com (must be the newest one)
your Jerbust message group (a forum to sell your chips).
What's the matter? Your not using your Jerbust dejanews posting service
anymore?
It's getting a little boring watching you poor souls make up new e-mail
accounts and post with John.
I am amazed, ever since John Wigley showed up in this news group on August
24,1998 a whole pile of his Jerbust buddies have created all kinds of messages
and posts from a variety of "new e-mail address sources" but all coming from
Ireland.
I realized you guys were hoping to have that market for yourself. Sorry. Your
prices were too high and your technology was not up to spec.
As for the data logger?
I would like some AMERICAN (not another Ireland Jerbust guy) company (who has
been around for awhile) to build the logger and test it in their area (or on
their headend). Like:
what:
Northwest, www.descramblers.com, www.descrambleit.com? Any takers?
The views here are totally from Jerbust and seem to NEVER have any seasoned
hacker in the western world. Interesting...
The data logger source code is pathetic. References to things that are not
used, constant resetting ports???,
look yourself:
fullbitloop
decfsz delaycount
goto fullbitloop
decfsz loopcount,F
goto readbyte ; 72uS in loop
movlw 4
movwf loopcount
No register reference after DECFSZ and some you do. (Compiler will pick 0
which ensures code will not work.
Noisy isn't the word for it.
I would like to see some posts from ACTUAL american companies who ACTUALLY
will build this device and HONESTLY report on their findings.
The whole parallel port??? Are you nuts??? You certainly are NO engineer.
Clearly shows you cannot design very well at all.
I send out my data loggers to dealers all over the US to collect data and
certainly don't send them an abortion like that.
I have ordered a Phantom cube, it will be here in a week or two. When I get it
i'll put up its dump and my logger design.
(a hint for my logger design).
Do you honestly think GI developed a SPECIAL UART just to read their own data
on the FSK stream?
Further Hint, in 1983 Jerrold Communications captured the data and processed
it with a standard 6850 UART (now they use a 6850 core in their custom chips)
with A SIMPLE CIRCUIT (unlike your design) manchester -> standard serial
bitstream totally compatible with ANY UART.
P.S. You are the same guys who asked me two weeks ago in EMAIL how to convert
frequencies to channel maps?? How to authorize PPV?? Your crap does fly
anymore. Still having problems with your test chips/cubes in UHF areas?
In article <35f9b305...@news.indigo.ie>,
diesc...@painfully.org wrote:
> On Fri, 11 Sep 1998 01:00:57 GMT, johnw...@my-dejanews.com wrote:
>
> >
> >
> >Here is part 2 of our information series on Jerrold cable boxes.
> >
> >This is a DIY suitable project for those with moderate experience of
> >electronics / PICs.
>
> code and hardware confirmed working. a little noise on the input but
> thats easily fixed.
>
> your turn Jim, lets see something.
>
>
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
diesc...@painfully.org
>And where did you come from?
Been here for quite a while.
>Mr. Jerbust, your posting from Ireland, Jerbust happens to be in North Ireland
>and run by John Wigley and Chris (whom has e-mailed me).
I know nothing of jerbust or the people who run the board.
>It's getting a little boring watching you poor souls make up new e-mail
>accounts and post with John.
I agree it does get a bit too much, but why are you now looking at me.
have I done something to you ?
I mearly asked that you post something which we can all take apart and
see if what you state is indeed fact. is that alone a reason for
changing the topic which by the way I and others are STILL waiting for
you to post. so do the right thing and do it now.
>I am amazed, ever since John Wigley showed up in this news group on August
>24,1998 a whole pile of his Jerbust buddies have created all kinds of messages
>and posts from a variety of "new e-mail address sources" but all coming from
>Ireland.
Many posts since John Wigley have been posted. but why ?
because you have never given an acceptable answer to anyones question.
you are correct that I have posted through an isp from Ireland. I
didnt think it makes much difference if I post through a US based one
or germany etc ?!
>I realized you guys were hoping to have that market for yourself. Sorry. Your
>prices were too high and your technology was not up to spec.
No jim, I am in no way involved with selling ANY type of cable
devices. I am here because of my technical interest in the subject, no
more.
>As for the data logger?
yes ?
>I would like some AMERICAN (not another Ireland Jerbust guy) company (who has
>been around for awhile) to build the logger and test it in their area (or on
>their headend). Like:
Yes I agree with you. here is an offer open to ANY well known company
who has knowledge in this area.
>Northwest, www.descramblers.com, www.descrambleit.com? Any takers?
Of the names you mention I only ever saw Northwest post here, so
perhaps they would do the honers ?
>The views here are totally from Jerbust and seem to NEVER have any seasoned
>hacker in the western world. Interesting...
My views are my own and I am an INDIVIDUAL!
>The data logger source code is pathetic. References to things that are not
>used, constant resetting ports???,
I never said the code was pathetic or otherwise, I mearly said that it
DOES work.
maybe you ought to post some of your own commented code for others to
look at.
>look yourself:
<snip>
Yes, Yes agreed. but lets not get distracted by trivial matters.
>Noisy isn't the word for it.
It is a noisey design as I originally stated. surely more than you
have seen that if they built the thing, which I have.
When you post some design I`ll build that too and give it the same
serious tests that anybodys design deserves.
>I would like to see some posts from ACTUAL american companies who ACTUALLY
>will build this device and HONESTLY report on their findings.
My report on this device IS HONEST!
Why dont you just built it and see for yourself.
>The whole parallel port??? Are you nuts??? You certainly are NO engineer.
>Clearly shows you cannot design very well at all.
The designer is best to answer that.
>I send out my data loggers to dealers all over the US to collect data and
>certainly don't send them an abortion like that.
Is that like your `jer stream` reader ?
want to post something on that perhaps ?
>I have ordered a Phantom cube, it will be here in a week or two. When I get it
>i'll put up its dump and my logger design.
Ok, we shall wait for a week or two and see who has designed the
better logger.
any other takers out there ?
>(a hint for my logger design).
>
>Do you honestly think GI developed a SPECIAL UART just to read their own data
>on the FSK stream?
no, doest make economical sense.
>Further Hint, in 1983 Jerrold Communications captured the data and processed
>it with a standard 6850 UART (now they use a 6850 core in their custom chips)
>with A SIMPLE CIRCUIT (unlike your design) manchester -> standard serial
>bitstream totally compatible with ANY UART.
>P.S. You are the same guys who asked me two weeks ago in EMAIL how to convert
>frequencies to channel maps?? How to authorize PPV?? Your crap does fly
>anymore. Still having problems with your test chips/cubes in UHF areas?
No Jim I have never mailed you. do note the non return mail address I
use. I know enough on channel mapping and PPV without having to ask
anybody. I also dont use any cubes or test chips becuase I have a
Satellite setup.
There may well be problems like you say in some areas. but its not of
interest to me.
johnw...@my-dejanews.com
diesc...@painfully.org wrote in article <35fbaf7b...@news.indigo.ie>...
> On Sat, 12 Sep 1998 18:18:09 GMT, magic...@magicboxes.com wrote:
>
> >And where did you come from?
>
> Been here for quite a while.
>
> >Mr. Jerbust, your posting from Ireland, Jerbust happens to be in North Ireland
> >and run by John Wigley and Chris (whom has e-mailed me).
Jim, You seem to be labouring under the misapprehension that I, Jerbust,
Chris, Cableitems, and maybe Diescammer are the same person and are trying to
form a UK cable cartel.
This is completely wrong, All of the above mentioned are DIFFERENT people,
although I know several of them. You have repeatedly demonstrated your
incomprehension by referring to cableitems (john) as asking for $2500 for the
automapper source code. I am in Southern England NOT Ireland, you are also
wrong about the location of several others though that is for them to correct
you if they see fit.
I am well aware that you can feed the data signal with a small amount of
translation into the PC's serial port and let its UART do the timing recovery
and decoding.
HOWEVER, The point of our design was to give people a starting point
for experimentation by providing code samples that people can use as a basis
for their own work. Simply providing a TTL to RS232 level shifter and a comm.
port logger would be absolutely no use at all for anyone wishing to design
their own devices.
You can take our receive routine and integrate it into a test chip, together
with the sample transmit routine in Pt.1, to provide a complete byte level
interface to the data stream in the test chip or cube.
Of course the code we posted is not the most elegant solution to a dedicated
data logger, but it is of far more use as a basis for experimentation which
was the overall point of the post.
Secondly IT WORKS which is AS YET more than can be said for any of Magicboxes
allegedly superior technology !
The noise is caused by high input impedance on the data input pins coupled
with the relatively high source impedance of the data line. Lowering the
input impedance with a resistor does cure almost all of the noise.
Oversampling as done by hardware UARTs would theoretically improve SNR but
empirically we have not found it neccessary. We have built several of these
designs, and when connected to valid data they work with a very low degree of
data corruption. In the devices we have built it is very rare to see a
corrupted byte in the output log.
John
< extraneous crap removed >
DamYankee
>snip
Thanks John it's refreshing to see some real info in the newsgroups
instead of the dribble coming from dealers who are only trying to sell
product.
I went to the magicbox site . All of Jim's files are nowhere to be
found unless he hid them, but judging from what limited info he does
have Your informatation is far more imformative and actually teaches
us something.
I don't have any exposure to jerrold equipment here. My experience is
with DSS and SA . I'm sure many of the same principles can be used for
the SA equipment if you have any more specifics or tips for SA it
would be appreciated.
Regardless your work is much appreciated and thank you
DamYankee
P.S. Jim put up or shut up!
magic...@magicboxes.com
Here, on magicboxes:
Before you waste your time on this SCAM (John Wigley and Chris)
Check out http://www.magicboxes.com/smellsbad.htm
(please re-load page if you have visted it before)
WE JUST RELEASED FULL T2 cube code with 2200 compressed commands!
We put on REAL FILES complete, working, commented, not like the shit these
scammers posted in news text.
John Wigley's code for the logger works VERY POORLY, and his source code is
incompilable. I won't insult your intelligence by posting such crap.
In article <35fbaf7b...@news.indigo.ie>,
diesc...@painfully.org wrote:
> On Sat, 12 Sep 1998 18:18:09 GMT, magic...@magicboxes.com wrote:
>
> >And where did you come from?
>
> Been here for quite a while.
Bullshit, your NEW address has just been posting to the newsgroups since
September 1,1998!
>
> >Mr. Jerbust, your posting from Ireland, Jerbust happens to be in North
Ireland
> >and run by John Wigley and Chris (whom has e-mailed me).
>
> I know nothing of jerbust or the people who run the board.
>
> >It's getting a little boring watching you poor souls make up new e-mail
> >accounts and post with John.
>
> I agree it does get a bit too much, but why are you now looking at me.
> have I done something to you ?
Nope, just looked like you were one of them. They spend alot of time creating
fake accounts to sell their $2500 test chip scam.
I got another engineer other than myself to build it and it had more errors
than GOOD! The thing is a piece of shit. If I put something that bad in my
test chips I would have to sell them for $2500 as well (as they would never
buy from me again).
>
> Of the names you mention I only ever saw Northwest post here, so
> perhaps they would do the honers ?
>
> >The views here are totally from Jerbust and seem to NEVER have any seasoned
> >hacker in the western world. Interesting...
>
> My views are my own and I am an INDIVIDUAL!
>
> >The data logger source code is pathetic. References to things that are not
> >used, constant resetting ports???,
>
> I never said the code was pathetic or otherwise, I mearly said that it
> DOES work.
> maybe you ought to post some of your own commented code for others to
> look at.
>
> >look yourself:
>
> <snip>
>
> Yes, Yes agreed. but lets not get distracted by trivial matters.
>
> >Noisy isn't the word for it.
>
> It is a noisey design as I originally stated. surely more than you
> have seen that if they built the thing, which I have.
> When you post some design I`ll build that too and give it the same
> serious tests that anybodys design deserves.
>
> >I would like to see some posts from ACTUAL american companies who ACTUALLY
> >will build this device and HONESTLY report on their findings.
>
> My report on this device IS HONEST!
> Why dont you just built it and see for yourself.
I did.
>
> >The whole parallel port??? Are you nuts??? You certainly are NO engineer.
> >Clearly shows you cannot design very well at all.
>
> The designer is best to answer that.
>
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
dude
> >certainly don't send them an abortion like that.
>
> Is that like your `jer stream` reader ?
> want to post something on that perhaps ?
>
didn't you guys see the logger I posted a few days ago, simplest one
I've
seen, requires nothing but a PC, no special hardware.
Far as I know this logger has been used for years all over the country,
could be that it is the one magic boxes uses? That is why he can't
post it, because it already has been claimed to be written by someone
else?
> >Do you honestly think GI developed a SPECIAL UART just to read their own data
> >on the FSK stream?
>
> no, doest make economical sense.
There are several manchester decoders that spit serial and parallel data
you can buy off the shelf that will decode the jerrold stream. Decoding
manchester is very easy with one of these chips since the manchester
signal provides the clock for these devices, if you use a seral version
of these chips you have to add a clock.
dude
Ohh by the way here is the sendbyte routine from the Group42 cube
code that has been floating around for a while. Very well documented.
; Set xtal speed here in MHz (ie. 8 for 8MHz, 12 for 12MHz,) this will
; set up the timing for the rest of the program
;
; Givin : 20 = 200ns, 10=400ns, 8 = 500ns, X=Yns, Then cycle time in ns
=
;
; 1/XTAL * 4000 = ns
;
XTAL equ .16 ;16mhz
;
; Calculate the processor CYCLE time in ns.
;
CYCLE equ .4000/XTAL
;
; Ok now lets calculate our manchester cycle time, we need a full and
half
; edge times of 70us and 35us, we subtract 3us off for fudge factor.
Since
; we use the RTCC timer and it's minimum prescale is 2:1 we must take
this
; into account ((.67/2)us for max RTCC out).
;
; Full cycle 70us-3us= 67us = (67us/2)/CYCLEns = FMCYCLE
;
FMCYCLE equ ((.68/2)*.1000)/CYCLE
; 35us - 3us = 32us or 20h us
HMCYCLE equ ((.33/2)*.1000)/CYCLE
;....
;--------------------------------------------------------------------
; Send Byte - This routine sends the byte in xmitbyte to the I/O
; port.
;
; manchester low-->hi = 1
;
; Send format example (send 5fh):
; 0 1111 1010 0 1
; ^ ^^^^ ^^^^ ^ ^
; St P Sp St=Start (always 0)
; f 5 P =Odd paraty
; Sp=Stop (Always 1)
;
; Clock:
; _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
; | |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_| |_|
;
; Data word: 5FH (Octal 137, bin 01011111)
; ___________________ ___
; ________| |___| |___________________________
; Data Frame:
; ____ ___________________ ___ ___ _______________
; |___| |___| |___| |___|
; Encoded data:
; ___ _ _ _ _ ___ ___ _ _ _ _ _
; |_| |___| |_| |_| |_| |_| |___| |___| |_| |_| |_| |_| |
; |T0 |T1 |T2 |T3 |T4 |T5 |T6 |T7 |T8 |T9 |T10|T11|T13|T14|T15|T16|
; St 1 1 1 1 1 0 1 0 OP Sp
; 0 1 1
;--------------------------------------------------------------------
Send_Byte_FF movlw 0ffh
Send_Byte movwf xmit_byte
;
; Send Start bit (0), we know that the data line is high and
; we want a high to low transistion, so wait for the next data
; transistion time and swing the I/O line low.
;
;;
Send_Start movf RTCC,W
subwf fmcycle,W
btfsc STATUS,CARRY
goto Send_Start
; swing data low
bcf Port_A, out_pin ; Set I/O port low
clrf RTCC ; reset RTCC counter to zero
;;
;
; Incerment checksum
;
movf xmit_byte,W ; get xmit byte to W
addwf checksum,Same ; add it into checksum
;
; Set parity Value to 1, for odd parity
;
clrf Parity_Val ; Set parity to one
incf Parity_Val, Same; (odd parity)
;
; Set the decesion flag to send parity next.
;
bsf d_flag,PARITY
;
; Send Data Byte
;
Send_Data movlw 8 ; 8 bits to be sent
movwf SCount
Send_Loop rrf xmit_byte, Same ; rotate bit right into carry
btfsc STATUS, CARRY ; check if we should send a Zero
goto S_One ; or One
S_Zero
;;;
btfsc Port_A, out_pin ; check I/O for current status
goto HiLow0
; We are currently low, and want a hi to low transistion, so
; do a transition at mid point to set up a hi to low at the
; next data transistion time.
LowHi0 movf RTCC,W
subwf hmcycle,W ; Half Manchester cycle
btfsc STATUS,CARRY
goto LowHi0
; swing data hi
bsf Port_A, out_pin ; Set I/O port Hi
;
; We are currently hi, and want a hi to low transistion, so wait
; until next data transison time and swing I/O line low.
;
HiLow0
movf RTCC,W
subwf fmcycle,W ; Full Manchester cycle 70ns
btfsc STATUS,CARRY
goto HiLow0
; swing data low
bcf Port_A, out_pin ; Set I/O port low
clrf RTCC ; reset RTCC counter to zero
Z_Ret
;;;
goto S_Next
S_One
incf Parity_Val, Same; Incerment parity value
;;;
btfsc Port_A,out_pin ; check I/O for current status
goto HiLow1
;
; We are currently low, and want a low to hi transistion,
; so wait until next data transison time and draw the I/O line
hi.
;
LowHi1 movf RTCC,W
subwf fmcycle,W ; Full Manchester cycle 70ns
btfsc STATUS,CARRY
goto LowHi1
; swing data hi
bsf Port_A, out_pin ; Set I/O port hi
clrf RTCC ; reset RTCC counter to zero
O_Ret
goto S_Next
;
; We are currently hi, and want a low to hi transistion, so
; do a transition at mid point to set up a low to hi at the
; next data transistion time.
;
HiLow1 movf RTCC,W
subwf hmcycle,W ; Full Manchester cycle 70ns
btfsc STATUS,CARRY
goto HiLow1
; Swing data low
OutWait2 bcf Port_A, out_pin ; Set I/O port low
; wait tell next data tranistion and swing data hi
goto LowHi1
;;;
S_Next decfsz SCount
goto Send_Loop
;
; determine whether to send parity, stop or bail
incf SCount
btfsc d_flag,PARITY
goto Send_Parity
btfsc d_flag,STOP
goto Send_Stop
clrwdt
Send_Byte_Ret retlw 0ffh
;
; Send Parity Value
;
Send_Parity clrf d_flag ; clear the decision flag
bsf d_flag,STOP ; set send stop bit next
btfsc Parity_Val,LSB ; See if we should send a one
or zero
goto S_One ; Send a one
goto S_Zero ; or send a zero
;
; Send Stop Bit (1)
;
Send_Stop clrf d_flag ; clear the decision flag
goto S_One ; send stop bit(1)
;...
magic...@magicboxes.com
DamY...@fcmail.com wrote:
> johnw...@my-dejanews.com wrote:
>
> >snip
>
> Thanks John it's refreshing to see some real info in the newsgroups
> instead of the dribble coming from dealers who are only trying to sell
> product.
His information was crap.
His source code was UNCOMPILABLE.
He is a dealer trying to get $2500 for test chip source code. Jerbust (John
Wigley, Chris) put together a SCAM message board to put out their products.
I have NOW made available a FULLY FUNCTIONAL WORKING CUBE using the NEWEST
technology available.
I am NOT going to insult you the way they did uploading non working code in
text format - making it almost impossible for anyone to try.
Our files are complete, real, and commented.
Check our Technology Awareness section today.
The source code, and hex files are provided as a file, not text.
P.S. Did you notice that John Wigley NEVER put any of his code in an
attachment? Why? It won't work.
Jim Borden
http://www.magicboxes.com
>
> I went to the magicbox site . All of Jim's files are nowhere to be
> found unless he hid them, but judging from what limited info he does
> have Your informatation is far more imformative and actually teaches
> us something.
>
> I don't have any exposure to jerrold equipment here. My experience is
> with DSS and SA . I'm sure many of the same principles can be used for
> the SA equipment if you have any more specifics or tips for SA it
> would be appreciated.
>
> Regardless your work is much appreciated and thank you
>
> DamYankee
>
> P.S. Jim put up or shut up!
>
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
diesc...@painfully.org
>Bullshit, your NEW address has just been posting to the newsgroups since
>September 1,1998!
well aint that interesting, you have the worlds first e-mail address
tracking system too ?
it must be truely amazing to be able to tell an old e-mail address
from their new one....wow I`m impressed!
I suppose I`d better post through dejanews now too ?
get real, nobody believes that crap!
>> >It's getting a little boring watching you poor souls make up new e-mail
>> >accounts and post with John.
>>
>> I agree it does get a bit too much, but why are you now looking at me.
>> have I done something to you ?
>
>Nope, just looked like you were one of them. They spend alot of time creating
>fake accounts to sell their $2500 test chip scam.
I said I was not and yet you still want proof ?
Again I`ll state it very clearly.
I DO NOT SELL, PRODUCE OR DESIGN FOR ANYONE!
I AM NOT AFFILIATED WITH JERBUST.
its these damn scams which keep on comming in here make my blood boil.
wild claims made by fools for fools.
>> Yes I agree with you. here is an offer open to ANY well known company
>> who has knowledge in this area.
>>
>> >Northwest, www.descramblers.com, www.descrambleit.com? Any takers?
>
>I got another engineer other than myself to build it and it had more errors
>than GOOD! The thing is a piece of shit. If I put something that bad in my
>test chips I would have to sell them for $2500 as well (as they would never
>buy from me again).
So you agree with me that even though its `shit` it does work ?
I`ll await your design here in a few weeks and we shall see your handy
work. I`m not getting into an argument over chip prices, thats best
left to the people who know of it such as you and the jerbust people.
>> My report on this device IS HONEST!
>> Why dont you just built it and see for yourself.
>
>I did.
have any other desiginated (by you) american companies expressed an
interest in building it for you ?
magic...@magicboxes.com
> >September 1,1998!
>
> tracking system too ?
> it must be truely amazing to be able to tell an old e-mail address
> from their new one....wow I`m impressed!
I actually used dejanews under power searhc. Tyored in your e-mail address.
You have only been posting to messages involved with Jerbust since September
1,1998.
Let me guess, you just got on the internet and become instantly interested in
Jerbusts discussions right?
>
> I suppose I`d better post through dejanews now too ?
>
> get real, nobody believes that crap!
>
> >> >It's getting a little boring watching you poor souls make up new e-mail
> >> >accounts and post with John.
> >>
> >> I agree it does get a bit too much, but why are you now looking at me.
> >> have I done something to you ?
> >
> >Nope, just looked like you were one of them. They spend alot of time creating
> >fake accounts to sell their $2500 test chip scam.
>
> I said I was not and yet you still want proof ?
> Again I`ll state it very clearly.
>
> I DO NOT SELL, PRODUCE OR DESIGN FOR ANYONE!
> I AM NOT AFFILIATED WITH JERBUST.
Good. If you don't sell the stuff then I appologize for implying that you did.
Jerbust has used many fake accounts and yours has only been used in the
newsgroups since September 1,1998.
>
> its these damn scams which keep on comming in here make my blood boil.
> wild claims made by fools for fools.
>
> >> Yes I agree with you. here is an offer open to ANY well known company
> >> who has knowledge in this area.
> >>
> >> >Northwest, www.descramblers.com, www.descrambleit.com? Any takers?
> >
> >I got another engineer other than myself to build it and it had more errors
> >than GOOD! The thing is a piece of shit. If I put something that bad in my
> >test chips I would have to sell them for $2500 as well (as they would never
> >buy from me again).
>
> So you agree with me that even though its `shit` it does work ?
No it doesn't work. If I made a test chip that turned on one channel would you
consider it working ? No.
We have a REAL problem in the states with a 3-wire automultimode chip that
POORLY reads data like the Jerbust/John Wigley reader does. Every time it
misreads a disconnect packet it ALLOWS it to go through (A lot of CFT boat
anchors out there). Using code like John Wigleys' is useless as it reads more
wrong than right.
John made his code purposefully difficult for end-users to deal with in these
news groups. I have contacted a few delear and some are building it and some
won't becuase of the headaches with building it.
I had another engineer build it from the post and his results were worse than
mine. On mine I could at least make out soem of the data some of the time.
Users would be better off stuffing the data line DIRECTLY to their serial port
on their computer in procomm and hope to see some fluke data.
> I`ll await your design here in a few weeks and we shall see your handy
> work. I`m not getting into an argument over chip prices, thats best
> left to the people who know of it such as you and the jerbust people.
>
> >> My report on this device IS HONEST!
> >> Why dont you just built it and see for yourself.
> >
> >I did.
>
> have any other desiginated (by you) american companies expressed an
> interest in building it for you ?
>
I have built it. Yuck.
All I ask is before ANYONE consider buying from John Wigley or Jerbust they
build the Data logger and try it themselves. After they build it they will get
an idea of the kind of quality to expect in their test chips - none.
diesc...@painfully.org
>I actually used dejanews under power searhc. Tyored in your e-mail address.
>You have only been posting to messages involved with Jerbust since September
>1,1998.
Yes, since dec 1 using this address only, you suggested that I had a
previous address too. which is not the case.
>Let me guess, you just got on the internet and become instantly interested in
>Jerbusts discussions right?
No quite the opposite in fact, I have become so fed up with reading
total bull posts including all the scam merchants out there that I
though it a good idea to show in public who knows ther stuff and who
is just talking bull.
All tech matters on cable interest me, regardless of who posted the
original.
>> I DO NOT SELL, PRODUCE OR DESIGN FOR ANYONE!
>> I AM NOT AFFILIATED WITH JERBUST.
>
>Good. If you don't sell the stuff then I appologize for implying that you did.
Thank you.
>Jerbust has used many fake accounts and yours has only been used in the
>newsgroups since September 1,1998.
Well I am not going to speak for others on their posting habits, it is
only a fluke that mine appeared then. after all it was when all this
crap strated flying!
>> So you agree with me that even though its `shit` it does work ?
>
>No it doesn't work. If I made a test chip that turned on one channel would you
>consider it working ? No.
No not working fully as we all know. but giving credit where credit is
due, the posted code does work, admittable it aint perfect but is a
start.
You will post your design for disection wont you ?
>We have a REAL problem in the states with a 3-wire automultimode chip that
>POORLY reads data like the Jerbust/John Wigley reader does. Every time it
>misreads a disconnect packet it ALLOWS it to go through (A lot of CFT boat
>anchors out there). Using code like John Wigleys' is useless as it reads more
>wrong than right.
Unfortunatly I have not got this 3 wire chip you mention, but
certainly the posted code would not work at all well in a situation
like that.
>John made his code purposefully difficult for end-users to deal with in these
>news groups. I have contacted a few delear and some are building it and some
>won't becuase of the headaches with building it.
I am not getting into a mud throwing match here, but I do agree it is
far from perfect. it should be treated only as a starting point.
Commerically it would be a disaster to use it in its current state.
>I had another engineer build it from the post and his results were worse than
>mine. On mine I could at least make out soem of the data some of the time.
Some reasonable data came out of mine, but I had gone to extra lengths
such as extra resistors and using shielded cable etc. it did cure some
of the noise but not enough.
>Users would be better off stuffing the data line DIRECTLY to their serial port
>on their computer in procomm and hope to see some fluke data.
Thats really not a good idea, dedicated software could be used to read
form the serial port but not procomm!
magic...@magicboxes.com
I designed a GI data logger 6 years ago. It uses on pic running at 8Mhz. It
connects between the RS232 port and the Jerrold. I wrote a program which
captures the datastream, processes it, and saves/displays it in a text
readable file. Using a 16550 UART I am able to save as it goes along. Many
times I have logged my system for days (until I got my own headend). My
program sets up the uart at 13888 baud (Actual GI rate), 14400 works as well
on some cubes/systems. It never makes a mistake as the manchester data is
just converted on the fly to serial data.
I never used the 1-wire parallel port Jerbust logger. I found it garbage as
it has to lock up the PC and can only save so much. I could never understand
why anyone would develope a logger to work on a parallel port when its clear
to see the data is in a standard 8,e,1 configuration. Simple manipulation of
the manchester data (Xilinx app can do it in 3 macrocells) creates a data
format ANY computer can read.
>
> >We have a REAL problem in the states with a 3-wire automultimode chip that
> >POORLY reads data like the Jerbust/John Wigley reader does. Every time it
> >misreads a disconnect packet it ALLOWS it to go through (A lot of CFT boat
> >anchors out there). Using code like John Wigleys' is useless as it reads more
> >wrong than right.
>
> Unfortunatly I have not got this 3 wire chip you mention, but
> certainly the posted code would not work at all well in a situation
> like that.
>
> >John made his code purposefully difficult for end-users to deal with in these
> >news groups. I have contacted a few delear and some are building it and some
> >won't becuase of the headaches with building it.
>
> I am not getting into a mud throwing match here, but I do agree it is
> far from perfect. it should be treated only as a starting point.
> Commerically it would be a disaster to use it in its current state.
>
> >I had another engineer build it from the post and his results were worse than
> >mine. On mine I could at least make out soem of the data some of the time.
>
> Some reasonable data came out of mine, but I had gone to extra lengths
> such as extra resistors and using shielded cable etc. it did cure some
> of the noise but not enough.
>
> >Users would be better off stuffing the data line DIRECTLY to their serial
port
> >on their computer in procomm and hope to see some fluke data.
>
> Thats really not a good idea, dedicated software could be used to read
> form the serial port but not procomm!
I was kidding. I do however recommend using Commchk. Its a shareware app which
monitors the serial port and saves as it goes along (without dropping any
bytes). I used it in initial development.
http://www.magicboxes.com
Jim Borden