Change Log

Version: Release-4.7
June 30, 2007

  • The API was modified so the extension attribute correctly accepts xml.
  • Several function names were changed to match the IPC Standards more closely. The changes made are as follows:
    • NewProcessStepAbortExtended function was changed to NewProsessStepAbort.
    • NewProcessStepCompleteExtended function was changed to NewProcessStepComplete.
    • NewProcessStepPauseExtended function was changed to NewProcessStepPause.
    • NewItemChangedExtended function was changed to NewItemChange.
    • NewItemInitializeExtended function was changed to NewItemInitialize.
    • NewItemChange function was changed to NewItemChangeExtended.
    • NewItemWorkAbort function was changed to NewItemWorkAbortExtended.
    • NewItemWorkComplete function was changed to NewItemWorkCompleteExtended.
    • NewItemWorkPause function was changed to NewItemWorkPauseExtended.
    • NewItemWorkResume function was changed to NewItemWorkResumeExtended.
    • NewItemWorkStart function was changed to NewItemWorkStartExtended.
  • The NewItemInitialization function was fixed. Prior to the change, append functions were generated a NO PARENT ERROR since the NewItemInitialization function was not developing the correct parent element.
  • The namespace references for the EquipmentNonSelectedRecipeModifiedExtended and EquipmentRecipeSelectedExtended messages were fixed.
  • The embedded xml schema for ProcessStepPause was modified so the message correctly validates.
  • The embedded xml schema for IPC-2546 ItemChange was added so the message correctly validates.
  • Various misspellings and errors were corrected:
    • MISSING ATTRUBUTE VALUE was changed to MISSING ATTRIBUTE VALUE.
    • INVALID ATTRUBUTE VALUE was changed to INVALID ATTRIBITE VALUE.
    • NOT WELL FORMED ELEMENT CONTENT is now used.
  • Additional error messages were added.

Version: Release-4.5
May 19, 2006

  • The updated schemas for the IPC-2546 have been placed at http://webstds.ipc.org/2546 and the old schemas have been deprecated and placed at http://webstds.ipc.org/2546/deprecated.  The API has been modified accordingly.
  • The names of certain project subfolders modified to so the project structured more elegantly.  The name changes do not affect the DLL interface.  Rather, the changes are just source code housekeeping.
  • The DateandTime attribute name was made consistent throughout the project.
  • The namespace references for the EquipmentErrorExtended and EquipmentParameterModifiedExtended messages were fixed.
  • The missing function, AppendMaterialHandlerTableUninstalled, was added.
  • The function name NewItemIdentifierRead was changed to NewItemIdentifierReadExtended to match the updated IPC-2546.

Version: Release-4.4
April 3, 2006

  • The Acknowledgement function was modified so that it responds with “NO ACKNOWLEDGEMENT” correctly.

Version: Release-4.3
March 22, 2006

  • The functions for publishing the EquipmentErrorExtended message were modified to use the correct namespace

Version: Release-4.2
March 21, 2006

  • The GetMessage function was fixed so that it works correctly when no messages are queued for the client.

Version: Release-4.1
March 20, 2006

  • The GetFirstSubscribedMessage function was fixed so that it works correctly when a null is encountered.
  • The AppendMaterialHandlerTableUninstalled function was added to the interface.

Version: Release-4.0
March 3, 2006

  • Many changes were made to the API so that it adheres to the proposed IPC-2546 schemas.  See http://webstds.ipc.org for information about the proposed IPC-2546 schemas.

Version: Release-3.0
November 19, 2004

  • The documentation has been updated as follows:
    • The width of all pages has been reduced to facilitate printing.
    • The format of the schemas in the documentation have been modified to facilitate printing.
    • If an attribute value must adhere to a particular W3C format (i.e. dateTime), then a hyperlink to that format has been embedded in the documentation.
    • References to IPC standards are hyper linked to a copy of the standard on the IPC site.
    • Message schema URL's references have been hyper linked to the schema residing on the IPC site.
    • Various accuracy changes have been made.
  • A set of error level, error code and error message triples have been defined for error level 2. The GetLastError function has been updated to return the triples.
  • The PublishMessage function has been implemented.
  • The PublishEquipmentParameterModifiedExtension function has been modified to generate an EquipmentParameterModified message that contains an EquipmentParameterModifiedExtension.
  • The AppendItemRepairSymptomRef and AppendItemRepairIndictmentRef functions were modified to accept input from the calling program.
  • The default value of the AppendInspectionFrameRegion decade attribute is set to 0 if the calling program passes NULL. This was done to be consistent with the IPC-2547 standard.

