Is Picaxe Dead?

I think the ONLY commands that "leverage the capabilities of the chips to the max ..." are those which configure / enable the core-independent peripherals (PWM, timers, etc.) Otherwise, you're running through the interpreter.

That being said, speaking for myself .... 80 - 90% of the projects I've built only really need to be faster than ME, not as fast a lightening ... so PICAXE works. But, I've also had projects where I want things to be much faster ... and I've enjoyed embedded PIC development for that ... I mean ... if you haven't played with Direct Memory Access ... you're missing out! :)
 
I think the ONLY commands that "leverage the capabilities of the chips to the max ..." are those which configure / enable the core-independent peripherals (PWM, timers, etc.) Otherwise, you're running through the interpreter.

That being said, speaking for myself .... 80 - 90% of the projects I've built only really need to be faster than ME, not as fast a lightening ... so PICAXE works. But, I've also had projects where I want things to be much faster ... and I've enjoyed embedded PIC development for that ... I mean ... if you haven't played with Direct Memory Access ... you're missing out! :)
DMA is fantastic and I've used it quite a lot with my experiments in audio, coupled to SPI, and getting 'frames' of audio to load into memory in the background. Parallel processing in it's truest sense. But I must admit it's sometimes taken ages to get working properly (and a lot of cost with licence renewals to get compiler optimisations!).
 
But I must admit it's sometimes taken ages to get working properly (and a lot of cost with licence renewals to get compiler optimisations!).
Yeah, the setup was the tricky part ... but it's all there in the datasheet ... you just need to re-read it about 100 times! Still, that's kind of the stuff I find fun about the hobby ... and for me, it's strictly a hobby. I'd be very stressed if I were trying to get DMA working for a work project and I was under a deadline.

Along that hobby track: I haven't had a need to optimize further than the free version of XC8 will give me ... given how much space is on chips now (128KB for code space?!) my humble little projects fit in there nicely.
 
Yeah, the setup was the tricky part ... but it's all there in the datasheet ... you just need to re-read it about 100 times! Still, that's kind of the stuff I find fun about the hobby ... and for me, it's strictly a hobby. I'd be very stressed if I were trying to get DMA working for a work project and I was under a deadline.

Along that hobby track: I haven't had a need to optimize further than the free version of XC8 will give me ... given how much space is on chips now (128KB for code space?!) my humble little projects fit in there nicely.
The optimisations I've used are more because of execution speed and getting the highest processing throughout that I can. I've never actually run out of programming space at all.
 
Well retired South Seas old timer "Manuka" here! I still occasionally browse this forum but haven't contributed for years & am now more involved in non electronic activities. Herewith a few e-musings -

I cut my teeth electronically 60+ years ago as a teen in early 1960s ham radio (then -gasp- largely thermionic!), & eventually went on to an associated NZ/Australian & UK technical & educational career.

In this context my PICAXE enthusiasm & promotion was quite recent as it began 2002 (while NZ tertiary teaching) & probably peaked during a long run of PICAXE articles (many 433 MHz data slanted) I penned for the Australian "Silicon Chip" monthly.

Yes -20+ years ago (although recent for an old timer!) & a telling duration given e-tech's white hot progress...

That early Y2k era predates such now common e-tech as BT, WiFi, SD cards, Lithium rechargeables,smartphones & even -gasp- now ubiquitous USB & white LEDs. Of course today's numerous powerful & cheap microcontrollers (& languages like microPython) were still to come.

PICAXE's,although serial programmed, then had few rivals & were superbly "can do" & cost effective beside such offerings as US sourced BASIC Stamps. I recall a degree level student saying he'd achieved more on a project in a few hours with PICAXEs than he'd managed in weeks with raw PICs. That remark rather reminded me of the mid 1970s when HP programmable calculators bypassed the need to program punch card style in Fortran. PRODUCTIVITY!

But it's now 2025 & I've rather lost touch with even NZ/Australian educational micro preferences,although apparently Raspberry Pi based setups tend the norm for senior students. (Refer an Australian MMBASIC Pico 2 based kit just released).

In Britain the BBC micro:bit (V.2) seems popular for 11-12 yo STEM teaching, no doubt boosted by it's self contained design easing classroom setup & "tidy up time" clutter.

All up, & although PICAXEs are/were schools focused, it could be that hobbiests are NOW the majority users...

To help keep things in perspective perhaps those involved with their region's STEM e-education could inform of the actual state of play?

Stan. (Wellington, New Zealand) ZL2APS
 

