WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Do you have any information on this type of files .cad and .fab ?

Do you think that it is possible to extract and try to read with another viewer.
It would seem unisoft and fabmaster would be the only ones to do this work maybe?
it might be easier to retrieve the right information

https://www.unisoft-cim.com/pcbview.php
https://smtnet.com/company/index.cfm...mpany_id=41319

I think you have already done research on this side

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Oh gee, all of this for a few strings… Nice teamwork!

Agreed, that one was a bit disproportionate.

I've been going back over your python dump_tvw code and migrated a lot of stuff in to my C decoder and things are starting to come together (sadly the whole pins/parts on the boardview won't really happen until right at the end ).

ie, here's a dump so far of what I've got with the B562.tvw file ( managed to get the nets out on this one ).

Still some issues with parsing on more complicated boards with different pad options / types and still haven't worked out the block of data after the nets but before the part:pin definitions (with all the probe data).

[mmu]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Oh gee, all of this for a few strings… Nice teamwork!

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

NOW it's fixed....

Header 1: 'O95w-28ps49m 02v9o.' => 'Tebo-ictview files.'
Owner: 'G5u9k8s' => 'Landrex'
Password: 'B!Z@6sob' => 'G!G@byt3'
Date: 'Eksq dc, beeh' => 'July 21, 2016'

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

SUCCESS!!! Finally. That was fiddly.

The key was that digit (plain) to encoded you have to use 3-rotate, but for alpha (plain) use 10-rotate.

EDIT: okay, not *quite* success yet, the date is wrong... should be July 26, 2016 :sigh:

Header 1: 'O95w-28ps49m 02v9o.' => 'Tebo-ictview files.'
Owner: 'G5u9k8s' => 'Landrex'
Password: 'B!Z@6sob' => 'G!G@byt3'
Date: 'Eksq dc, beeh' => 'July 21, 2908'

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

I have confirmed that it should read "Teboview-ict file" ( O95w-28ps49m 02v9 ). With that knowledge I will now try fix my algorithm

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Based on your technique, it appears that there's 10 columns total for the normal letters; I'll code this up and see how it goes then.

exactly, we saw it at the same time

@paul :look your mp sometimes

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

Oh very smart!

ssssssssssssss = nmlkzyxwvu_nmlk
______________12345678910_1234

you notice that after 10th it starts again

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

I force the number of characters to have the rest of the decoding

Based on your technique, it appears that there's 10 columns total for the normal letters; I'll code this up and see how it goes then.

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

I force the number of characters to have the rest of the decoding

Oh very smart!

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

How did you do this conversion?

The mapping I have now ends after 8th

	 { 'n', 'm', 'l', 'k', 'z', 'y', 'x', 'w' }, // 's'

I force the number of characters to have the rest of the decoding

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

ssssssssssssss = nmlkzyxwvunmlk

look 9th

How did you do this conversion?

The mapping I have now ends after 8th

	 { 'n', 'm', 'l', 'k', 'z', 'y', 'x', 'w' }, // 's'

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

ssssssssssssss = nmlkzyxwvunmlk

look 9th

my decoder is bad
s : n m l x z y x w

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

The decoding is fine until the 9th character; ie, we decode 'Y960v50n' to 'December' correctly but something changes in the algorithm after the 8th char and I'm not sure what yet.

I'm not modifying the code in the file, I'm trying to make my decoder function correctly convert 'O95w-28ps49m' to 'Tebo-ictview' based on an assumption that that is what the header *should* be decoded as.

Right now we get the first 8 characters right if I don't increase the rolling-index for the '-' ( ie, only increase for 0-9, a-z, A-Z ), but the algorithm still breaks after the 8th character and interestingly there's no mapping from a 's' encoded char to a 'v' output (closest is 'k' input for rolling-index zero (0).

However after that char, the rest of the letters are then 1 index too far ahead.

Maybe the header string isn't meant to be decoded to "Tebo-ictview" but it seems like it would be a natural thing given that we have "Tebo-ict" for the first 8 characters of decoded string.

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

If I modify my decoder, and make it so it keeps rolling with the rolling index on a '-', we start to see => Header 1: 'O95w-28ps49m 02v9o.' => 'Tebo-ictnjfu ehodv.'

if you change this, the program no longer recognizes the filename and therefore does not accept it, yes it designates the type of files

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

continuous rotation in relation to the number of characters

zzzzzzz = u t s r q p o
zzzzzzzzzz= u t s r q p o n m l

I saw that I made mistakes in the decoding

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

If I modify my decoder, and make it so it keeps rolling with the rolling index on a '-', we start to see => Header 1: 'O95w-28ps49m 02v9o.' => 'Tebo-ictnjfu ehodv.'

Which makes me think that the first part there should be Tebo-ictview, not Tebo-ictnjfu, because if you look iat it, "njfu" is actually close to "view" as the last 3 letters are one letter too advanced, jfu => iew; so that makes me think that it should be Tebo-ictview... best I go fix my decoding system

int TVW_decode_string( char *dest, char *s, ssize_t l ) {
	ssize_t i = 0;
	int r = 0; // roll position
	while ( i < l && *s ) {
		if (isalnum(*s)) {
			dest[i] = TVW_dec[(ssize_t)*s][r % 8];
			r++;
		} else if (*s == '-') {
			dest[i] = *s;
			r++;
		}
		else {
			dest[i] = *s; 
			r=0;
		}
//		r++;
		i++;
		s++;
	}
	dest[l] = 0;
	return 0;
}

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

So far all the sequential, unbroken strings are decoding correctly that I can ascertain, though they don't contain numbers ( decoded ).

Two things I need to clarify are;

1) Does the rolling index halt, or reset (to zero) when a non-alpha/numerical character is encountered in the string? ( I'm strongly suspecting a reset to zero )

2) Are the numbers being correctly decoded ( probably just have to go through many files and see statistically what the decoding results are. Lower value (0~6) seem okay but there might be an issue with 8~9 :shrug:

[Maxpower3]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

others chars not coded ,I would rather be sure

i will look for the dates

[inflex]

Re: WANTED: Teboview / TVW file format specification to write OpenBoardview decoder

ha I was wrong , happy if that can help you

Some of the dates are coming out strange; not sure if that's because they're using a different calendar (non-Georgian) or the data isn't being decoded right.

ie, I'll get "October 89, 3899" or similar