Subj : Mbse co tick + hatch
To   : Gert Andersen
From : Vince Coen
Date : Thu Sep 12 2013 11:07 pm

Hello Gert!

11 Sep 13 19:31, you wrote to me:

 > There seem to be some bad by when mbse is hatch out files or something
 > other release files. When mbse hatch files out look it like that there
 > is some miss or error between .tic files and the file. I have checked
 > it out by hatch a file from my node 2 to my node 1. example is that
 > the files size is 444455 and in the tic have is the line size korrekt
 > with 444455, but when the file and tic is got to my node 1 and my
 > husky htick is trying import the file is the crc error between the
 > file and tic onfo. htick said that the zise of file wrong in the tic
 > file and it should be 00000000

 > The same is happen when I getting files from RJ Clay ad the file is
 > not been imported and processed.


Having checked with my uplink (Janis) there is no problems with the files I
have produced with mbse, e.g., the file size matches with the size given in 
the
tic file along with the crc values.

That includes rest of the tic file contents.

I suspect that the issue is with htick so :

1. Look at the files going into htick including the size and crc data
2. Check what htick is reporting in the log file/s
3. If needed increase the reporting level (full error data etc).
4. Change your processor, mbse handles it fine.

Regardless, the problem is with htick, heck it is very old code.


Vince

--- Linux/Mbse/GoldED+/LNX 1.1.5-b20120229
 * Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

.