Bentley Instruments

All Support Posts for ‘’ Category

Software

IBC user interface program (Win7) -> BACTOCOUNT IBC VERSION 0.1.7.x

IBC user interface program (prev release) -> BACTOCOUNT IBC VERSION 0.1.6.3329

IBC user interface program (prev release) -> Bactocount IBC version 0.1.6.2959

Firmware revision used in the Autosampler -> Autosampler version 2.0E

Firmware used in the Piezo driver -> Sonicator 2.0C

The embedded software when using the new piezo driver -> Embedded 3.5.0.C

The license security key for Windows 7-64 bit -> Security key – win 7

 NOTE: Before updating your system, consult with a local Bentley Service point as some systems are not hardware compatible with the current deployment of our new custom Piezo driver.

Posted in Uncategorized | No Comments »

Fatty Acid Calibrations for NexGen software v2.15+

 Note: To load these calibration files, the instrument must be running v2.15 or greater of the Bentley NexGen software

Component  Units  Range Comments  File
Free-Fatty Acids (FFA) mmol/L 0.1 – 0.58 N=444       PLS FFA2 28Apr14
Monounsaturated Fatty Acids (MFA)  % 0.3 – 1.9 N=1575 PLS MFA2 28Apr14
Polyunsaturated Fatty Acids (PFA)  % 0.05 – 0.24 N=1541 PLS PFA2 28Apr14
Saturated Fatty Acids (SFA)  % 1 – 4.5 N=501 PLS SFA2 28Apr14
Saturated Fatty Acids (SFA)  % 1 – 4.5 N=1038 PLS SFA3 28Apr14
Unsaturated Fatty Acids (UFA)  % 0.4 – 2.2 N=1545 PLS UFA2 28Apr14
Palmitic Acid (PA, C:16:0)  % 0.4 – 2.3 N=1565 PLS PA2 28Apr14
Stearic Acid (SA, C:18:0)  % 0.1 – 0.78 N=1546 PLS SA2 28Apr14
Oleic Acid (OA, C:18:1)  % 0.22 – 1.48 N=1557 PLS OA2 28Apr14
Omega3 FA % 0.008 – 0.074 N=674 PLS OM31 1May14
Omega6 FA % 0.03 – 0.37 N=674 PLS OM61 1May14

Posted in Uncategorized | No Comments »

How To create a custom warning message

Hi

Starting with revision 2.14.5136 It is possible to create and manage a completely custom warning system. To initialize this feature you need to manually edit the database table “Warnings” and add a record to this table with the “Code” field set to the number 1001 (which internally is used to identify this warning).

 Warnings Table

Once this is done, the custom SQL can be created. You can create/edit the SQL and place it in the column “longMSG” . 

Once initialized, the options dialog under warnings will include a field showing the SQL – double click this field to edit/view the code.

Options Dialog User Warning

 

This SQL can take many forms – the following is a simple limit check on a protein reading

DECLARE @protein double;
SET @protein = (SELECT C2 FROM Samples WHERE [index]=:paramSampleIndex);
IF(@protein<2.50)THEN 
    SELECT 'Range Error' as "TitleMessage", 'Value of Protein is less than 2.50' as "Message" FROM System.IOTA;
ELSEIF(@protein>4.50)THEN 
    SELECT 'Range Error' as "TitleMessage",'Value of Protein is more than 4.5' as "Message" FROM System.IOTA;
ELSE
    SELECT '' as "Message", 0 as "Code", False as "Stop" FROM System.IOTA;
END;

 

In the above SQL there are several special requirements that must be met 

  • SET @protein = (SELECT C2 FROM Samples WHERE [index]=:paramSampleIndex); — selects the current sample and returns the Protein value to the local variable

The first condition in the error message compares the protein value to a fixed value of 2.50 

  • IF(@protein<2.50)THEN 

