Article: KB-12364
How to:
Fix the Flanker State from Receiving to Empty.
Skill required to complete this article: Controls and level is No Skill Level Association.

KB [How to fix the flaker state from Receiving to Empty]

 

Question/Problem \How to fix the flanker state which is stuck in receiving state for AAFES site.

 

Environment

-BOSS III

-Shared Memory

 

 

Answer/Solution

 

 

Step

Details

Image/s

Transfer Status

Check Status of transfer in Acupass Maint tab in BOSS HMI (ask site which transfer is stuck) for example here left flanker from transfer 2 (RTC3), is stuck in receiving.

 

Shared Memory

Open Shared Memory for related RTC and navigate to flanker o and array zone_State.

To array the zone_State, right click on it and select 'Group 0 1000mSec.

 

In this example the issue was with RTC3, transfer 2 (module[1]) left flanker, as we see it's stuck in receiving [4].

 

 

 

 

 

 

Flanker State change from receiving to Empty

In Shared Memory we will change the transfer state value from 4 [Receiving] to 3 [Empty].

 

AcuPass Maint tab in BOSS HMI

Check Acupaas Maint tab in BOSS HMI to verify transfer State Change, transfer State should be changed to Empty.

Flanker State in code

Zone state can be verified from Accupaas.h file in code

0,1,2-FLANKER_DIVERT_STATE_UNKNOWN

3-FLANKER_DIVERT_EMPTY

4-FLANKER_DIVERT_RECEIVING_PRODUCT

 

 

 

Related items

 

Reference Ticket

TS-00419710,

TS-00435353

TS-00430407

 

 

[This section is for attachments and/or links to other items. Attached documents shall be up-to-date, correct and using Honeywell standard templates.]

 

Internal Notes

 

[Section is meant for information only available for internal use. This includes references to internal records, such as Jira tickets, bug numbers, etc.]

***If there is information in this section prior to migration to SalesForce, then it may NOT be published. This information will be fully visible along with all information above.***

 

Reason for confidentiality

 

#NotValidated

[Section is meant for a brief reason for any data recorded in Internal Notes above, or any reason that the general article cannot be released to the public. Can be updated to Validated once reused and agreed by KCS Contributor]

***If there is information in this section prior to migration to SalesForce, then it may NOT be published. This information will be fully visible along with all information above.***

 

DISCLAIMER:

Information in this document is subject to change without notice and does not represent a commitment on the part of Intelligrated. This information is typical of the questions and general advice given; however, your particular case and circumstances may produce different results or require different recommendations. Therefore, use of this information is not a suitable replacement for contacting Intelligrated Technical Service engineering for specific recommendations and solutions to your application.

 

No part of this article may be reproduced or transmitted in any form or by any means including recording, or information storage and retrieval systems, for any purpose without the express written permission of Intelligrated. All information contained within the article is private and confidential and the sole property of Intelligrated.

 

In no event, shall Intelligrated be liable for any damages whatsoever including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss, even if Intelligrated has been advised of the possibility of such damages. Because some states do not allow the exclusion or limitation of liability for consequential or incidental damages, the above limitation may not apply to you.

 

Template updated 2022-09-20 kwk Pending approval

 

 

 

 

 Related Articles
No Related Articles Available.