This my submissions for the 2014 ATM challenge. It contains 2 different solutions.The first is a single stand-alone state machine using several of the techniques that I have evolved over the years.The second is a collection of 4 independent main programs or actors that communicate to each other through user events.ATM, ATM2, Account will remain idle or offline until the Banker comes online.The Banker is designed to maintain the account information and respond to transaction request of the other 3 clients.Please let me know if you have any comments.Mark Balla

Chicago LabVIEW User Group

Mark Balla ATM Solution LV2012

Looking forward very much to the discussion. Learning about the problems of my own approach and seeing new architectures is exactly what I was hoping for.

Message 11 of 11

(374 Views)

Chicago LabVIEW User Group

Mark Balla ATM Solution LV2012

Re: Mark Balla ATM Solution LV2012