When I saw your blog on the PCB, I hoped that you had become a blogger. This confirms it. Now you have to catch as well as pitch (field as well as bowl in your case).
Being too lazy to go and check it out (start of the weekend and all that) I wanted to ask if the Picaxe is in fact a standard Pic with a BASIC interpreter in firmware, much like Zilog And Intel had in year's past?
Also is it possible to descend into assembler?
Thanks Aubrey! Max is very persuasive.... Ref assembler - this is one of my questions that I will be investigating for a further blog, so you'll have to wait! I know it does let you access the different memories (PEEK and POKE statements), but I don't know how far beyond that you can go.
Why is the first question always one to which you have to say "I'll get back to you on that"? I always seem to do that when I'm on training courses.....so I guess it's karma.... :-)
Pretty cool, David. You model picaxe looks only two pins bigger than a dual opamp.
Glad to hear you're a BASIC afficionado. In case you didn't know, there's a very nice new version of BASIC from right in your own backyard: QB64. Virtually 100 percent compatible with MS Qbasic, even gives you that same familiar editor, but it goes a lot further too. Runs fine on 32-bit or 64-bit machines, MS, Apple, or Linux, and it's a compiled version.
These picaxe devices seem to have a language simiilar to older versions of BASIC, in which variable names were restrictive.
(Now you've got me questioning how I orient the resistors on my boards. Thanks a lot!)
Hello Bert, thanks. The PICAXE 08M2 is 8 pins, same as a dual opamp. and it has an internal resonator so all 6 pins apart from power can be used for I/O (with certain restrictions).
You CAN call your variables whatever you want, using a command, and I'll be dealing with that in Part 2.
I must look into QB64 though I have long had a hankering to learn Visual Basic. Structured program people will tell you that the GOTOs in BASIC are a no-no, and I do make an effort to avoid them in general use, but there's times they save you a lot more jumping through hoops.
I'd love to be a fly on the wall next time you are building something :-)
@adventures0 - sounds like you should have written this! I have found before that writing blogs like this, and maybe having some fixed goals in mind project-wise, is a GREAT way to learn. I am so impressed at the ease of use of the PICAXE and the wide range of sensors and peripherals which have purpose-made commands to simplify their use. It's going to be impossible to cover everything but I'm hoping to do a couple more blogs on them. Any suggestions on topics that you think would be good to cover would be very welcome.
The PicAxe has an associated program called LOGICATOR that makes understanding and programming much easier. It allows identification the PIC being programed . Once it is identified you are able to select the configration of the pins for that device as inputs or outputs. Once these options are selected you can then graphically pick and place the procedures you need. You can run the simulator using some of the attached view screens for input /outputs, LCD display , variables et. to debug your program. When it's working on the simulator you can then download it to the PIC. This program will also convert the flowchart to BASIC and they are usually as short or shorter than if you do it the long way. It doesn't get much easier than this.
@flabruce - you're getting ahead of me here, I was aware of Logicator and was going to have a go at it but haven't got there yet. It's diffciult to see how it could be easier than I have found it, but that's coming from a pre-knowledge of BASIC. I hope Max will allow me enough space to get to Logicator....
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.