Attachments

  • Screenshot_20250403_110502_Chrome.jpg
    Screenshot_20250403_110502_Chrome.jpg
    351.4 KB · Views: 15
  • Screenshot_20250405_051900_Chrome.jpg
    Screenshot_20250405_051900_Chrome.jpg
    84.2 KB · Views: 8
Last edited:
I've just come back to electronics after a break and want to get back to Picaxe projects again but the programming tools for Linux seem somewhat out of date and picaxecloud.com just times out.

Does anyone have any recommendations? So far, I've been running Axepad in an Ubuntu 14 VM.

Thanks in advance,

Jools
 
I don't agree with this ... there are certainly more powerful 8-bit, 8-pin chips than the 12F1840 (PICAXE 08M2) ... some with 2x or 4x the RAM, 2x the flash storage, more UART, configurable logic blocks, etc. The PIC16F17115 for instance. As for the 18F14K22 (PICAXE 20X2), I've started playing with the PIC18F16Q41 which has 4x the storage, 8x the RAM, More timers, CLC, etc. There's even 20-pin chips that are nearly identical to the 20x2, but include a USB module.

Microchip has been marching along.


Going back to the original topic ... motivated by Bpowell's remark,

What I could appreciate as a "compromise" solution (with likely limited implementation effort for Rev-Ed as I suspect) succeeding the 08M2 (based on 12F1840): A new 08M3 (based on PIC16F17114 or 115) implementing both:

1. As a baseline: the current Picaxe BASIC command set for the 08M2 - which definitely will satisfy all educational purposes which is at the core of Rev-Eds venture,
2. Adaptations to the POKESFR/ & PEEKSFR commands, allowing all internal modules of the new PIC16F17114/5 chip to be addressed and configured - as a gift to the "professional hobbyists" seeking to use the full potential of the new device (like the OpAmp, numerical oscillator etc.).

Of course, similar reasoning holds for the 14 - and 20-pin devices in the M2 series, as well as the X2 series devices.
I can imagine that this would be possible with not too much effort since both chips are based on the same Mid-range Enhanced Core architecture, it seems just more exiting modules and increased pin mapping flexibility in the newest chips ... .

Am I a dreamer, or is there some hope ;)?

/Jurjen
 
Last edited:
I just want to remind everyone, just cuz I keep seeing it pop up, there are the X2 chips that are quite a bit more powerful than the M2 versions. Just saying.
 
I don't think anyone's mentioned this yet, but what about In Circuit Debug?

PE5 has a 'Connect' feature in the menu which just shows a message box saying that feature is in development.

Did that feature ever get implemented? I can't see it in the latest version of PE6. (The crude 'debug' command doesn't count)

This is one thing a certain 5-letter competitor got right first time out of the gate, using the same serial download cable as PICAXE and no additional external hardware.

It's also a particular weakness of Arduino. Arduino IDE 1.x doesn't have it at all and I believe the newfangled Arduino 2.x IDE has this feature if you have an expensive Atmel ICE, a requirement which is to be expected because it runs compiled code. This is a feature that is very useful in education, a potential advantage over Arduino, and it's good educational experience for students who will eventually use things like the MPLAB ICD in industry (or more likely Segger J-Link on this newfangled 32-bit ARM stuff that is very popular now).
 
No, we actually never got to see the Circuit Debug functionality supported on Picaxes. Plain 'Debug' functionality, although slow, can give you quite a bit of details of what is happening on your Picaxe and it has indeed been very helpful to me when things didn't go as 'programmed'.
Arduino is (still - I think) using the serial monitor to see what is happening, but this is more of a 'console output' type of debug.
 
To help keep things in perspective perhaps those involved with their region's STEM e-education could inform of the actual state of play?
I think that manuka has identified something that us forum members should keep firmly in mind when discussing how great it would be if there were faster M3/X3 chips with more program memory and more variable storage.

Rev-Eds PICAXE chips are a child of the technology that was being used when they were first created. I did see a forum thread that described the early history of Rev-Ed but I was unable to find it with a search. The pinned "READ ME FIRST" post in the active forum is dated 2007 so it was before 2007.

This means it is now nearly 20 years on since PICAXE chips using BASIC were released and the first languages being taught in schools may have moved on from BASIC.

This certainly appears to be the case in Australian schools were my google search came up with an Australian Govt Education web site which:
- gave an example of using visual programming in years 5-6 where the example was Scratch
- described one of the objectives for years 7-8 as "code and test programs in a general-purpose programming language such as Python or JavaScript"
- and described one of the objectives for years 9-10 as "explore the object-oriented paradigm for organising code"