The most important is to return a result in the proper format in order to show the warning 

  • SELECTRange Error‘ as “TitleMessage”, ‘Value of Protein is less than 2.50‘ as “Message” FROM System.IOTA

It is important to use the single and double quotes exactly as shown. The “Message” will show as the longer message in the error message and the “TitleMessage” will be displayed as the title of the warning. The samples in the main display will get a question mark on the icon, and when double clicking the sample the error messages will show as

Range Error Example

 

 

A second example would test the sample identification and only test the result if the sample has a specific id. The example is created as the above and shows the added logic in bold.

DECLARE @protein double;
DECLARE @sampleid varchar(80);
SET @protein = (SELECT C2 FROM Samples WHERE [index]=:paramSampleIndex);
SET @sampleid = (SELECT SampleID FROM Samples WHERE [index]=:paramSampleIndex);

IF (UPPER(@sampleid)=UPPER('HELLO')) THEN
    IF(@protein<2.50)THEN 
        SELECT 'Range Error' as "TitleMessage", 'Protein is less than 2.50' as "Message" FROM System.IOTA;
    ELSEIF(@protein>4.50)THEN 
        SELECT 'Range Error' as "TitleMessage", 'Protein is higher than 4.5' as "Message" FROM System.IOTA;     
    ELSE         
        SELECT '' as "Message", 1 as "Code" FROM System.IOTA;     
    END; 
ELSE    
   SELECT '' as "Message", 0 as "Code" FROM System.IOTA; 
END;

 

The next example is from a BactoCount IBCm where the desired effect is to have a warning only apply to a specific batch type or product as in the IBCm. The example is for an SQL which will single out the samples tested under product number 133 (133 is the index in the batchtypes table).

DECLARE @sidx integer;

DECLARE @product integer;
DECLARE @ibc double;
SET @sidx = :paramSampleIndex;

SET @product = (SELECT BatchTypeIndex FROM Samples JOIN Batch ON Batch.TestOrder=Samples.BatchIndex WHERE [index]=@sidx);
SET @ibc = (SELECT C27 FROM Samples WHERE [index]=@sidx);

IF (@product=133) THEN
    IF(@ibc<30)THEN
        SELECT ‘Range Error’ as “TitleMessage”, ‘ibc count is too low for this product type’ as “message” FROM System.IOTA;
    ELSEIF(@ibc>300)THEN
        SELECT ‘Range Error’ as “TitleMessage”, ‘ibc value for this sample is too high’ as “message” FROM System.IOTA;
    ELSE
        SELECT ” as “Message” FROM System.IOTA;
    END;
ELSE
    SELECT ” as “Message” FROM System.IOTA;
END;

 

As the custom warning is execute immediately following the calculation of the final result, a possibility exists to do other custom actions as part of this warning system. A customer requested that when a particular warning happened, the lab would like to see this warning in the sample-id field which can be made immediately visible in the IBCm revisions of the main software. The following SQL executes an update on the samples table and when a sample has a given error – in this case the Sonication control voltage error 0x3310 – if a sample has this error set, the sample id will be filled with the custom message.  The SQL must end with the proper select statement as this is what the software would expect the warning system to do – in the example we just return an empty message prompting no further action.

 

UPDATE Samples 
     SET [SampleID] = 'Sonicator Error' 
     WHERE ([index]=:paramSampleIndex) AND (ErrorCodes LIKE '%0x3310;%');

SELECT '' as "TitleMessage", 
                 '' as "Message", 
                 0 as "Code", 
                 False as "Stop", 
                 False as "Used" 
FROM System.IOTA;

 

 

 

 

 

 

 

Posted in Uncategorized | No Comments »

News

BactoCount IBC & IBCm accepted by NCIMS

BactoCount IBC & IBCm are now accepted by NCIMS as alternate methods for bacterial counts…
Read More >

New and Improved Microspheres!

Our new and improved Microspheres are equivalent to the current product but with an added…
Read More >

International Committee for Animal Recording International Dairy Federation