Mark Balla ATM Solution LV2012

[MarkBalla-Tecnova]

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

[Sergey_Kolbunov]

Mark,

I realize that it is year 2014 already, but that is happened that I'm still using LabVIEW 2012.

It would be good to post solutions at least in current and previous versions of LabVIEW.

Could you please save yours and David's solution to LV 2012?

Thanks,

Sergey

[NJKirchner]

fgv?!

.....{heavy sigh}

I guess I haven't read through all the requirements of the app, but still, I will stand against.

~,~

[MarkBalla-Tecnova]

Not sure where you see a reference to FGV.

My solution does not use them to transfer data between actors. The state machines are a direct result of principals I learned from your "Rebirth of the LabVIEW State Machine presentation. I would love to hear your feed back on the structure.

Mark

[jordankuehn]

I believe he is looking at the ATM Project inside of your project and referring to the [Control States.vi] AE, rather than the VIs listed in the two MAIN folders which I assume are the solutions you are presenting Mark since they look a lot like the TLB from a quick glance.

[David_Ferster]

My version, which I am scheduled to present, is FGV's all the way down. I guess I have some work to do before Thursday.

[David_Ferster]

I see what happened. My code somehow got mixed into the files with Mark's. So my FGV's are unfairly tainting him.

[MarkBalla-Tecnova]

Let me clarify a few things before this discussion goes out of bounds and user’s become reluctant to submit their solution for fear of being scolded by the Codding Cops.

The purpose of this challenge IS NOT to debate over each other’s coding choices or style.  So let me start by saying It’s OK to be a terrible LabVIEW programmer that is what the UGMs are for to help everyone get better.

I want the focus instead on the developer’s journey. Starting from defining problem to choices made during the process to final solution. My expectation is if we focus on the user’s story we will have a better more inclusive discussion.

I really would like to see less experienced developers create a solutions and present it without concern for getting put into a coding review. Personally I can see looking at a less experience user’s code and remembering when I used a similar techniques.  My goal would be if programmers see something they no longer do to share why they move away from one method to another.

So for this challenge let’s please focus on our LabVIEW journeys good or bad and avoid getting into a debate on right and wrong coding practices.

Thanks

Mark

[NJKirchner]

I see that I was indeed looking at the wrong implementation.

It took me a second to see the forest for the trees, but I indeed am intrigued by your take on the TLB`prime concept. I'll stew on how that shakes out in my head.

wrt the fgv's in the original implementation, it indeed illustrates very cleanly and without a lot of hoohaa a very understandable solution. It was so well done it is indeed making me try to discern how to best make recommendations for when the last S in SMoRES indeed warrants something as simple as the FGV based implementation.

So David, in short, well done.

In long, be sure to know, have a healthy respect for the issues they can easily cause.

Together lets see if we can shake out solutions that do a good job being as easy to adopt and understand, which also embody the principles of SMoRES

[NJKirchner]

I completely agree with you Mark.

I apologize for potentially derailing the UGM discussion.

Indeed everyone should feel welcome and eager to share and learn