The site I found did not discuss teaching the use of microcontrollers so I don't know what is used in Australian schools.
 
I think that manuka has identified something that us forum members should keep firmly in mind when discussing how great it would be if there were faster M3/X3 chips with more program memory and more variable storage.
...
Rev-Eds PICAXE chips are a child of the technology that was being used when they were first created. ... This means it is now nearly 20 years on since PICAXE chips using BASIC were released and the first languages being taught in schools may have moved on from BASIC.
So true.

And there might be some truth in Manuka's statement below as well:
...
All up, & although PICAXEs are/were schools focused, it could be that hobbiests are NOW the majority users...
...
This is the reason why I proposed in this discussion (item #48) an approach where M2/X2-level Picaxe BASIC would be implemented on newer silicon (hence the M3/X3) with POKESFR/PEEKSFR opportunities offered to hobbyists to configure the new modules themselves, whilst for educational purposes one can stick with the already excellent M2/X2 functionality. I see this as a way for RevEd to cater to both communities with very limited extra efforts from their side.

Regarding the main topic, I see similar things happening to other comparable microcontroller platforms like Parallax's Stamp, NetMedia's BasicX and - sadly - also to my other favorite microcontroller platform for more advanced and demanding projects, namely ZBASIC. The latter's forum has grown practically silent (which luckily is not yet the case of PICAXE).

But I think there is still a case to make for excellent microcontroller platforms like PICAXE and ZBASIC since the value of them lies in so much more than just the chips themselves: Through their excellent forums, the motivated and helpful userbase and excellent documentation, these platforms can bring much value and sometimes may still be the best options in many projects for years to come. But how to make this value visible?

I think is it is the rapid pace of technology development that both enables the conception of new powerful tools, but also inevitably bears with it the impression of rapidly dwindling added value as new concepts emerge and overtake the previous ones.
But value is not just based on conceptual strength but primarily created by thorough experience with the platform and leveraging on it in actual projects, i.e. really designing and making things. This value remains for very long times for the crafted individual (like so many forum members involved in this discussion), but I feel that many newcomers in the field may simply not observe this and thus miss a great opportunity.

I have messaged the owners of both the PICAXE and ZBASIC platforms on my scenario proposals for including newer silicon with limited efforts (I think) from their side, we'll see, this is the maximum useful effort I could think of … .

Best regards,
Jurjen
 
Last edited:
Spring has come, so new creatures start to emerge from the winter time ... . Maybe this could apply to the PICAXE devices as well, therefore this public request to Rev.Ed.:

To expand a bit on the idea I floated in post #48 above (implementing current PICAXE Basic for M2 chips directly on newer, recently released silicon - with POKESFR for use by advanced hobbyists to themselves unlock the potential of newer modules in the new silicon): I researched a bit more regarding differences between newer PIC devices (in particular the 8-pin PIC17115) and the (likely) preceding M2-device (PIC12F1840).

As I see it, the biggest challenge would be to implement a changed memory map, since more memory banks have been added, and also the position of specific SFR's in the older M2 device have changed in the new map. To me it seems that this is the only real relevant change (as a precondition for my proposal, in which the BASIC language itself would not change/expand, as an easy way to enable a device update/modernization without a significant BASIC language change), since both the older and newer silicon are based on the Enhanced Mid-Range Core architecture.

I would really love to see RevEd take this step, since:
  • The newer silicon is more than 10 years younger than the M2-based silicon, with significant improvements and additions regarding modules (including the ADCC, Opamp, NCO, improved DAC etc.).
  • Still key knowledgeable enthousiasts (like Allycat, Inglewoodpete etc.etc, also including me :)) are active on the forum and giving support to new members, so it would be highly motivational for all of us as enthousiasts to see new devices being introduced and to not loose a critical mass of supporters (which many other platforms have)
For newer silicon I would propose the PIC16F17114-15-24-25-44-45 family as they seem to me to have the most attractive combination of modules, allowing sensor signal conditioning and processing.

Rev.Ed, I sincerely hope you are willing to consider something like this as your product is a source of great joy to many of us hobbyists, and I feel the Picaxe platform is still very relevant. I am willing to support as well (within reach of my opportunities).

Thanks! /Jurjen Kranenborg
 
Last edited:
What an interesting thread, which I have read almost in its entirety.

