Spoke to the head honcho. He'd read my cv prior to interview, and decide he wanted to interview me for another job he had coming up - systems engineering and making the control software for a weighbridge.
He offered me a job and I took it :-) There might be some involvement with the database, but the priority will be capturing the requirements of, specifying the hardware for, and engineering the control software for the weighbridge project.
I start on Monday.
He who laughs last ... is still using a slow modem
Congratcho Nacho!
Weighbridges are sexy
Quality! Well done that man!
So, out of interest, what will you be writing the control software in?
Originally Posted by frankus
Great news phil, the GAS fund can start mounting again.
I think that's partly my decision. C would be my first choice, with assembler for whatever can't be done in C (which tbh isn't much once you've set up the runtime stack registers). If there's GUI-style user interfaces to worry about these may be easier to write in C++ but I don't know 'cos I've never tried (C++ or GUIs for that matter).
Will need to decide whether the volume of production versus development timescales dictates using such things as logic controllers or own code on SBCs, whether there needs to be a proprietary RTOS or any bought-in libraries of protocol software ... all that has to be decided. The first thing is to get a grip on what we want the system to do.
Also up for consideration is the development host. Depends on what the target is going to be and who makes the relevant cross-development tools, and what they can be hosted on. I hope it's UNIX.
He who laughs last ... is still using a slow modem
He he ... ES-175 or a new car ? Hmmmm....Great news phil, the GAS fund can start mounting again.
He who laughs last ... is still using a slow modem
nice one phil, mucho congrats.
None of you seem to understand; I'm not locked in here with you, you'll all locked in here with me.
Nice one... Right up my alley that... Not that I've ever done anything specifically similar, but I love that style of software engineering and the feeling of wrangling a solution out of raw bits and bytes. That's proper programming
Closest thing I ever did was write an assembly (80386) layer as an interrupt driver to sit on top of a network "T" card (which copied all network traffic passing it into its onboard memory), then a C layer above that to decode the protocol (X25 in this case), then some C++ interfaces into the company's bespoke BASIC control language to manipulate and interrogate the packets, running in Windows 3. All I started with was a small typed "manual" from the manufacturer describing how to control the card and access its memory, and a book on X25 protocol. It was easily the most satisfying bit of programming I've ever done... *sigh* those were the days... Worked a treat as well...
Well done that man, just in time for a good Christmas (an a ES-175 of course).
Well done Chap. Loads of 3rd party add-on UI libraries for C without needing to hurt your head learning C++
Reply With Quote