I learnt Picaxe basic and then wanted to convert my programs to GCB. The syntax differences could be the big stepping stone as well as the flash device and the hardware differences.
So I'm willing to write a guide and wondered a/ worth bothering with...b/ I got it...I don't care...........z/ good idea, I'll help..............c/ don't know....I always voted monster ravin loony party
CDRIVE maybe??
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I disagree sorry William.
I converted various programs from picaxe to GCB so have experience.
How many people use GCB as their 1st pic programming language...are there data statistic published results?
So I guess I'm the only person who although knew assembler wanted to have a simpler option and used picaxe then discovered gcb but had to learn another system,could have learnt c,but didn't wouldn't find a conversion help useful. Well fair comment,I won't bother.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was thinking no servo command in gcb, no arrays in picaxe,no serout 1,2,3,4,5,6,7,8 in gcb etc.
You might say converting is easy. So why can't other gcb team not understand picaxe basic?
We don't want any riff raff using gcb attitude seems a waste of effort.
Last edit: stan cartwright 2017-04-28
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Paul. The picaxe forum has users that use arduino but find c difficult and find picaxe basic doable.Some said they'd tried GCB but it was too complicated. I stopped using Picaxe but the transition took a while. Picaxe is quite low level and appreciating the wider command set and math priority differences would help a beginner get going faster. I say beginner,some picaxe users have been using it for ages. Me,5 months. arduino c,never used it.
Then there's the hard ware. I made my own picaxe boards but most buy one. Using a pic and you need a programmer,board,icp,supply,etc. bit complicated but an arduino is more like picaxe ie buy a board,plug it in usb and you're away and the terminal works like picaxe.
A comparison of arduino or picaxe to GCB programming.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"I was thinking no servo command in gcb, no arrays in picaxe,no serout 1,2,3,4,5,6,7,8 in gcb etc. You might say converting is easy. So why can't other gcb team not understand picaxe basic?
We don't want any riff raff using gcb attitude seems a waste of effort."
I will take the servo command as an example. Look at the Picaxe implementtion of Servo. Picaxe "servo" is internally interrupt driven and requires 2 timers. The chip can only operate at certain speeds for it to work. Picaxe Servo conflicts with other Picaxe commands that also require the of either timer1 or timer2 or that can be affected by a system interrupt. These conflicts often result in servo glitches, inaccurate delays and serial comms failures. But it generally works good enough for toy robots and such.
GCB is so flexible and the choice of Chips is so wide, that there are many possible methods to control a servo or multiple servos. Writing a guide just for explaing the various possible methods of controlling servos using GCB on a wide range of chips would take a lot of time in compiling the data, testing code and then writing it up so a newbie could understand. Im guessing a least 10 pages plus example code. And the person who wrote it would need to be an expert in servo control, MCU hardware, timers, Picaxe Basic and Great Cow Basic. This is only for Servos.. Imagine how difficlut and time consuming it would be to cover everything.
As far as comment impying that gcb team members have an attitude that Picaxe users are "riff raff" and unwelcome, this is presumptive, misguided and far from the truth. All are welcome, especially Picaxe users as that is where I got started using BASIC with microcontrollers.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This thread is getting a bit odd because absolutely nobody here on GCB has made me feel unwelcome because I came here from Picaxe. I've been nothing but impressed with the aid I've received. GCB is awesome and so are the contributing members!
I LOVE THIS PLACE!
CJ
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I suppose so. Some things like code works faster can cause head scratching. The recommendation is "forget picaxe".hmmm..? If GCB got a foot hold in the uk education electronics curriculum then the existing picaxe users might need a conversion table.Some things like servo don't exist in GCB but looking at GCB include it's lots of #if def .....for different controllers,lcds,etc. so could be implemented.The "standard" servo command is just an interrupt and pulseout but most picaxe users,correct me,don't know what an interrupt is and setting one up isn't trivial,but they know how to use the servo command.
rif-raf comment was what I thought some people's thoughts about picaxe and hence it's users,something about sycophantic. :)
Arduino c system users using GCB must be strange,like basic users using c or does eveyone learn basic first,not nowadays I guess. Arduino is "standard libs" and third party includes.Picaxe, you roll your own,there aren't any.
If you use one system you forget the previous and the team can't be bothered trying to remember stuff to answer questions maybe.
Last edit: stan cartwright 2017-05-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stan, your mind reading skills seem to be failing you. If you want to know wnat people think you might try asking them. But making up stuff like your "riff raff" comment is absurd.
Keeping things context is critical in understanding what someone is trying to comminucate communicate. This of couse assumes that the listener/reader actually wants to understand and is not just looking for "ammunition" that can be taken out of context to bulid a false narative or as a reason to get wonkey.
Heres what I actually posted (in context).
"Stan,
*You should not equate Picaxe stuff with PIC stuff. If you do you will likely be wrong. Picaxe >terminolgy does not generally apply to PIC or Great Cow Basic. So it's a good idea to forget Picaxe >stuff when dealing with PICs and Great cow Basic." *
.
The context was from your previous post where you posted an incorrect factoid about serial "port" portpin location based possiby upon Picaxe usage of certain pins for serial programming.
Did I say "Forget Picaxe"? No... I said "forget about picaxe stuff" referring to the terminology common to Picaxe and how it does not necessarily carry over to PICS in general or to Great Cow Basic. And I further qualified that with " when dealing with PIC's and GreatCow Basic".
So please try to read what is actually written and consider the context in which it was written before you go off making absurd ridiculous comments.
William
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry I was inexact with my quotes.Beam me up Scotty as Kirk never actually said along with There's life Jim but not as we know it.
Picaxe and GCB do the same things but use different names so if you've invested time learning picaxe and start using GCB you might convert a program and wonder why it doesn't work. I have, so thought a guide might be useful.
I converted a game to GCB and was asked why I used +255 instead of -1. I explained picaxe doesn't have negative numbers or signed integers. I've looked at the RosettaCode site and which basic example would convert easiest. It's time consuming. Freebasic has while-wend and other differences. Other basics use proc.
I think now,it would be of little use as it seems most picaxe users are happy except some also use arduino for it's hardware support ie include files..
a wee point-picaxe-- high portb.1:pulsin portb.1,var us as used for 1 pin us sensor sro4. that works but changing to GCB is not so straight forward. the picaxe generates the 10us delay by changing portb.1 dir automatically.
Last edit: stan cartwright 2017-05-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, I am brand new to GCBASIC. I come from the PICAXE users world. I hate reading all the forum arguments that are going nowhere. The first response should be an example solution.
What I'm looking for is actual code samples that show
the PICAXE serout C.1,T4800_4,(132,5,112,46)
PICAXE command serout, PIN C.1, BAUD 4800, Data (132,5,112,46)
converted to a GCBASIC example.
Simple lines of code in GCBASIC to do the same job from header, declarations to program end.
Last edit: wperko 2021-08-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
https://picaxe.com/basic-commands/serial-rs232-interfacing/serout/
Picaxe condenses a lot into a a command. gcb is simpler/different... got to set chip,baud,port before "data" as in link.
I've asked for picaxe to gcb serial conversion on this forum before for my own us and for others who have used picaxe and want to use gcb.
gcb does software serial and hardware serial and so many pics and avr to cover.
Someone explain better please. Gcb is worth using, you'll be doing much more but there's differences to picaxe...lots...but your code will run MUCH! faster and runs on pic or arduino uno/nano or even logic green328...like a pic at 128MHz.
If I used a picaxe 28x2, in gcb it would be #chip 18f26k20,64
that is the pic and clock speed
then look at help for setting up serial. Hardware serial needs the hwserial pins to be defined.
Someone please explain this better, show a help example maybe.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Wow! this is an old thread. For the record picaxe is a good system. Gcb is a better system.
Even Evan used picaxe.
More gcb users the better.
There's 2 versions of gcb... one for spectrum users and one for bbc users.
In one you use basic basic and the other you use functions, variable aliases and loads of very interesting stuff.
Either way you can get a working prog. Tidy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@wperko please start a new thread as @William Roth suggested.
It will be interesting . I was never much good with picaxe but got some projects posted.
Nice people on their forum.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I learnt Picaxe basic and then wanted to convert my programs to GCB. The syntax differences could be the big stepping stone as well as the flash device and the hardware differences.
So I'm willing to write a guide and wondered a/ worth bothering with...b/ I got it...I don't care...........z/ good idea, I'll help..............c/ don't know....I always voted monster ravin loony party
CDRIVE maybe??
Would be a rather large undertaking and I suspect not worth the time and effort.
I disagree sorry William.
I converted various programs from picaxe to GCB so have experience.
How many people use GCB as their 1st pic programming language...are there data statistic published results?
So I guess I'm the only person who although knew assembler wanted to have a simpler option and used picaxe then discovered gcb but had to learn another system,could have learnt c,but didn't wouldn't find a conversion help useful. Well fair comment,I won't bother.
I was thinking no servo command in gcb, no arrays in picaxe,no serout 1,2,3,4,5,6,7,8 in gcb etc.
You might say converting is easy. So why can't other gcb team not understand picaxe basic?
We don't want any riff raff using gcb attitude seems a waste of effort.
Last edit: stan cartwright 2017-04-28
An interresting project which could help a beginer to get started and undestand the GCB envioroment.
Hi Paul. The picaxe forum has users that use arduino but find c difficult and find picaxe basic doable.Some said they'd tried GCB but it was too complicated. I stopped using Picaxe but the transition took a while. Picaxe is quite low level and appreciating the wider command set and math priority differences would help a beginner get going faster. I say beginner,some picaxe users have been using it for ages. Me,5 months. arduino c,never used it.
Then there's the hard ware. I made my own picaxe boards but most buy one. Using a pic and you need a programmer,board,icp,supply,etc. bit complicated but an arduino is more like picaxe ie buy a board,plug it in usb and you're away and the terminal works like picaxe.
A comparison of arduino or picaxe to GCB programming.
As I see it this forum has enough GCB 'Wiz-Kids' to walk any GCB nube through converting Picaxe Basic to GCB.
CJ
*Posted by Stan: *
I will take the servo command as an example. Look at the Picaxe implementtion of Servo. Picaxe "servo" is internally interrupt driven and requires 2 timers. The chip can only operate at certain speeds for it to work. Picaxe Servo conflicts with other Picaxe commands that also require the of either timer1 or timer2 or that can be affected by a system interrupt. These conflicts often result in servo glitches, inaccurate delays and serial comms failures. But it generally works good enough for toy robots and such.
GCB is so flexible and the choice of Chips is so wide, that there are many possible methods to control a servo or multiple servos. Writing a guide just for explaing the various possible methods of controlling servos using GCB on a wide range of chips would take a lot of time in compiling the data, testing code and then writing it up so a newbie could understand. Im guessing a least 10 pages plus example code. And the person who wrote it would need to be an expert in servo control, MCU hardware, timers, Picaxe Basic and Great Cow Basic. This is only for Servos.. Imagine how difficlut and time consuming it would be to cover everything.
As far as comment impying that gcb team members have an attitude that Picaxe users are "riff raff" and unwelcome, this is presumptive, misguided and far from the truth. All are welcome, especially Picaxe users as that is where I got started using BASIC with microcontrollers.
This thread is getting a bit odd because absolutely nobody here on GCB has made me feel unwelcome because I came here from Picaxe. I've been nothing but impressed with the aid I've received. GCB is awesome and so are the contributing members!
I LOVE THIS PLACE!
CJ
I suppose so. Some things like code works faster can cause head scratching. The recommendation is "forget picaxe".hmmm..? If GCB got a foot hold in the uk education electronics curriculum then the existing picaxe users might need a conversion table.Some things like servo don't exist in GCB but looking at GCB include it's lots of #if def .....for different controllers,lcds,etc. so could be implemented.The "standard" servo command is just an interrupt and pulseout but most picaxe users,correct me,don't know what an interrupt is and setting one up isn't trivial,but they know how to use the servo command.
rif-raf comment was what I thought some people's thoughts about picaxe and hence it's users,something about sycophantic. :)
Arduino c system users using GCB must be strange,like basic users using c or does eveyone learn basic first,not nowadays I guess. Arduino is "standard libs" and third party includes.Picaxe, you roll your own,there aren't any.
If you use one system you forget the previous and the team can't be bothered trying to remember stuff to answer questions maybe.
Last edit: stan cartwright 2017-05-10
Stan, your mind reading skills seem to be failing you. If you want to know wnat people think you might try asking them. But making up stuff like your "riff raff" comment is absurd.
Keeping things context is critical in understanding what someone is trying to comminucate communicate. This of couse assumes that the listener/reader actually wants to understand and is not just looking for "ammunition" that can be taken out of context to bulid a false narative or as a reason to get wonkey.
Heres what I actually posted (in context).
.
The context was from your previous post where you posted an incorrect factoid about serial "port" portpin location based possiby upon Picaxe usage of certain pins for serial programming.
Did I say "Forget Picaxe"? No... I said "forget about picaxe stuff" referring to the terminology common to Picaxe and how it does not necessarily carry over to PICS in general or to Great Cow Basic. And I further qualified that with " when dealing with PIC's and GreatCow Basic".
So please try to read what is actually written and consider the context in which it was written before you go off making absurd ridiculous comments.
William
I'm sorry I was inexact with my quotes.Beam me up Scotty as Kirk never actually said along with There's life Jim but not as we know it.
Picaxe and GCB do the same things but use different names so if you've invested time learning picaxe and start using GCB you might convert a program and wonder why it doesn't work. I have, so thought a guide might be useful.
I converted a game to GCB and was asked why I used +255 instead of -1. I explained picaxe doesn't have negative numbers or signed integers. I've looked at the RosettaCode site and which basic example would convert easiest. It's time consuming. Freebasic has while-wend and other differences. Other basics use proc.
I think now,it would be of little use as it seems most picaxe users are happy except some also use arduino for it's hardware support ie include files..
a wee point-picaxe-- high portb.1:pulsin portb.1,var us as used for 1 pin us sensor sro4. that works but changing to GCB is not so straight forward. the picaxe generates the 10us delay by changing portb.1 dir automatically.
Last edit: stan cartwright 2017-05-11
Hi, I am brand new to GCBASIC. I come from the PICAXE users world. I hate reading all the forum arguments that are going nowhere. The first response should be an example solution.
What I'm looking for is actual code samples that show
the PICAXE serout C.1,T4800_4,(132,5,112,46)
PICAXE command serout, PIN C.1, BAUD 4800, Data (132,5,112,46)
converted to a GCBASIC example.
Simple lines of code in GCBASIC to do the same job from header, declarations to program end.
Last edit: wperko 2021-08-13
Hi and Welcome
Best to start a new thread for this instead of tagging on to the end of an old one.
It will get more views
William
https://picaxe.com/basic-commands/serial-rs232-interfacing/serout/
Picaxe condenses a lot into a a command. gcb is simpler/different... got to set chip,baud,port before "data" as in link.
I've asked for picaxe to gcb serial conversion on this forum before for my own us and for others who have used picaxe and want to use gcb.
gcb does software serial and hardware serial and so many pics and avr to cover.
Someone explain better please. Gcb is worth using, you'll be doing much more but there's differences to picaxe...lots...but your code will run MUCH! faster and runs on pic or arduino uno/nano or even logic green328...like a pic at 128MHz.
If I used a picaxe 28x2, in gcb it would be #chip 18f26k20,64
that is the pic and clock speed
then look at help for setting up serial. Hardware serial needs the hwserial pins to be defined.
Someone please explain this better, show a help example maybe.
Wow! this is an old thread. For the record picaxe is a good system. Gcb is a better system.
Even Evan used picaxe.
More gcb users the better.
There's 2 versions of gcb... one for spectrum users and one for bbc users.
In one you use basic basic and the other you use functions, variable aliases and loads of very interesting stuff.
Either way you can get a working prog. Tidy.
@wperko please start a new thread as @William Roth suggested.
It will be interesting . I was never much good with picaxe but got some projects posted.
Nice people on their forum.
Moved to new thread
Last edit: William Roth 2021-08-14
@williamroth
Code sample look great.