In my case, my programming lay in the distant past, but PICAXE's unique combination of hardware and approachable programmability has allowed me to undertake a complex project in later life that I would never have been able to get my head around if I'd had to learn a more modern development environment.

Fortunately this project, a novel musical clock with many complications, has no specific speed requirements, but in fact it was RevEd's hardware offerings, such as the sound kit and the OLED display, that made me realise that the whole idea was feasible.

I can well understand why the whole scene seems a little stale, but my sincere hope is that it endures, as it provides a very easy route to automation of lightweight projects.
 
Quote Baker Steve "I can well understand why the whole scene seems a little stale, but my sincere hope is that it endures, as it provides a very easy route to automation of lightweight projects."

I agree 100 %

I used to love the simplicity of Mikroelektronica compilers - then they froze support and moved to Necto and ruined everything

... no problem - move to Microchip XC8 - no nice libraries (that I could find) but powerful and straight forward as long as you avoid MCC and Harmony. Now VScode is the future. Not the future I want.

Love PICAXE ecosystem for simple projects. Simple, quick and little BS. Would love to see a revival, but don't hold out much hope. Still very useful though.

Don't miss any PIC16 based PICAXES other than newer 8 pin PIC16 varieties. Would love to see support for PIC18 Q series.

My 2 cents
 
I still use picaxe for my motor control systems but where I need control of LED strip - WS2812 - or LCD and vga monitors I use picMX32 series chips or Raspberry pico / pico2 modules programmed in MMBasic.
 
As a small time user I think picaxe is the best. It is small, robust and is really not fussy about it power requirements give it 5 V and it's happy. I'm using them to drive servo controlled points and semaphore signals on a garden railway. Teamed with ESP01 boards I can use wifi to do this. The lack of wifi is a drawback. The one thing I would really like to do is to be able to read the program on a picaxe back into the editor to debug it. That is the one thing Arduino has over picaxe. As I said small time user so I may be wrong. With the use of the dreaded AI for programming (70 years old with no computer experience) I'm using them for just about everything in fact I tried Arduino gave up and went back to old faithful.
I will sorely miss it if it goes.
 
The one thing I would really like to do is to be able to read the program on a picaxe back into the editor to debug it.
The bear suggested a simple way to deal with this issue in this post.
Simply add a sertxd command that reports the file name and date using ppp_filepath, ppp_filename and ppp_datetime as the first line of every program.
e.g.
sertxd(ppp_filepath, ": ", ppp_datetime, cr, lf)

Hookup PE, power the PICAXE off and back on and it will report the program file and the date (for the version) to PE

That is the one thing Arduino has over picaxe.
My understanding of Arduino is that you write your program in the "C" language which the Arduino IDE compiles into the binary machine code that the microcontroller used and downloads that binary.

You choose whether the machine code that is downloaded into the microcontroller is "read-protected" in flash so if you didn't "read-protect" your program then you can read it back but that downloaded binary machine code is not the original "C" program source code.

But I don't use Arduino, so I could be wrong. Do you have a link describing how to read the original "C" program from the microcontroller using Arduino?
.
 
As a small time user I think picaxe is the best. It is small, robust and is really not fussy about it power requirements give it 5 V and it's happy. I'm using them to drive servo controlled points and semaphore signals on a garden railway. Teamed with ESP01 boards I can use wifi to do this. The lack of wifi is a drawback. The one thing I would really like to do is to be able to read the program on a picaxe back into the editor to debug it. That is the one thing Arduino has over picaxe. As I said small time user so I may be wrong. With the use of the dreaded AI for programming (70 years old with no computer experience) I'm using them for just about everything in fact I tried Arduino gave up and went back to old faithful.
I will sorely miss it if it goes.
The Programming Editor setup on my PC has a "backup" folder directly under ....Documents\PICAXE Editor

A backup is created every 10 minutes. I just checked mine and there are over 1200 backup files that I can call on if I need one.
 
The bear suggested a simple way to deal with this issue in this post.
Simply add a sertxd command that reports the file name and date using ppp_filepath, ppp_filename and ppp_datetime as the first line of every program.
e.g.
sertxd(ppp_filepath, ": ", ppp_datetime, cr, lf)

Hookup PE, power the PICAXE off and back on and it will report the program file and the date (for the version) to PE


My understanding of Arduino is that you write your program in the "C" language which the Arduino IDE compiles into the binary machine code that the microcontroller used and downloads that binary.

You choose whether the machine code that is downloaded into the microcontroller is "read-protected" in flash so if you didn't "read-protect" your program then you can read it back but that downloaded binary machine code is not the original "C" program source code.

