Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 3 Next »

Target release6.10.0
Epic

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Feature Request

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Document status

DRAFT

Document owner

Goals

  • Allow the end user to reduce SR140 volume on per call basis without needing to modify BT_CPARAM.CFG file.

Background and strategic fit

Currently, the fax transmission level and fax reception level are set in the file BT_CPARM.CFG parameter file which contains several sets of parameters which are specific to a country or to a group of countries. For example, for the USA, the fax transmission level is set by the define DATA_LEVEL_USA (default 0xe2) and the fax reception level is set by the define REC_LEVEL_USA (default 0xaa). It is difficult to change these values in the file BT_CPARM.CFG since this file is a binary file. This feature request will implement two new ways of modifying the transmission and reception levels. The first way will be via new keywords in the user configuration file btcall.cfg and the second way will be via the API function BfvFaxT30Params(). The changes implemented for this feature request will apply to all platforms (SR140 and boards).

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1Provide parameters in btcall.cfgAdd new keywords to btcall.cfg to allow user to change SR140 levels.Must Have


2Update API function BfvFaxT30Params()Update BfvFaxT30Params() to allow the application to change the SR140 levels.Must Have 
3Apply to both SR140 and TR1034Apply to both SR140 and TR1034Nice to Have
4DocumentationInclude in documentation in section "Parameters for Technical Support Purposes"Must Have
5



User interaction and design

For the first way, two new keywords will be defined for the user configuration file btcall.cfg. For the fax transmission level (will also affect tone generation), the new keyword will be xmt_level_override and for the fax reception level the new keyword will be rcv_level_override. If the keyword xmt_level_override appears in btcall.cfg, it will override the DATA_LEVEL_XXX level specified in the BT_CPARM.CFG file. If the keyword rcv_level_override appears in btcall.cfg, it will override the REC_LEVEL_XXX level specified in the BT_CPARM.CFG file.

If the keyword xmt_level_override is present in the btcall.cfg file, it will override the DATA_LEVEL_XXX value from the BT_CPARM.CFG file. If the keyword rcv_level_override is present in the btcall.cfg file, it will override the REC_LEVEL_XXX value from the BT_CPARM.CFG file. If the BfvFaxT30Params() function is called to set xmt_level or rcv_level, it will override the values from BT_CPARM.CFG and btcall.cfg.

If the both the btcall.cfg parameters are set and a value is passed into BfvFaxT30Params(), the offset will be additive.

The transmit level in BT_CPARM.CFG ranges from 0xCE to 0x00 (-50 to 0) where -50 corresponds to the lowest possible transmit level and 0 corresponds to the highest possible transmit level. So for xmt_level_override = 2 and xmt_level = 4 the transmit level would increase by 3 dB total. The receive level in BT_CPARM.CFG ranges from 0xA8 to 0xBC (-88 to -68) where -88 corresponds to the highest possible receive level and -68 corresponds to the lowest possible receive level. So for rcv_level_override = 2 and rcv_level = 4 the receive level would increase by 3 dB total as well. The calculation for negating the rcv_level_override and rcv_level will be done in the software due to the inverted range for the receive level.  

The new keywords should appear in the user configuration file btcall.cfg as follows:

xmt_level_override E4

rcv_level_override  AC

For the second way, two new members will be defined for the structure args_fax_t30_params. For the fax transmission level the new member will be defined as char xmt_level and for the fax reception level the new member will be defined as char rcv_level.

struct args_fax_t30_params {

    RES res;

    unsigned bit_rate;

    unsigned scan_time;

    unsigned modulation_type;

    unsigned line_compression;

    MILL_LINE *async_lp;

    unsigned iaf_bit_rate;

    char xmt_level;

    char rcv_level;

};

 

An example for setting the new members xmt_level and rcv_level before calling BfvFaxT30Params(lp, &args_params); is as follows:

struct args_fax_t30_params args_params;

BT_ZERO(args_params);

args_params.xmt_level = 0xE4;

args_params.rcv_level = 0xAC;

// Set other parameters here such as bit_rate, scan_time, etc.

BfvFaxT30Params(lp, &args_params);

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • Currently, the plan is not to update the structure t30parampkt and the sample application mkinfopk.c to include xmt_level or rcv_level.

Tasks Releated to Feature

key summary type assignee

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.