@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
If your code was wrong, I'm sure I would highlight where it was wrong, and offer a correction ...as I said previously... that is my duty! Would I be wrong in doing that? I mean... should the forum members here be led astray by your wrong and buggy code?
Have you ever provided any code other than waffle of your previous experiences?
Please don't take this the wrong way... it's a valid question... have you?
@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
If your code was wrong, I'm sure I would highlight where it was wrong, and offer a correction ...as I said previously... that is my duty! Would I be wrong in doing that? I mean... should the forum members here be led astray by your wrong and buggy code?
Have you ever provided any code other than waffle of your previous experiences?
Please don't take this the wrong way... it's a valid question... have you?
@frogandtoad ABSOLUTLY, if I have a bug in my code, please point it out, yes it is your duty. Sadly I have not yet provided any code, all I have done so far is use existing code, this is part of my reason for not being a fan of OOP, I just have not yet seen a need. I know you have reasons galore, and have posted code, but non of that changes my mind for the reasons I have previously stated.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
If your code was wrong, I'm sure I would highlight where it was wrong, and offer a correction ...as I said previously... that is my duty! Would I be wrong in doing that? I mean... should the forum members here be led astray by your wrong and buggy code?
Have you ever provided any code other than waffle of your previous experiences?
Please don't take this the wrong way... it's a valid question... have you?@frogandtoad ABSOLUTLY, if I have a bug in my code, please point it out, yes it is your duty. Sadly I have not yet provided any code, all I have done so far is use existing code, this is part of my reason for not being a fan of OOP, I just have not yet seen a need. I know you have reasons galore, and have posted code, but non of that changes my mind for the reasons I have previously stated.
You haven't posted any code in over 800 posts... when are we going to see some of your 50 years of software engineering?
I look forward to that!
@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
If your code was wrong, I'm sure I would highlight where it was wrong, and offer a correction ...as I said previously... that is my duty! Would I be wrong in doing that? I mean... should the forum members here be led astray by your wrong and buggy code?
Have you ever provided any code other than waffle of your previous experiences?
Please don't take this the wrong way... it's a valid question... have you?@frogandtoad ABSOLUTLY, if I have a bug in my code, please point it out, yes it is your duty. Sadly I have not yet provided any code, all I have done so far is use existing code, this is part of my reason for not being a fan of OOP, I just have not yet seen a need. I know you have reasons galore, and have posted code, but non of that changes my mind for the reasons I have previously stated.
You haven't posted any code in over 800 posts... when are we going to see some of your 50 years of software engineering?
I look forward to that!
@frogandtoad Given your attitude you likely won't, but as I said before, so far I am using sample code or other people's code. This is fun stuff, not the kind of stuff I was paid to do.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@frogandtoad Indeed, if I had my code and posted it you would have had a lot of fun nit-picking it to death I am sure.
If your code was wrong, I'm sure I would highlight where it was wrong, and offer a correction ...as I said previously... that is my duty! Would I be wrong in doing that? I mean... should the forum members here be led astray by your wrong and buggy code?
Have you ever provided any code other than waffle of your previous experiences?
Please don't take this the wrong way... it's a valid question... have you?@frogandtoad ABSOLUTLY, if I have a bug in my code, please point it out, yes it is your duty. Sadly I have not yet provided any code, all I have done so far is use existing code, this is part of my reason for not being a fan of OOP, I just have not yet seen a need. I know you have reasons galore, and have posted code, but non of that changes my mind for the reasons I have previously stated.
You haven't posted any code in over 800 posts... when are we going to see some of your 50 years of software engineering?
I look forward to that!
@frogandtoad Given your attitude you likely won't, but as I said before, so far I am using sample code or other people's code. This is fun stuff, not the kind of stuff I was paid to do.
LOL... hopefully, we might one day see that rusty code of yours 😉
I edit my posts to fix typos, correct grammar, or improve clarity. On-screen keyboards are evil.
@binaryrhyme Darn, I wish I seen yours before I did mine. I like the switches and meters. Did you put fuses on the back? I don't even have an ON/OFF but it will be added shortly.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@zander No fuses. I considered it but my power bar, and I think the power brick, have breakers - and the brick can only send 4.6A total, anyway. I might add them later... pondering where they'd go... I should check the stats on the buck converters to see if they trip at max amps. Stuff to think on.
Still calibrating stuff - currently one of the buck converters won't dial down to 3.3v - frowny face 🙁 - specs say it should get down as low as 1.5v - have to see if the other one can get down there, or I'll have to rework that circuit with a different converter or a daisy chain or something.
I edit my posts to fix typos, correct grammar, or improve clarity. On-screen keyboards are evil.
@binaryrhyme I found that some of those take a lot of turns before they change much, then they change quickly. That's why I bought a batch of 10 for $20. I assume you have them right way round, IN and OUT.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@zander Yeh, I've run it up and down from 15v to 4v, but seems to hit a limit at 4.
I edit my posts to fix typos, correct grammar, or improve clarity. On-screen keyboards are evil.
@binaryrhyme Have you tried another one assuming you have a few, and what do you think of getting it down to 4-5 then add an LDO VR chip, the problem will be how much amperage you want to get out. The AMS1117 produces 800ma with at least a 4.75V input (I would round up a bit to 5) I like combining them when the input is 12V to keep the heat down.
Arduino says and I agree, in general, the const keyword is preferred for defining constants and should be used instead of #define
"Never wrestle with a pig....the pig loves it and you end up covered in mud..." anon
My experience hours are >75,000 and I stopped counting in 2004.
Major Languages - 360 Macro Assembler, Intel Assembler, PLI/1, Pascal, C plus numerous job control and scripting
@zander Yeh, I have another to try - and can add another buck to get the rest of the way - or buy a different one, lol. I'll muck about.
I edit my posts to fix typos, correct grammar, or improve clarity. On-screen keyboards are evil.
@binaryrhyme Good job Biny!! looks good to me,
maybe your better at it than you give yourself credit for..anyway, nice work..
regards,
LouisR
LouisR