But I don't use Arduino, so I could be wrong. Do you have a link describing how to read the original "C" program from the microcontroller using Arduino?
.
You are correct ... the only code you'll get off the Arduino (assuming it's not read-protected) is the compiled machine code ... you can easily (with the GCC provided tools) convert that machine code back into Assembly. There are programs that will attempt to convert assembly back into C ... but it'll be messy code ... no variable names, code remarks, etc.

I've pulled the assembly off of chips a few times, but mostly to see what addresses they were occupying, and to ensure the code was complete (bootloaders for instance).
 
Yet another long-time senior member of the community checking in (the forum was such a great read years ago, so many fascinating projects and discussions), god I can't believe it's been 15 years since the M2 chips came out, I remember being so excited for them, and it seemed like X3 or M3 series would inevitably be out a few years later. These days I've generally moved on to Raspberry Silicon chips (RP2040 and RP2350), both with micropython for simple projects, and the arduino core from Earle Philhower. My local community college has recently made the same transition away from PICAXE in favor of the Raspberry Silicon offerings.

I'm still really nostalgic for the PICAXE family, but these days I find that the limitations of BASIC get in the way more often than they help, and the lack of any updates to the hardware for well over a decade doesn't help either. I did enjoy the challenge of the resource limitations, and still find myself occasionally doing a project that ends up using a PICAXE if I already have some old hardware that's set up well for it.

Aside from a total rewrite to make a similar firmware that runs MicroPython instead of BASIC, I'm not sure exactly what the solution is though, but it seems generally that something needs to change if PICAXE wants to stay relevant. Or maybe a way that the BASIC could be integrated inline with direct compiled C or Python? There's interesting approaches that could be possible, but I'm guessing Rev-Ed doesn't have the resources to build something like that these days. If they ever do eventually close and discontinue selling the PICAXE chips or maintaining the software, I hope they'll at least open source the projects to benefit the community.

Edit with a couple additional thoughts: One niche that I find PICAXE chips particularly well suited for, in a way that few more popular modern microcontrollers are, is in their ability to be used with small simple chips (such as the 08M2), that need very little support circuitry and tolerate a wide range of voltages. Personally my dream IC for a lot of projects would be 08M2 sized, with native i2c slave support (memory-mapped to scratchpad or similar like on the X2 chips would be perfect), and the ability to program them directly over USB with various languages. I guess that's kinda more just describing the Raspberry Silicon again with those latter criteria, but that's a big part of why they've been such a big hit in modern projects. Meanwhile they definitely don't meet those former criteria, they're much more particular with their recommended/required voltage regulators, a required set of passives (including an odd custom polarized inductor), external flash chip, etc. A PICAXE meanwhile needs what? A vaguely smooth voltage source and a single pull down resistor. Of course ultimately that's more a trait of the underlying PIC, but still, I think the PICAXE concept could hold a lot of potential still for some more modernized hardware, even if it also needs a bit of a paradigm shift for the software to fully keep up.
 
Last edited:
Yet another long-time senior member of the community checking in (the forum was such a great read years ago, so many fascinating projects and discussions), god I can't believe it's been 15 years since the M2 chips came out, I remember being so excited for them, and it seemed like X3 or M3 series would inevitably be out a few years later. These days I've generally moved on to Raspberry Silicon chips (RP2040 and RP2350), both with micropython for simple projects, and the arduino core from Earle Philhower. My local community college has recently made the same transition away from PICAXE in favor of the Raspberry Silicon offerings.

I'm still really nostalgic for the PICAXE family, but these days I find that the limitations of BASIC get in the way more often than they help, and the lack of any updates to the hardware for well over a decade doesn't help either. I did enjoy the challenge of the resource limitations, and still find myself occasionally doing a project that ends up using a PICAXE if I already have some old hardware that's set up well for it.

Aside from a total rewrite to make a similar firmware that runs MicroPython instead of BASIC, I'm not sure exactly what the solution is though, but it seems generally that something needs to change if PICAXE wants to stay relevant. Or maybe a way that the BASIC could be integrated inline with direct compiled C or Python? There's interesting approaches that could be possible, but I'm guessing Rev-Ed doesn't have the resources to build something like that these days. If they ever do eventually close and discontinue selling the PICAXE chips or maintaining the software, I hope they'll at least open source the projects to benefit the community.

