vennerig
Hi there,

Last year I got a hold the this data logger and was able to use it very successfully for a project. However, I ran into an issue that led me to re load code onto the LLB and have since had difficulty sending a setup. I want to know what I'm doing wrong as I get the codes loaded on the LLB successfully but still cannot seem to send a setup to the LJB successfully. 

I get this message from Pi Server when trying to send a setup:

Load Data - LJB node 0x1F does not have its internal monitor block (block ID 200) available for use by Workshop. This may cause problems.

I've been told to clean out workshop’s FSR & setup cache to see if that fixes the problem, but I'm not familiar on how to do that.

Any suggestions on how to conduct a sound troubleshooting procedure for this software related issue?

Any help would be appreciated.

Thanks,

-Giuseppe

Below is my box info from DeBug and Pi Server:

Card Type : MPC 8240
OS Version : Epsilon 110 (Release) May 02 2007
Boot Version : 8245 Boot Loader 1.01 Nov 04 2004
Application : Logger 8245 LLB
Build Date : Thu May 29 11:19:26 2008
Build Stamp : 0x483e832e
Card Id : 0x00000002

Card Type : MPC 8240
OS Version : Epsilon 110 (Release) May 02 2007
Boot Version : 8245 Boot Loader 1.01 Nov 04 2004
Application : Elite Application
Build Date : Thu Jul 26 20:38:07 2007
Build Stamp : 0x46a8f81f
Card Id : 0x0000000a

Card Type : LJB 565
OS Version : Delta 312 (Release) Jan 05 2006
Boot Version : 565 Boot Loader 2.10 Jan 14 2005
Application : Not Loaded
Card Id : 0x0000001f

----------------------------------

Properties: LLB\Logger

Location: 2
Node: 0x2
BuildDate: 29 May 2008 (03:19.26)
BuildStamp: 0x483E832E

NOS V1.0
CLS II V1.2
DIS V4.1
DRV V5.12
EDL V1.20
ELB V1.9
ENV V1.23
ESI V1.2
EVG V1.10
EVL V1.26
EVW V1.2
LCM V1.37
PidB V1.0
PDL V1.36
SWH V2.4
TEL V1.8
TTL V1.4
RTC V1.5
VID V1.0
ADR V2.1
CAN V0.0
CRC V2.1
FDL V1.1
FIU V2.2

----------------------------------------

Properties: LLB\Application Card

Location: 10
Node: 0xa
BuildDate: 26 July 2007 (12:38.07)
BuildStamp: 0x46A8F81F

No additional information

------------------------------------------

Properties: LJB

Location: 31
Node: 0x1f
BuildDate: No Code.
BuildStamp: 0x00000000

No additional information

Quote 0 0
NealB
Hi Giuseppe,

It looks like you don't have code loaded onto the LJB,

Card Type : LJB 565
OS Version : Delta 312 (Release) Jan 05 2006
Boot Version : 565 Boot Loader 2.10 Jan 14 2005
Application : Not Loaded
Card Id : 0x0000001f

the best way to load this is via debug direct to the LJB. The process of sending the .bin file is the same as the LLB code loading. Just make sure the switch on the debug lead is in the correct position.

The clear the dataset cache you can go to "System" - "Configuration" in Pi Server and select the "Dataset Messages" tab and use the "Delete Dataset Cache" to clear this.

Regards,
Neal


Quote 0 0
vennerig
Thanks Neal,

My next question is which .bin file on the LJB?

the setup.bin?


below is the flash data of the LJB through Debug:

 >iflash

0. 00000000. BOOT SECTOR                     : Loaded

1. 00080000. MANUFACTURERS SECTOR   : Loaded

2. 00090000. FPGA SECTOR                     : Loaded; Sigma LJB Card 603204

                                                             : Rev 2.3  Fri Jan  7 16:11:38 2005

                                                             : CardType 204, Pinout 1

3. 00010000. OS SECTOR                        : Loaded

4. 000C0000. APPLICATION SECTOR         : -



-Giuseppe



Quote 0 0
NealB
Hi Giuseppe,

The LJB code will be specific to your application, if you have a setup that has been used with the code you will be able to find out the LJB code version used. If you go to "Sigma Configuration" in Workshop and select the LJB in the setup, the Build Stamp of the code should be displayed. The file will be a .bin and the size is normally around 14kb. If you don't have the file and it was build by Cosworth I should be able to find it for you.

Regards,
Neal
Quote 0 0
vennerig
Thanks Neal,

I looked at the Build stamp for LJB Code Builds left in "set code build"  memory and saw this:

Build Stamp: 0x4a5f880f
Build Date: 16 Jul 2009

Can you check if you have this .bin file in your inventory?

This .bin file can only be loaded through debug right? Not workshop?
Quote 0 0