Version: Beta-2.4
October 11, 2004

  • In the past, if the contents of the second MIME block in a received HTTP transmission were not well formed, the API would indicate the problem via a dialog box. The dialog box will no longer be generated. Instead, the error will be indicated to the calling program via the GetLastError function.
  • The interfaces to the API sub-classes have been hidden from the solution explorer. The interface to the main class remains. Issue #491.
  • A set of error level, error code and error message triples have been developed. The GetLastError function has been updated to return the triples associated with error levels zero and three. It will also return the triple associated with the “NETWORK ERROR” error code. Issue #495.
  • The schemas for the following IPC-2546 messages were found to be inconsistent with the standard document:
    • BadBoardMarkReport
    • ComponentMispick
    • ComponentNotPlaced
    • ComponentNotRecognized
    • ComponentReject
    • EquipmentErrorSubsystem
    • EquipmentOutOfComponent
    • EquipmentParameterModifiedExtension
    • ItemDidNotTransferSuccessfully
    • ItemRecognitionFailure
    • MaterialHandlerChanged
    • MaterialHandlerDivisionDown
    • MaterialHandlerDivisionUp
    • MaterialHandlerInstalled
    • MaterialHandlerLow
    • MaterialHandlerOutOfComponent
    • MaterialHandlerRefilled
    • MaterialHandlerTableInstalled
    • MaterialHandlerTableUninstalled
    • MaterialHandlerTrouble
    • MaterialHandlerUninstalled
    • ProcessDataReport
      Hence, the schemas were updated to be consistent with the standard. The API was modified to be consistent with the new schemas. Copies of the new schemas can be found at: http://webstds.gatech.edu/2546. The new schemas will be submitted to the IPC. Issues #’s: 388, 389, 390, 391, 392, 393, 394, 395, 396, 401, 402, 405, 422-433, 435, 437, 440, 442, 443, 445, 451, 470, 476, 504 & 506.
  • The schemas for the following IPC-2546 messages were found to be inconsistent with the standard document:
    • ItemWorkStart
    • WaitingForOperatorAction
    • EquipmentWarningsCleared
      Hence, the schemas were updated to be consistent with the standard. The API was modified to be consistent with the new schemas. Issue #’s: 406, 472, 484 & 499.
  • The documentation has been updated to include the following:
    • The list of possible error level, error code and error message triples.
    • The definition of error levels.
    • Embedded links to the triples, error level definitions and the w3c Date and Time format.
    • The “required” column has been removed from the attributes table.
    • The “Restrictions” column of the attributes table has been renamed “Acceptable Values.” The attribute acceptable value entries have been more fully populated.
    • The function declaration value is formulated from the attribute and return value entries (versus being stored in the database). This should lead to more accurate function declarations.

Version: Beta-2.3
September 23, 2004

  • The fix reported in Beta-2.2 was not correctly applied to the Acknowledge, GetDomainConfiguration and GetMessage functions. The fix has now been applied.

Version: Beta-2.2
September 21, 2004

  • The correct DateTime string is now generated for time zones equal to or greater than GMT (i.e. +00:00, +01:00, etc). This bug caused an error when (TZD >= 0 and (DateAndTime = “” or Null)). Where, TZD is the value of the regional settings time zone offset and DateAndTime is the value supplied for the attribute. Issue #490.

Version: Beta-2.1
September 17, 2004

  • A new function has been added, GetFirstSubscribedMessage. This function obtains the list of messages, that the client can publish, which have been subscribed to by other clients in the domain configuration. The function returns the first message in the list. Issue #487.
  • A new function has been added, GetNextSubscribedMessage. This function returns the next message in the list of messages, that the client can publish, which have been subscribed to by other clients in the domain configuration. Issue #488.
  • All functions have been modified so their DateAndTime attribute can accept an empty string. Passing an empty string causes the API to use the value of the system clock for the DateTime of the message. Issue #478.
  • The ErrorCode attribute of the GetLastError function has been changed to be of type STRING. Issue #480
  • The GetMessage function now returns an empty string if there are no messages queued for the client. In the past, the function would return a string, "There are no more messages for you at this time." Issue #481
  • The GetDomainConfiguration, GetMessage and Acknowledge messages are now validated against their corresponding schemas prior to being sent.