Edit with a couple additional thoughts: One niche that I find PICAXE chips particularly well suited for, in a way that few more popular modern microcontrollers are, is in their ability to be used with small simple chips (such as the 08M2), that need very little support circuitry and tolerate a wide range of voltages. Personally my dream IC for a lot of projects would be 08M2 sized, with native i2c slave support (memory-mapped to scratchpad or similar like on the X2 chips would be perfect), and the ability to program them directly over USB with various languages. I guess that's kinda more just describing the Raspberry Silicon again with those latter criteria, but that's a big part of why they've been such a big hit in modern projects. Meanwhile they definitely don't meet those former criteria, they're much more particular with their recommended/required voltage regulators, a required set of passives (including an odd custom polarized inductor), external flash chip, etc. A PICAXE meanwhile needs what? A vaguely smooth voltage source and a single pull down resistor. Of course ultimately that's more a trait of the underlying PIC, but still, I think the PICAXE concept could hold a lot of potential still for some more modernized hardware, even if it also needs a bit of a paradigm shift for the software to fully keep up.
I would argue that it isn't BASIC that is the limitation but the hardware and the way PicAxe BASIC is run as interpreted code.

I have been programming for many years and love the PicAxe devices and especially the simulator. For reasons of speed and code space I have moved to a fully compiled BASIC that runs on the "native" PIC devices. With this I've been able to write some quite impressive programs that have required me to use a PIC18F27Q43 as my program exceeds the 64k offered by the device I previously used.

All my programs have been written in BASIC and have been sold commercially. I'm very close to retiring, but were I not, I'd still be using BASIC and singing its praises. I love BASIC and see no limits in what the language can achieve given the inspiration and imagination.
 
@tmfkam

Your post intrigues me

If you don't mind...

How may I program PIC18F27Q43 in BASIC please?

How much must I pay for suitable BASIC compiler?

Regards, Robin from UK
 
@hex - Check out a product called Great Cow Basic ... it's a free Basic compiler for 8-bit PIC chips ... you'll need a PICKIT to burn the code to the chip (or, to burn a serial bootloader).
 
@tmfkam

Your post intrigues me

If you don't mind...

How may I program PIC18F27Q43 in BASIC please?

How much must I pay for suitable BASIC compiler?

Regards, Robin from UK
Indeed, as BPowell replied, Great Cow Basic. The latest release with an integrated editor covers the possibility of using almost any programmer you can imagine. I use one by NSDSP as it is blindingly fast and when you switch from one device to another it doesn't need 'updating' like PicKit always seems to.

GCB is free and has excellent support for the latest PIC devices and AT (Mega and Tiny) devices too.
 
In this thread I would like to focus on persuading Rev-Ed to modernize the Picaxe line itself (and which could be done in a simple way, as I feel that it is still an excellent comcept, as other contributers have testified here). Alternatives are there as well of course, but the Picaxe is the key subject of this forum.
 
Perhaps Rev-Ed no longer have enough resource any more to develop new product, any company that stagnates its product for so long is bound to be on a downwards spiral; it costs a lot to get in people to do the work and will there be any profit to show at the end, perhaps not.
As there has never been any published road-map for future PicAxe development, then the future is uncertain....
 
Rev-Ed had serious competition over the last years with the Micro:bit and Rpi Pico. What is not clear to me is if PicAxe is still used in schools in UK or it has been replaced. Schools seems to be the main source of income for Red-Ed.
 
I've just come back to electronics after a break and want to get back to Picaxe projects again but the programming tools for Linux seem somewhat out of date and picaxecloud.com just times out.

Does anyone have any recommendations? So far, I've been running Axepad in an Ubuntu 14 VM.

Thanks in advance,

Jools
A bit late, but I've got a few recommendations for anyone that still wants to use PICAXE on an operating system that isn't still being natively supported by Rev-Ed: I've written a preprocessor tool that (amongst other features, such as replicating/reimplementing many otherwise PE6-only features) integrates with the PICAXE compilers, and (as a feature that's been in an experimental state since 2023, but now I've finally gone to the effort of fixing up and releasing), now supports integrating directly with the picaxecloud online compilers, allowing it to be run on any operating system that has access to python 3 and the ability to make web requests.

Also I believe I ran into the same issue as you did while I was testing and preparing the online compiler feature for release, at some point the URL for picaxe cloud seems to have been changed from supporting https://picaxecloud.com, to instead only supporting access via https://www.picaxecloud.com, which likely explains why it timed out when you tried to use it, assuming you didn't explicitly include the `www`.
 
Back
Top