from:"Rob CJ"

Re: [jallib] Linux executable

2024-05-30 Thread Rob CJ

Hi Vasi,

I uploaded the static version. I did some checking of older version of the JAL 
compiler and I saw it was a static version before.

Not sure why the original Makefile did not have this option.

Anyway it will be in the next bee-package. Compiler version is still the same 
btw.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: maandag 27 mei 2024 23:47
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Linux executable

Many say that AppImage can be the solution on the long term.. I personally 
can't make it work... But I use some applications that come in AppImage 
format I think this is a way to provide dynamically compiled apps to any 
Linux, but you have to package all teh required libraries. If you forget one, 
it won't work. It will be the only working solution for a dynamic app that uses 
dynamic libraries like Qt... but jalv2 does not use such libraries and is 
easier to compile it statically. But of course, you can try AppImage and decide 
if is worth the effort.

On Mon, May 27, 2024 at 8:25 PM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I did the following test:
-) Build the compiler without the static on my Ubuntu laptop on which I got the 
GLIBC problem.
-) Ran that compiler on my Laptop running Virtual Box and Linux Mint. Got the 
GLIBC error
-) Build the compiler with the static on my Ubuntu laptop on which I got the 
GLIBC problem.
-) Ran that compiler on my Laptop running Virtual Box and Linux Mint. Did not 
get the GLIBC error

Screenshot of both runs on my Linux Mint version:

[cid:ii_18fbc0106b1cb971f161]

So that seems to work nicely.

One question though. Somebody suggested me to have a look at the Appimage 
format:
https://docs.appimage.org/packaging-guide/index.html

I did not look into that yet, but is that also an option?

Kind regards,

Rob






Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens vasi vasi 
mailto:funl...@gmail.com>>
Verzonden: zondag 26 mei 2024 15:07
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Linux executable

This discussion or a similar subject was here some time ago... the compiler 
becomes an educational tool, when you write books about it, with examples and 
specific libraries and that book must remain relevant in time, with a compiler 
and projects still usable. As is possible in WIndows. In Linux, you get this 
with a statically linked compiler. This compiler does not use or need a dynamic 
loader. Ask Kyle if you don't get it.

On Sun, May 26, 2024 at 3:52 PM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Sorry Rob,

that really is not our problem. We do not statlically ling glibc. We statically 
link our executable that do NOT use any shared lib, so it does not need a 
dynamic loader. Is that simple. Statically linking you app (where is possible) 
gives you the freedom to run on ANY Linux distribution, old or new. Again, 
nothing to do with glibc. And also, musl has absolutely nothing to do with 
glibc.  Compiling it dynamically, it means it will... but I already explained 
you why you don't need to create such vulnerability in Linux.

On Sun, May 26, 2024 at 11:10 AM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

Thanks for the info.

I made an error before and adding static works. The size of the compiler is 
then more than doubled to about 1.2 Mbyte and it still works OK.

I will do a test on another computer where I got issues with the GLIBC to see 
if that is gone.

But I also read that it is not recommeded to do this, see: 
https://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged

So it looks that one problem might then be replaced by another problem.  Are 
there any other JAL users that have problems with the Linux version of jalv2?

"If it ain't broken don't fix it" 

Kind regards,

Rob




Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens vasi vasi 
mailto:funl...@gmail.com>>
Verzonden: zondag 26 mei 2024 03:13
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Linux executable

You can check with the following command if you executable is static:
$=>  ldd jalv2-native
And you must get the following message:
not a dynamic executable

Or, you can install MIdnight Commander (it looks like Norton COmmander from 
MS-DOS) with
sudo apt install mc
then run it, navigate to the jalv2 executable, position the bas/cursor over it 
and press F3 button. After a red dialog that announces you that there are no 
symbols, press enter and you will get a window with details about the 
executable.  You get more info than using just th

Re: [jallib] Linux executable

2024-05-27 Thread Rob CJ

Hi Vasi,

I did the following test:
-) Build the compiler without the static on my Ubuntu laptop on which I got the 
GLIBC problem.
-) Ran that compiler on my Laptop running Virtual Box and Linux Mint. Got the 
GLIBC error
-) Build the compiler with the static on my Ubuntu laptop on which I got the 
GLIBC problem.
-) Ran that compiler on my Laptop running Virtual Box and Linux Mint. Did not 
get the GLIBC error

Screenshot of both runs on my Linux Mint version:

[cid:cfa1192b-5b4a-4c53-849e-394e25c37a62]

So that seems to work nicely.

One question though. Somebody suggested me to have a look at the Appimage 
format:
https://docs.appimage.org/packaging-guide/index.html

I did not look into that yet, but is that also an option?

Kind regards,

Rob






Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: zondag 26 mei 2024 15:07
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Linux executable

This discussion or a similar subject was here some time ago... the compiler 
becomes an educational tool, when you write books about it, with examples and 
specific libraries and that book must remain relevant in time, with a compiler 
and projects still usable. As is possible in WIndows. In Linux, you get this 
with a statically linked compiler. This compiler does not use or need a dynamic 
loader. Ask Kyle if you don't get it.

On Sun, May 26, 2024 at 3:52 PM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Sorry Rob,

that really is not our problem. We do not statlically ling glibc. We statically 
link our executable that do NOT use any shared lib, so it does not need a 
dynamic loader. Is that simple. Statically linking you app (where is possible) 
gives you the freedom to run on ANY Linux distribution, old or new. Again, 
nothing to do with glibc. And also, musl has absolutely nothing to do with 
glibc.  Compiling it dynamically, it means it will... but I already explained 
you why you don't need to create such vulnerability in Linux.

On Sun, May 26, 2024 at 11:10 AM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

Thanks for the info.

I made an error before and adding static works. The size of the compiler is 
then more than doubled to about 1.2 Mbyte and it still works OK.

I will do a test on another computer where I got issues with the GLIBC to see 
if that is gone.

But I also read that it is not recommeded to do this, see: 
https://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged

So it looks that one problem might then be replaced by another problem.  Are 
there any other JAL users that have problems with the Linux version of jalv2?

"If it ain't broken don't fix it" 

Kind regards,

Rob




Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens vasi vasi 
mailto:funl...@gmail.com>>
Verzonden: zondag 26 mei 2024 03:13
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Linux executable

You can check with the following command if you executable is static:
$=>  ldd jalv2-native
And you must get the following message:
not a dynamic executable

Or, you can install MIdnight Commander (it looks like Norton COmmander from 
MS-DOS) with
sudo apt install mc
then run it, navigate to the jalv2 executable, position the bas/cursor over it 
and press F3 button. After a red dialog that announces you that there are no 
symbols, press enter and you will get a window with details about the 
executable.  You get more info than using just the ldd command.

On Sun, May 26, 2024 at 4:00 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
this is the Makefile.inc I used

On Sun, May 26, 2024 at 3:50 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Using musl-gcc, with -Werror and -fPIC removed and adding -static to LFLAGS, I 
get a size of 530272 bytes, statically linked and striped.  LinuxMint LMDE 6 
here.

musl library is a very small library compared to glibc.

On Sun, May 26, 2024 at 3:34 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
I never heard that you are not allowed to create static executables!! Any linux 
provide also a set of static libraries. Only certain libraries are dynamic and 
these days, you do not get a static version of glibc. So, don't worry, you can 
compile jalv2 statically, it won't include glibc. You don't need musl, I will 
look into it, but it is not needed.

On Thu, May 23, 2024 at 10:51 PM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I tried this:

  *
sudo apt -y install musl-tools
  *
Added: -static in the Makefile.inc to the linker flag
  *
Changed (as a hack): $(CC) by musl-gcc

Compiled the compiler but the size is exactly the same with and without the 
-static option. I would expect the file to be bigger for the static version.

Any suggestions?

Kind regards,

Rob

_

Re: [jallib] Linux executable

2024-05-26 Thread Rob CJ

Hi Vasi,

Thanks for the info.

I made an error before and adding static works. The size of the compiler is 
then more than doubled to about 1.2 Mbyte and it still works OK.

I will do a test on another computer where I got issues with the GLIBC to see 
if that is gone.

But I also read that it is not recommeded to do this, see: 
https://stackoverflow.com/questions/57476533/why-is-statically-linking-glibc-discouraged

So it looks that one problem might then be replaced by another problem.  Are 
there any other JAL users that have problems with the Linux version of jalv2?

"If it ain't broken don't fix it" 

Kind regards,

Rob




Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: zondag 26 mei 2024 03:13
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Linux executable

You can check with the following command if you executable is static:
$=>  ldd jalv2-native
And you must get the following message:
not a dynamic executable

Or, you can install MIdnight Commander (it looks like Norton COmmander from 
MS-DOS) with
sudo apt install mc
then run it, navigate to the jalv2 executable, position the bas/cursor over it 
and press F3 button. After a red dialog that announces you that there are no 
symbols, press enter and you will get a window with details about the 
executable.  You get more info than using just the ldd command.

On Sun, May 26, 2024 at 4:00 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
this is the Makefile.inc I used

On Sun, May 26, 2024 at 3:50 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
Using musl-gcc, with -Werror and -fPIC removed and adding -static to LFLAGS, I 
get a size of 530272 bytes, statically linked and striped.  LinuxMint LMDE 6 
here.

musl library is a very small library compared to glibc.

On Sun, May 26, 2024 at 3:34 AM vasi vasi 
mailto:funl...@gmail.com>> wrote:
I never heard that you are not allowed to create static executables!! Any linux 
provide also a set of static libraries. Only certain libraries are dynamic and 
these days, you do not get a static version of glibc. So, don't worry, you can 
compile jalv2 statically, it won't include glibc. You don't need musl, I will 
look into it, but it is not needed.

On Thu, May 23, 2024 at 10:51 PM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I tried this:

  *
sudo apt -y install musl-tools
  *
Added: -static in the Makefile.inc to the linker flag
  *
Changed (as a hack): $(CC) by musl-gcc

Compiled the compiler but the size is exactly the same with and without the 
-static option. I would expect the file to be bigger for the static version.

Any suggestions?

Kind regards,

Rob


Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens Rob CJ 
mailto:rob...@hotmail.com>>
Verzonden: donderdag 23 mei 2024 19:32
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Linux executable

Hi Vasi,

I am no Linux expert (always using Windows) and I had a quick look on the 
internet and I read that you are not allowed to statically link GLIBC due to 
licensing.

I saw some info about musl but no clue (yet) what to do.

Any hints would help.

Thanks.

Kind regards,

Rob



Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens vasi vasi 
mailto:funl...@gmail.com>>
Verzonden: woensdag 22 mei 2024 19:43
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Linux executable

Hi Rob,

No problems for me because I recompiled it to be statically linked.

On Wed, May 22, 2024 at 8:01 PM Rob CJ 
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I had problems with GLIBC version 2.29. In order to solve that I recompiled the 
JAL compiler with an older version of gcc and that solved that issue.

I can have a look a linking it statically. Are you - or other JAL users - 
experiencing problems with the current version (2.5r8) of the JAL compiler?

Kind regards,

Rob


Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>> namens vasi vasi 
mailto:funl...@gmail.com>>
Verzonden: woensdag 22 mei 2024 13:38
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com> 
mailto:jallib@googlegroups.com>>
Onderwerp: [jallib] Linux executable

Hi Rob,

I see you provide executables for linux that are dynamically linked...
A statically linked executable can work on both glibc and musl based 
distributions (Alpine and Void linux as two main examples as musl platforms) no 
matter on which platform this was compiled (be it glibc or musl), and it can 
also work on much older linux distros. It will help also with old projects tha

Re: [jallib] Linux executable

2024-05-23 Thread Rob CJ

Hi Vasi,

I tried this:

*
sudo apt -y install musl-tools
*
Added: -static in the Makefile.inc to the linker flag
*
Changed (as a hack): $(CC) by musl-gcc

Compiled the compiler but the size is exactly the same with and without the
-static option. I would expect the file to be bigger for the static version.

Any suggestions?

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: donderdag 23 mei 2024 19:32
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Linux executable

Hi Vasi,

I am no Linux expert (always using Windows) and I had a quick look on the
internet and I read that you are not allowed to statically link GLIBC due to
licensing.

I saw some info about musl but no clue (yet) what to do.

Any hints would help.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: woensdag 22 mei 2024 19:43
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Linux executable

Hi Rob,

No problems for me because I recompiled it to be statically linked.

On Wed, May 22, 2024 at 8:01 PM Rob CJ
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I had problems with GLIBC version 2.29. In order to solve that I recompiled the
JAL compiler with an older version of gcc and that solved that issue.

I can have a look a linking it statically. Are you - or other JAL users -
experiencing problems with the current version (2.5r8) of the JAL compiler?

Kind regards,

Rob

Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>> namens vasi vasi
mailto:funl...@gmail.com>>
Verzonden: woensdag 22 mei 2024 13:38
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>>
Onderwerp: [jallib] Linux executable

Hi Rob,

I see you provide executables for linux that are dynamically linked...
A statically linked executable can work on both glibc and musl based
distributions (Alpine and Void linux as two main examples as musl platforms) no
matter on which platform this was compiled (be it glibc or musl), and it can
also work on much older linux distros. It will help also with old projects that
require a specific version of jalv2 compiler. Right now, a static link edit is
possible only by modifying the Makefiles at source level.

I have a lot of old applications dynamically linked that do not work on today's
computers and operating systems. Is not only that many are written in an old
standard, not supported by the compiler, but in many cases, even the GUI
libraries are not available anymore. And jalv2 can be linked statically. Maybe
you don't know, but there are "recent" changes in GLIBC that will prevent
shared programs to work on linux distributions that have GLIBC at a lower
version than 2.34 (don't know if is the case of the jalv2 compiler though).

I think is in Jalv2 interest to avoid this vulnerability of Linux/UNIX world.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D9%3D%3DPqrr7ffPaVDg3qSYTiwQKKhbroLpWucDDNjb9XrVA%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D9%3D%3DPqrr7ffPaVDg3qSYTiwQKKhbroLpWucDDNjb9XrVA%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D-nUyCPhH2a%2B3xgLg9U-O-WX3qXi5rhgY4pVemaF3AG6w%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D-nUyCPhH2a%2B3xgLg9U-O-WX3qXi5rhgY4pVemaF3AG6w%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving e

Re: [jallib] Linux executable

2024-05-23 Thread Rob CJ

Hi Vasi,

I am no Linux expert (always using Windows) and I had a quick look on the
internet and I read that you are not allowed to statically link GLIBC due to
licensing.

I saw some info about musl but no clue (yet) what to do.

Any hints would help.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: woensdag 22 mei 2024 19:43
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Linux executable

Hi Rob,

No problems for me because I recompiled it to be statically linked.

On Wed, May 22, 2024 at 8:01 PM Rob CJ
mailto:rob...@hotmail.com>> wrote:
Hi Vasi,

I had problems with GLIBC version 2.29. In order to solve that I recompiled the
JAL compiler with an older version of gcc and that solved that issue.

I can have a look a linking it statically. Are you - or other JAL users -
experiencing problems with the current version (2.5r8) of the JAL compiler?

Kind regards,

Rob

Hi Rob,

I think is in Jalv2 interest to avoid this vulnerability of Linux/UNIX world.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D-nUyCPhH2a%2B3xgLg9U-O-WX3qXi5rhgY4pVemaF3AG6w%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D-nUyCPhH2a%2B3xgLg9U-O-WX3qXi5rhgY4pVemaF3AG6w%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16374EF7B6C5195047F9FE5DE6F42%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Linux executable

2024-05-22 Thread Rob CJ

Hi Vasi,

I had problems with GLIBC version 2.29. In order to solve that I recompiled the
JAL compiler with an older version of gcc and that solved that issue.

I can have a look a linking it statically. Are you - or other JAL users -
experiencing problems with the current version (2.5r8) of the JAL compiler?

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: woensdag 22 mei 2024 13:38
Aan: jallib@googlegroups.com
Onderwerp: [jallib] Linux executable

Hi Rob,

I think is in Jalv2 interest to avoid this vulnerability of Linux/UNIX world.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D9%3D%3DPqrr7ffPaVDg3qSYTiwQKKhbroLpWucDDNjb9XrVA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16373F60F98E826FCC3DA47AE6EB2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Seven segment library

2024-05-06 Thread Rob CJ

Hi Vasile,

I uploaded the updated library using your example. No breaking changes.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens zet.weeh

Verzonden: maandag 6 mei 2024 15:07
Aan: jallib@googlegroups.com
Onderwerp: RE: [jallib] Seven segment library

Hi Rob

When I started with JAL I sometimes get a message in the compiler: deprecated.

Then I knew something changed in the library.

I did not see it the last years but maybe a suggestion.

I think it was a good way to update a library.

Peter

Van: jallib@googlegroups.com [mailto:jallib@googlegroups.com] Namens vasi vasi
Verzonden: maandag 6 mei 2024 00:03
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Seven segment library

Anyway, the developer that stole the 25th char, should get in front, admit it
and return the char... Just kidding. 

On Mon, May 6, 2024 at 12:57 AM vasi vasi
mailto:funl...@gmail.com>> wrote:

Hi Rob

For the 25 value I used the h_small char (h)...

But the library I was working on is for gcbasic. No problem in sending it to
you, is easy to read.

Anyway, it might need the validation of others... or a rearranging of the
chars...

Ah, just found the old one I corrected and with some additions... back in
2014.. but it has a different arrangement...

As I said, it needs some supervision...

On Sun, May 5, 2024 at 11:32 AM Rob CJ
mailto:rob...@hotmail.com>> wrote:

Hi Vasi,

I had a quick look and normally you should move 26 to 25 and 27 to 26 but that
would mean that exisiting application might not work correctly anymore.

An alternative would be to add 25 and use that for all segments off which is
the same a space.

If users to not mind the move (the first option) then I can change that.

Suggestions are welcome.

Kind regards,

Rob

Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>> namens Rob CJ
mailto:rob...@hotmail.com>>
Verzonden: zondag 5 mei 2024 07:48
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Seven segment library

Hi Vasi,

Thanks for reporting is. Since you already fixed it can you give me the exact
code change that you made?

Ik will upload it for the next build.

Thanks

Kind regards,

Rob

Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>> namens vasi vasi
mailto:funl...@gmail.com>>
Verzonden: zondag 5 mei 2024 06:37
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>>
Onderwerp: [jallib] Seven segment library

Hi guys,

There is a problem with seven_segment.jal and if I remember, is not the first
time I signaled this.

If you look at it, there is a missing value, you jump from 24 to 26. in both
the comment section where you document the library, and in the code section.

The code from the value 25 is missing... now, not too big of a deal, as
everything is functional, but, there is no really a 27 value (it will give you
an error) and the 26 value will not return what you would expect to return.
Hopefully, I am clearer now than back then in explaining the problem...

Not a problem for me, I had my own corrections and adds... just saying...

Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D_qxMjuhCtEM_PV2GCG1WM%2BHv0pbh5%2Bi3fF-dXs6tP75w%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D_qxMjuhCtEM_PV2GCG1WM%2BHv0pbh5%2Bi3fF-dXs6tP75w%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEB3C890A8323109E4C4E61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEB3C890A8323109E4C4E61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

Re: [jallib] Seven segment library

2024-05-05 Thread Rob CJ

Hi Vasi,

I had a quick look and normally you should move 26 to 25 and 27 to 26 but that
would mean that exisiting application might not work correctly anymore.

An alternative would be to add 25 and use that for all segments off which is
the same a space.

If users to not mind the move (the first option) then I can change that.

Suggestions are welcome.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: zondag 5 mei 2024 07:48
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Seven segment library

Hi Vasi,

Thanks for reporting is. Since you already fixed it can you give me the exact
code change that you made?

Ik will upload it for the next build.

Thanks

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: zondag 5 mei 2024 06:37
Aan: jallib@googlegroups.com
Onderwerp: [jallib] Seven segment library

Hi guys,
There is a problem with seven_segment.jal and if I remember, is not the first
time I signaled this.

If you look at it, there is a missing value, you jump from 24 to 26. in both
the comment section where you document the library, and in the code section.

Not a problem for me, I had my own corrections and adds... just saying...
--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D_qxMjuhCtEM_PV2GCG1WM%2BHv0pbh5%2Bi3fF-dXs6tP75w%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D_qxMjuhCtEM_PV2GCG1WM%2BHv0pbh5%2Bi3fF-dXs6tP75w%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEB3C890A8323109E4C4E61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEB3C890A8323109E4C4E61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163719F2267C9E1658855EEAE61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Seven segment library

2024-05-04 Thread Rob CJ

Hi Vasi,

Thanks for reporting is. Since you already fixed it can you give me the exact
code change that you made?

Ik will upload it for the next build.

Thanks

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: zondag 5 mei 2024 06:37
Aan: jallib@googlegroups.com
Onderwerp: [jallib] Seven segment library

Hi guys,
There is a problem with seven_segment.jal and if I remember, is not the first
time I signaled this.

If you look at it, there is a missing value, you jump from 24 to 26. in both
the comment section where you document the library, and in the code section.

Not a problem for me, I had my own corrections and adds... just saying...
--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D_qxMjuhCtEM_PV2GCG1WM%2BHv0pbh5%2Bi3fF-dXs6tP75w%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEB3C890A8323109E4C4E61D2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: Problem with jallist group

2024-04-24 Thread Rob CJ

Hi David,

For some unknown reason  your messages are seen as spam and are blocked until I 
or Matt release them. I have been looking for a fix but could not find it. We 
could try the following. I could delete you as member and if you then send a 
message you are added again. Shall we try that?

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of David VB 

Sent: Tuesday, April 23, 2024 7:46:41 PM
To: jallib 
Subject: [jallib] Re: Problem with jallist group

(I do have the solution for Hans problem "PicKit3 problems").
It is off-topic here, but is it OK I post it here anyway, since I cannot post 
anything more on jallist ?

Kr

David

Le mardi 23 avril 2024 à 19:36:49 UTC+2, David VB a écrit :
Hi,

I tried to post some answers on the jallist group, but all my messages were 
deleted without an apparent reason.

We wil see if my message here will be published.

In the meantime, I quit the jallist group, hoping this could solve the problem, 
but now I cannot ask to reintegrate it

To whom can I ask ?

Thanks,

Kind regards,

David



--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/83ffa1c1-e90b-4643-a335-7a873efdc89dn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16373B2A6FE4DD66095706A7E6102%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Assembling

2024-04-16 Thread Rob CJ

Hi Vasi,

I think not but you should be able to  create a hexfile using the mplabx 
assembler since the syntax should be correct.

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of vasi vasi 

Sent: Tuesday, April 16, 2024 11:02:33 AM
To: jallib@googlegroups.com 
Subject: [jallib] Assembling

Can jalv2 generate a hex file from its own (generated) asm file if provided 
with only that?

--
Vasi

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CABsDq%3D-u1tFwiCh5oBtK-6Hdh%3DsZQ0gP4j8KD2GQAyotsdh%2BQQ%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637C4A3CBB292F2BBD41472E6082%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PWM modules in PIC16F177* family

2024-04-14 Thread Rob CJ

Hi David,

I did some testing this weekend and made some fixes to the PWM files. I 
uploaded them to GitHub so they should be part of the next bee-package.

About your design. I assume that you want to control the ADJ pin with a DAC? I 
do not think it will work since the ADJ is used to continuously keep the output 
voltage at the right level and that can only be done realtime.

What you could do is use a digital potentiometer (but I assume the resolution 
is too low) to feedback - a part of - the signal to the ADJ input.

Good luck figuring it out.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens David VB 

Verzonden: zondag 14 april 2024 18:26
Aan: jallib 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

About the voltage drop, I can live with that up to 500 or even 600 mV.
The problem is the dissipation of the transistor if it has to pass 1.2 A with a 
drop of 3 V as VCE  (Voltage rail = 5 V, Vbase = VEmitter = 2 V).   This is 
more than 3.5 W to dissipate.
Multiply this by 6 channels.

>From there, on the eevblog forum, we discuss the possibility to use a small 
>fake-LM2596 (actual LM2576) switching module from chinese resellers, one per 
>channel..
I could adjust them with the help of one DAC buffered by an OPA configured as 
Unity gain (all within the PIC).

Problems:
- There are not enough independant 10-bit DAC's (only 3) and OPA's (only 3) in 
the PIC16F1778 I use for 6 channels
- I am still struggling to understand exactly how to drive the ADJ (or 
Feedback) pin of the regulator



This is off topic here, but if you got ideas, feel free to join the discussion 
on weblog

(For the mails, strangely, I only receive a notification when *I* and only me 
post a subject to either list (jallist or jallib) )

Le vendredi 12 avril 2024 à 19:04:37 UTC+2, Rob CJ a écrit :
Hi David,

Strange that you are not notified. On Google Groups it says that you would get 
an e-mail every time something happens.

The PWM should work since I tested all your channels except for PWM12 since I 
do not have that PIC but the code is the same as PWM11.

I am still in the process of cleaning up some code. Next to that I removed the 
16-bit code for PWM7, 8, 9, and 10  (I mention that in the pwm_common.jal file) 
since they do not yet exist for 16-bit, only 10-bit. I do that because I apply 
YAGNI (You Ain't Gonna Need It) and only add code for which the hardware exists.

I think I will test the other PWM channels this weekend and will then upload 
the final version for PWM1..PWM12 but let me know if you got it working.

Last week I discovered something new. There are PICs with 10-bit PWM where you 
can assign another timer to the PWM output than only timer 2 so that each PWM 
(like the 16-bit version) can have a different frequency. Since there is no 
request for that I will not create that now.

About your project. If you use an emitter follower you will not be able to 
create 5 Volt due to the voltage drop. You almost need to make some kind of 
buck converter ...

Good luck with your project.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens David VB 

Verzonden: vrijdag 12 april 2024 18:44

Aan: jallib 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family
Hi Rob,

Thanks for your efforts !
(No matter what, I cannot subsribe to the emails again and have to check 
directly the list on the website  that's why I didin't see your messages 
before)

This week-end, I hope to be able to experiment more with this project.
I also openend a discussion on eevblog for a rather totally different subject 
(but it's about the same project)
You can see it here: 
https://www.eevblog.com/forum/beginners/variable-voltage-with-high-current/

In short, I have, from one PIC, to drive six channels that may use up the 1.2 
or 1.5 A (very worst case).
I MUST have the voltage varying between around 2 V and around 5 V.PWM is 
allowaed to control, but the ouptut voltage must be somewhat clean
And now I am struggling: ADC to control a switching regulator, or (filtered) 
PWM to control a emitter-follower transisotr.
Tough choice

A lot of experimentation foreseen this week-end

Kind regards,

David

Le samedi 6 avril 2024 à 19:55:46 UTC+2, Rob CJ a écrit :
Hi David,

I got it working. The nice thing about these 16-bit PWM's is that each has its 
own timer register. This means that the frequency can be set for each of these 
PWM's individually which is not the case for the 10-bit PICs that all seem to 
use Timer2. For the 10-bit you can only change the duty cycle individually.

I still need to clean things up and check with other PICs what the names of the 
PWM modules are.

For example PWM5 seems to be a 10-bit PWM for the PIC16F18323 but is a 16-bit 
PWM for the 16F1778.

In the attached zip-file I only did the 10-bit and 16-bit modifications for  
PWM5 and PWM6 and I only created the 16-bit PWM version for PWM11 and

Re: [jallib] PWM modules in PIC16F177* family

2024-04-12 Thread Rob CJ

Hi David,

Strange that you are not notified. On Google Groups it says that you would get 
an e-mail every time something happens.

The PWM should work since I tested all your channels except for PWM12 since I 
do not have that PIC but the code is the same as PWM11.

I am still in the process of cleaning up some code. Next to that I removed the 
16-bit code for PWM7, 8, 9, and 10  (I mention that in the pwm_common.jal file) 
since they do not yet exist for 16-bit, only 10-bit. I do that because I apply 
YAGNI (You Ain't Gonna Need It) and only add code for which the hardware exists.

I think I will test the other PWM channels this weekend and will then upload 
the final version for PWM1..PWM12 but let me know if you got it working.

Last week I discovered something new. There are PICs with 10-bit PWM where you 
can assign another timer to the PWM output than only timer 2 so that each PWM 
(like the 16-bit version) can have a different frequency. Since there is no 
request for that I will not create that now.

About your project. If you use an emitter follower you will not be able to 
create 5 Volt due to the voltage drop. You almost need to make some kind of 
buck converter ...

Good luck with your project.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens David VB 

Verzonden: vrijdag 12 april 2024 18:44
Aan: jallib 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi Rob,

Thanks for your efforts !
(No matter what, I cannot subsribe to the emails again and have to check 
directly the list on the website  that's why I didin't see your messages 
before)

This week-end, I hope to be able to experiment more with this project.
I also openend a discussion on eevblog for a rather totally different subject 
(but it's about the same project)
You can see it here: 
https://www.eevblog.com/forum/beginners/variable-voltage-with-high-current/

In short, I have, from one PIC, to drive six channels that may use up the 1.2 
or 1.5 A (very worst case).
I MUST have the voltage varying between around 2 V and around 5 V.PWM is 
allowaed to control, but the ouptut voltage must be somewhat clean
And now I am struggling: ADC to control a switching regulator, or (filtered) 
PWM to control a emitter-follower transisotr.
Tough choice

A lot of experimentation foreseen this week-end

Kind regards,

David

Le samedi 6 avril 2024 à 19:55:46 UTC+2, Rob CJ a écrit :
Hi David,

I got it working. The nice thing about these 16-bit PWM's is that each has its 
own timer register. This means that the frequency can be set for each of these 
PWM's individually which is not the case for the 10-bit PICs that all seem to 
use Timer2. For the 10-bit you can only change the duty cycle individually.

I still need to clean things up and check with other PICs what the names of the 
PWM modules are.

For example PWM5 seems to be a 10-bit PWM for the PIC16F18323 but is a 16-bit 
PWM for the 16F1778.

In the attached zip-file I only did the 10-bit and 16-bit modifications for  
PWM5 and PWM6 and I only created the 16-bit PWM version for PWM11 and PWM12 so 
that at least you can use it for your project.

As said, I need to check other PICs to see for which modules there is overlap 
in the names  for 10-bit and 16-bit.

I could not test PWM12 since my 16F1778 does not have it but I assume it works.

Let me know if it works for you too.

Thanks

Kind regards,

Rob



Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: zaterdag 6 april 2024 10:40

Aan: jal...@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

Update. I did a test but it does not yet work for the 16-bit PWM's. I am in the 
process of getting it working.

Will give you an update as soon as I have more info.

Kind regards,

Rob

Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 5 april 2024 19:49
Aan: jal...@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

I did a quick program change.

I just extended the existing 6 standard pwm's to 12 and all compiles. In the 
sample program I am using pwm 3, 4, 5, 6, 9 and 11 since that is what the 
PIC16F1778 has on board so you may have changed the number for your PIC (that's 
why I made it up to 12).

Did not test it yet but you can give it a try. I attached a zip-file but not 
sure if it is blocked or not.

I will see if it works this weekend.

If the zipfile does not work I can send it via wetransfer.

Kind regards,

Rob




Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 5 april 2024 18:51
Aan: jal...@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

When I took over the device file generation scripts of Rob Hamerling I also got 
all his - hundreds - of PIC samples and  because of that I do have a PIC16F1778 
which is of the same family

Re: [jallib] Re: Next release Jallib-1.9.0

2024-04-10 Thread Rob CJ

Hi Matt,

The link in this e-mail and the link on the download page are not the same. For
the full zip-file the links are as follows:

This e-mail:
http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib%20full%20jallib_full-1.9.0beta2.zip

Download page:
http://justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib%20full%20jallib_full-1.9.0beta.zip

The link on the download page gives the page not foud error (www is missing).

I downloaded the beta release from the link in the e-mail and I think the
release is OK.

So if there are no other remarks you could make the final release.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Matthew Schinkel

Verzonden: maandag 8 april 2024 21:33
Aan: jallib
Onderwerp: Re: [jallib] Re: Next release Jallib-1.9.0

Hi, it's on the download page http://www.justanotherlanguage.org/downloads

jallib full
jallib_full-1.9.0beta2.zip
jallib-1.9.0beta2.zip
jallib_full_win_setup-1.9.0beta2.exe

On Monday, April 8, 2024 at 12:41:30 PM UTC-4 rob...@hotmail.com wrote:
Hi Matt,

I cannot download the new beta.

[https://groups.google.com/group/jallib/attach/2919d7059e3b1/image.png?part=0.1=1]

Kind regards,

Rob

Van: jal...@googlegroups.com namens Matthew Schinkel

Verzonden: maandag 8 april 2024 14:02
Aan: jallib
Onderwerp: [jallib] Re: Next release Jallib-1.9.0

Hi, I've added the updated I2C and CHANGELOG as Rob had asked.

Please try it so I may put out the official release in a few days.

Thanks,
Matt.

On Sunday, March 24, 2024 at 4:18:12 PM UTC-4 pinhe...@gmail.com wrote:
Hello Matt,

We are a small community, and we love JAL. I do not create a lot of projects
(this is my hobby, not my work), but since I discovered jal I always use it for
my projects.
And I enjoy it.
As a former Pascal programmer, you'll see what I find so compelling about jal.

I would take the opportunity of this new release to thank you for your
commitment to keep jal alive.
And all the others who contribute to the lib, the compiler, the vs-code add-on,
jaledit, the documentations. and I certainly miss someone (sorry for that)

Thanks to you all to make jal a real thing, a really GOOD language, affordable,
easy to grasp.

Thank you, really!

David (aka Pinhead, because of the Cenobite in Hellraiser and (good) horror
movies in general, and because I love pinball :-) )

Le samedi 16 mars 2024 à 22:32:16 UTC+1, Matthew Schinkel a écrit :
Hi Everyone,

I'll be putting together another release, Jallib-1.9.0. Please put in any
changes you need by next week. I'll create a beta package. Let me know if more
time is needed.

Thanks,
Matt.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/1b7387a7-fa01-4fd1-a85a-a605e832f128n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/a90590bb-33a2-4f61-9fb8-fc75a9122ef9n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637C8CCEE7E107716E39EA6E6062%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Greenhouse

2024-04-10 Thread Rob CJ

Hi Jos,

Good to hear that it works. Will add it later to GitHub so it becomes part of
the latest bee-package (after the release is done).

About the programming issue. I also have it sometimes and it depends on the
PICKit3 I am using. I have two - different - Chinese copies and one of them is
more sensitive to this problem than the other.

It may help to add sufficient decoupling capacitors close to the PIC.

Enjoy your Greenhouse .

Kind regards,

Rob

Van: jallib@googlegroups.com namens Hans van
Veldhuizen
Verzonden: woensdag 10 april 2024 11:57
Aan: jallib
Onderwerp: Re: [jallib] Greenhouse

Hello Jos,
I have the same problem every now and then. I use Pckit3 plus. then use the
following tricks.
Read, Erase and then check if it is empty.
Remove from the circuit and erase directly and check with a regular 5 volt
charger. Usually it's fine again.
Hans

Op woensdag 10 april 2024 om 09:43:34 UTC+2 schreef jos smans:
hi Vsurcan,
I think not it is a hardware issue because i reprogrammed the pic but also pic
18f4455 which programmed perfectly, so i think not it is a power connection
,programmer speed or something else.
Anywhere thanks for suggestions.
kind regards
Jos

Op wo 10 apr 2024 om 07:20 schreef vsurducan :
That is a programming issue not a library issue. Check hardware, supply, cable
length, wires with cold solder or even not connected, programmer speed,
programmer software malfunction. I guess you need pickit3 plus or pickit3 minus
to program that pic. With a correct definition file.

On Tue, Apr 9, 2024 at 10:45 PM jos smans wrote:
hi Rob,
I have compiled the 18f4431 and a hex file was made, but after programming
the pic with pickit 3, the error occurred "programming failed at program memory
address 0x00".Maybe the adc library must, as you said before, changed.
kind regards
Jos

Op di 9 apr 2024 om 21:09 schreef jos smans :
Hi Rob,
Thank you very much for your support. It works excellent.
Kind regards
Jos

Op di 9 apr 2024 om 19:48 schreef Rob CJ :
Hi Jos,

The problem is in the ADC library. Apparently the 18F4431 has a different way
of selecting the ADC channel that I have never seen before.

I made a quick fix and added the channel selection for your PIC but to the
attached ADC library did not test this so you should give it a try. The code I
added could be simplified but that is something that could be done later.

So place the attached ADC library in the directory of your program recompile it
and let me know if it works.

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens jos smans

Verzonden: dinsdag 9 april 2024 16:56
Aan: jallib
Onderwerp: [jallib] Greenhouse

Good day, i have a problem with a program to make automatic my greenhouse.
With pic 18f4455, it works fine, but not with pic 18f4431.I think its a adc
fault but i am not sure.
Can someone help me? thanks
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/eaae0d75-efe1-4bdc-b6ce-ca87db6dd560n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/eaae0d75-efe1-4bdc-b6ce-ca87db6dd560n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637171120AC6BA343AB4AFFE6072%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637171120AC6BA343AB4AFFE6072%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAMK-nAftmPUHcT-g_kMvgQW0HykAT40z2yZi7z_cKAsxjbO%2BUQ%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAMK-nAftmPUHcT-g_kMvgQW0HykAT40z2yZi7z_cKAsxjbO%2BUQ%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qs-jwoRSyH81N8gqEEgXhp1fRuJ_OkfYku55YFm5dK_hg%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAM%2Bj4qs-jwoRSyH81N8gqEEgXhp1fRuJ_OkfYku55YFm5d

Re: [jallib] Greenhouse

2024-04-09 Thread Rob CJ

Hi Jos,

The problem is in the ADC library. Apparently the 18F4431 has a different way
of selecting the ADC channel that I have never seen before.

So place the attached ADC library in the directory of your program recompile it
and let me know if it works.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens jos smans

Verzonden: dinsdag 9 april 2024 16:56
Aan: jallib
Onderwerp: [jallib] Greenhouse

Good day, i have a problem with a program to make automatic my greenhouse.
With pic 18f4455, it works fine, but not with pic 18f4431.I think its a adc
fault but i am not sure.
Can someone help me? thanks
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/eaae0d75-efe1-4bdc-b6ce-ca87db6dd560n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637171120AC6BA343AB4AFFE6072%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

adc.jal
Description: adc.jal

Re: [jallib] Re: Next release Jallib-1.9.0

2024-04-09 Thread Rob CJ

Hi Matt,

I tried that yesterday but it didn’t work. Will try again later today.

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of Matthew 
Schinkel 
Sent: Monday, April 8, 2024 9:33:26 PM
To: jallib 
Subject: Re: [jallib] Re: Next release Jallib-1.9.0

Hi, it's on the download page http://www.justanotherlanguage.org/downloads

jallib full 
jallib_full-1.9.0beta2.zip
jallib-1.9.0beta2.zip
jallib_full_win_setup-1.9.0beta2.exe

On Monday, April 8, 2024 at 12:41:30 PM UTC-4 rob...@hotmail.com wrote:
Hi Matt,

I cannot download the new beta.

[https://groups.google.com/group/jallib/attach/2919d7059e3b1/image.png?part=0.1=1]

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Matthew Schinkel 

Verzonden: maandag 8 april 2024 14:02
Aan: jallib 
Onderwerp: [jallib] Re: Next release Jallib-1.9.0

Hi, I've added the updated I2C and CHANGELOG as Rob had asked.

Please try it so I may put out the official release in a few days.

Thanks,
Matt.

On Sunday, March 24, 2024 at 4:18:12 PM UTC-4 pinhe...@gmail.com wrote:
Hello Matt,

We are a small community, and we love JAL.   I do not create a lot of projects 
(this is my hobby, not my work), but since I discovered jal I always use it for 
my projects.
And I enjoy it.
As a former Pascal programmer, you'll see what I find so compelling about jal.

I would take the opportunity of this new release to thank you for your 
commitment to keep jal alive.
And all the others who contribute to the lib, the compiler, the vs-code add-on, 
jaledit, the documentations. and I certainly miss someone (sorry for that)

Thanks to you all to make jal a real thing, a really GOOD language, affordable, 
easy to grasp.

Thank you, really!

David (aka Pinhead, because of the Cenobite in Hellraiser and (good) horror 
movies in general, and because I love pinball :-) )

Le samedi 16 mars 2024 à 22:32:16 UTC+1, Matthew Schinkel a écrit :
Hi Everyone,

I'll be putting together another release, Jallib-1.9.0. Please put in any 
changes you need by next week. I'll create a beta package. Let me know if more 
time is needed.

Thanks,
Matt.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/1b7387a7-fa01-4fd1-a85a-a605e832f128n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/a90590bb-33a2-4f61-9fb8-fc75a9122ef9n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637C9C9CD4D4CFD31994C58E6072%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: Next release Jallib-1.9.0

2024-04-08 Thread Rob CJ

Hi Matt,

I cannot download the new beta.

[cid:469f3ec8-da17-4c1d-b2f0-856f3053cacb]

Kind regards,

Rob

Van: jallib@googlegroups.com namens Matthew Schinkel

Verzonden: maandag 8 april 2024 14:02
Aan: jallib
Onderwerp: [jallib] Re: Next release Jallib-1.9.0

Hi, I've added the updated I2C and CHANGELOG as Rob had asked.

Please try it so I may put out the official release in a few days.

Thanks,
Matt.

On Sunday, March 24, 2024 at 4:18:12 PM UTC-4 pinhe...@gmail.com wrote:
Hello Matt,

Thanks to you all to make jal a real thing, a really GOOD language, affordable,
easy to grasp.

Thank you, really!

David (aka Pinhead, because of the Cenobite in Hellraiser and (good) horror
movies in general, and because I love pinball :-) )

Le samedi 16 mars 2024 à 22:32:16 UTC+1, Matthew Schinkel a écrit :
Hi Everyone,

I'll be putting together another release, Jallib-1.9.0. Please put in any
changes you need by next week. I'll create a beta package. Let me know if more
time is needed.

Thanks,
Matt.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/1b7387a7-fa01-4fd1-a85a-a605e832f128n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637CD60ADF24FBD37AA8294E6002%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PWM modules in PIC16F177* family

2024-04-06 Thread Rob CJ

Hi David,

I got it working. The nice thing about these 16-bit PWM's is that each has its 
own timer register. This means that the frequency can be set for each of these 
PWM's individually which is not the case for the 10-bit PICs that all seem to 
use Timer2. For the 10-bit you can only change the duty cycle individually.

I still need to clean things up and check with other PICs what the names of the 
PWM modules are.

For example PWM5 seems to be a 10-bit PWM for the PIC16F18323 but is a 16-bit 
PWM for the 16F1778.

In the attached zip-file I only did the 10-bit and 16-bit modifications for  
PWM5 and PWM6 and I only created the 16-bit PWM version for PWM11 and PWM12 so 
that at least you can use it for your project.

As said, I need to check other PICs to see for which modules there is overlap 
in the names  for 10-bit and 16-bit.

I could not test PWM12 since my 16F1778 does not have it but I assume it works.

Let me know if it works for you too.

Thanks

Kind regards,

Rob



Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: zaterdag 6 april 2024 10:40
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

Update. I did a test but it does not yet work for the 16-bit PWM's. I am in the 
process of getting it working.

Will give you an update as soon as I have more info.

Kind regards,

Rob

Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 5 april 2024 19:49
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

I did a quick program change.

I just extended the existing 6 standard pwm's to 12 and all compiles. In the 
sample program I am using pwm 3, 4, 5, 6, 9 and 11 since that is what the 
PIC16F1778 has on board so you may have changed the number for your PIC (that's 
why I made it up to 12).

Did not test it yet but you can give it a try. I attached a zip-file but not 
sure if it is blocked or not.

I will see if it works this weekend.

If the zipfile does not work I can send it via wetransfer.

Kind regards,

Rob




Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 5 april 2024 18:51
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

When I took over the device file generation scripts of Rob Hamerling I also got 
all his - hundreds - of PIC samples and  because of that I do have a PIC16F1778 
which is of the same family and has 6 PWM's (three 10-bit and three 16-bit) so 
I could give it a try if I can extend the current PWM library with the 16-bit 
addition providing the same basic functionality.

Not sure how long it will take but will start this weekend.

Kind regards,

Rob



Van: jallib@googlegroups.com  namens David VB 

Verzonden: vrijdag 5 april 2024 15:49
Aan: jallib 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

To be honest, in my application, I need 6 PWM signals.
Since they must be equivalent to one another, I will use some 16-bits modules 
but without those new features, and with a duty cycle defined with only the 10 
MSB

So, as far as I am concerned, there is no need for a specific 16-bit PWM 
library now, but it would be a nice addition to the lib, just to keep its 
attractiveness in the future and avoid a technical debt when more and more 
PIC's will implement these new modules.

(The same goes for the ADCC module, the new CLB module)

I cannot commit to write a specific library since I can never be sure to be ok 
with all of the rules of the style guide, not to be extensive in the 
funcitonnalities written, but I can offer to send here some libraries to serve 
as a starting point, if someone can review and amend them as needed.

Kr,

D.

Le jeudi 4 avril 2024 à 19:12:22 UTC+2, Rob CJ a écrit :
Hi David,

In 2022 I added PWM5 and PWM6 like the previous pwm's.

What is foreseen is what is requested  (and there is a need for it).

So it can be straight forward to add the 10-bit PWM 9 and PWM 10 but not sure 
if there is a need for it.

For the 16-bit I think we need a complete new library, something like 
pwm16_hardware.jal and add more features. That may take quite some time.

Do you - or does anybody else - have plans to use the 16-bit pwm with all its 
nice features?

Kind regards,

Rob






Van: jal...@googlegroups.com  namens David VB 

Verzonden: woensdag 3 april 2024 23:14
Aan: jallib 
Onderwerp: [jallib] PWM modules in PIC16F177* family

Hi there,

It appears that the PIC16F177* family have PWM modules named up to PWM12, which 
is not foreseen in Jallib

Example: PIC16F1777 or 1779 have:
PWM3, PWM4, PWM9, PWM10 : 10 bits PWM modules
PWM5, PWM6, PWM11, PWM12 : 16 bits PWM modules (with more functionnalities as 
10-bit modules, such as four offset modes, and different operation modes)

Is there anything foreseen for those

Re: [jallib] PWM modules in PIC16F177* family

2024-04-06 Thread Rob CJ

Hi David,

Update. I did a test but it does not yet work for the 16-bit PWM's. I am in the
process of getting it working.

Will give you an update as soon as I have more info.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: vrijdag 5 april 2024 19:49
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

I did a quick program change.

I just extended the existing 6 standard pwm's to 12 and all compiles. In the
sample program I am using pwm 3, 4, 5, 6, 9 and 11 since that is what the
PIC16F1778 has on board so you may have changed the number for your PIC (that's
why I made it up to 12).

Did not test it yet but you can give it a try. I attached a zip-file but not
sure if it is blocked or not.

I will see if it works this weekend.

If the zipfile does not work I can send it via wetransfer.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: vrijdag 5 april 2024 18:51
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

When I took over the device file generation scripts of Rob Hamerling I also got
all his - hundreds - of PIC samples and because of that I do have a PIC16F1778
which is of the same family and has 6 PWM's (three 10-bit and three 16-bit) so
I could give it a try if I can extend the current PWM library with the 16-bit
addition providing the same basic functionality.

Not sure how long it will take but will start this weekend.

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: vrijdag 5 april 2024 15:49
Aan: jallib
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

To be honest, in my application, I need 6 PWM signals.
Since they must be equivalent to one another, I will use some 16-bits modules
but without those new features, and with a duty cycle defined with only the 10
MSB

So, as far as I am concerned, there is no need for a specific 16-bit PWM
library now, but it would be a nice addition to the lib, just to keep its
attractiveness in the future and avoid a technical debt when more and more
PIC's will implement these new modules.

(The same goes for the ADCC module, the new CLB module)

I cannot commit to write a specific library since I can never be sure to be ok
with all of the rules of the style guide, not to be extensive in the
funcitonnalities written, but I can offer to send here some libraries to serve
as a starting point, if someone can review and amend them as needed.

Kr,

Le jeudi 4 avril 2024 à 19:12:22 UTC+2, Rob CJ a écrit :
Hi David,

In 2022 I added PWM5 and PWM6 like the previous pwm's.

What is foreseen is what is requested  (and there is a need for it).

So it can be straight forward to add the 10-bit PWM 9 and PWM 10 but not sure
if there is a need for it.

For the 16-bit I think we need a complete new library, something like
pwm16_hardware.jal and add more features. That may take quite some time.

Do you - or does anybody else - have plans to use the 16-bit pwm with all its
nice features?

Kind regards,

Rob

Van: jal...@googlegroups.com namens David VB

Verzonden: woensdag 3 april 2024 23:14
Aan: jallib
Onderwerp: [jallib] PWM modules in PIC16F177* family

Hi there,

It appears that the PIC16F177* family have PWM modules named up to PWM12, which
is not foreseen in Jallib

Example: PIC16F1777 or 1779 have:
PWM3, PWM4, PWM9, PWM10 : 10 bits PWM modules
PWM5, PWM6, PWM11, PWM12 : 16 bits PWM modules (with more functionnalities as
10-bit modules, such as four offset modes, and different operation modes)

Is there anything foreseen for those in Jallib ?

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscrib

Re: [jallib] PWM modules in PIC16F177* family

2024-04-05 Thread Rob CJ

Hi David,

I did a quick program change.

Did not test it yet but you can give it a try. I attached a zip-file but not
sure if it is blocked or not.

I will see if it works this weekend.

If the zipfile does not work I can send it via wetransfer.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: vrijdag 5 april 2024 18:51
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

Hi David,

Not sure how long it will take but will start this weekend.

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: vrijdag 5 april 2024 15:49
Aan: jallib
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

(The same goes for the ADCC module, the new CLB module)

Kr,

Le jeudi 4 avril 2024 à 19:12:22 UTC+2, Rob CJ a écrit :
Hi David,

In 2022 I added PWM5 and PWM6 like the previous pwm's.

What is foreseen is what is requested  (and there is a need for it).

So it can be straight forward to add the 10-bit PWM 9 and PWM 10 but not sure
if there is a need for it.

For the 16-bit I think we need a complete new library, something like
pwm16_hardware.jal and add more features. That may take quite some time.

Do you - or does anybody else - have plans to use the 16-bit pwm with all its
nice features?

Kind regards,

Rob

Van: jal...@googlegroups.com namens David VB

Verzonden: woensdag 3 april 2024 23:14
Aan: jallib
Onderwerp: [jallib] PWM modules in PIC16F177* family

Hi there,

It appears that the PIC16F177* family have PWM modules named up to PWM12, which
is not foreseen in Jallib

Is there anything foreseen for those in Jallib ?

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637AAA978040122D51160CBE6032%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637AAA978040122D51160CB

Re: [jallib] PWM modules in PIC16F177* family

2024-04-05 Thread Rob CJ

Hi David,

When I took over the device file generation scripts of Rob Hamerling I also got 
all his - hundreds - of PIC samples and  because of that I do have a PIC16F1778 
which is of the same family and has 6 PWM's (three 10-bit and three 16-bit) so 
I could give it a try if I can extend the current PWM library with the 16-bit 
addition providing the same basic functionality.

Not sure how long it will take but will start this weekend.

Kind regards,

Rob



Van: jallib@googlegroups.com  namens David VB 

Verzonden: vrijdag 5 april 2024 15:49
Aan: jallib 
Onderwerp: Re: [jallib] PWM modules in PIC16F177* family

To be honest, in my application, I need 6 PWM signals.
Since they must be equivalent to one another, I will use some 16-bits modules 
but without those new features, and with a duty cycle defined with only the 10 
MSB

So, as far as I am concerned, there is no need for a specific 16-bit PWM 
library now, but it would be a nice addition to the lib, just to keep its 
attractiveness in the future and avoid a technical debt when more and more 
PIC's will implement these new modules.

(The same goes for the ADCC module, the new CLB module)

I cannot commit to write a specific library since I can never be sure to be ok 
with all of the rules of the style guide, not to be extensive in the 
funcitonnalities written, but I can offer to send here some libraries to serve 
as a starting point, if someone can review and amend them as needed.

Kr,

D.

Le jeudi 4 avril 2024 à 19:12:22 UTC+2, Rob CJ a écrit :
Hi David,

In 2022 I added PWM5 and PWM6 like the previous pwm's.

What is foreseen is what is requested  (and there is a need for it).

So it can be straight forward to add the 10-bit PWM 9 and PWM 10 but not sure 
if there is a need for it.

For the 16-bit I think we need a complete new library, something like 
pwm16_hardware.jal and add more features. That may take quite some time.

Do you - or does anybody else - have plans to use the 16-bit pwm with all its 
nice features?

Kind regards,

Rob






Van: jal...@googlegroups.com  namens David VB 

Verzonden: woensdag 3 april 2024 23:14
Aan: jallib 
Onderwerp: [jallib] PWM modules in PIC16F177* family

Hi there,

It appears that the PIC16F177* family have PWM modules named up to PWM12, which 
is not foreseen in Jallib

Example: PIC16F1777 or 1779 have:
PWM3, PWM4, PWM9, PWM10 : 10 bits PWM modules
PWM5, PWM6, PWM11, PWM12 : 16 bits PWM modules (with more functionnalities as 
10-bit modules, such as four offset modes, and different operation modes)

Is there anything foreseen for those in Jallib ?

Kind regards,

David



--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/0a1fcd7f-71a5-4350-be8f-8c4f19d17d5an%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637AAA978040122D51160CBE6032%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] [Request] I2c_hardware.jal : Option for user-selected bus speed

2024-04-04 Thread Rob CJ

Hi David,

I added option 3) to the library. Not yet tested and not yet uploaded but can 
you give it a try.

So define:
const I2C_USER_BUS_SPEED = 50_000

And give it a try. This version also has the user defined i2c_pins that you can 
use, solving 2 issues at the same time.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: donderdag 4 april 2024 19:33
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] [Request] I2c_hardware.jal : Option for user-selected 
bus speed

Hi David,

A few suggestions
Option 1
Why not add a value for 50 kHz, although we cannot enter 0.5.

Option 2
Or replace the 100 kHz by 50 kHz?
So instead of:
const _i2c_slowest = 127   -- (40 kHz @ 20 MHz Fosc)
Use:
const _i2c_slowest  = target_clock / 50_000 / 4 - 1 –- 50 kHz

Option 3
Another option would be to use a user defined constant, for example:
const I2C_USER_BUS_SPEED = 50_000

And then overrule everything by:
if defined(I2C_USER_BUS_SPEED) then
  spadd =  target_clock / I2C_USER BUS_SPEED / 4 - 1
else
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
   elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
   elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
   elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
   elsesspadd = _i2c_100khz  -- default
end if

Option 3) would be the most flexible.

Kind regards,

Rob




Van: jallib@googlegroups.com  namens David VB 

Verzonden: donderdag 4 april 2024 15:30
Aan: jallib 
Onderwerp: [jallib] [Request] I2c_hardware.jal : Option for user-selected bus 
speed

Hi,

I was struggling with an I2C LCD display until I found out on the manufacturer 
website that, due to a design flaw, the I²C bus speed should be 50 kHz
(for the record: 
https://support.newhavendisplay.com/hc/en-us/community/posts/9600301114775-NHD-0220D3Z-NSW-BBW-V3-using-I2C-dropping-characters
 )

My request here is to allow the user to define the sspadd value directly in his 
application by modifying the following code in i2c_hardware.jal

   -- set correct speed
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
   elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
   elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
   elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
   elsesspadd = _i2c_100khz  -- default
   end if

so that the user may override the default 100 kHz value:
by defining _i2c_bus_speed = 0xFF and initialize sspadd with the needed value 
in his application

   if _i2c_bus_speed != 0xFF then
 -- set correct speed
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
elsesspadd = _i2c_100khz  -- default
   end if
   end if

What do you think ?

Kind regards,

David


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/28c93aa1-8b14-4004-aa96-a4692f808654n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/28c93aa1-8b14-4004-aa96-a4692f808654n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637ABCF1E78FC9E3837C64EE63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637ABCF1E78FC9E3837C64EE63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16376DB7F985201ECB524ADDE63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.


i2c_hardware.jal
Description: i2c_hardware.jal

Re: [jallib] [Request] I2c_hardware.jal : Option for user-selected bus speed

2024-04-04 Thread Rob CJ

Hi David,

A few suggestions
Option 1
Why not add a value for 50 kHz, although we cannot enter 0.5.

Option 2
Or replace the 100 kHz by 50 kHz?
So instead of:
const _i2c_slowest = 127   -- (40 kHz @ 20 MHz Fosc)
Use:
const _i2c_slowest  = target_clock / 50_000 / 4 - 1 –- 50 kHz

Option 3
Another option would be to use a user defined constant, for example:
const I2C_USER_BUS_SPEED = 50_000

And then overrule everything by:
if defined(I2C_USER_BUS_SPEED) then
  spadd =  target_clock / I2C_USER BUS_SPEED / 4 - 1
else
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
   elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
   elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
   elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
   elsesspadd = _i2c_100khz  -- default
end if

Option 3) would be the most flexible.

Kind regards,

Rob




Van: jallib@googlegroups.com  namens David VB 

Verzonden: donderdag 4 april 2024 15:30
Aan: jallib 
Onderwerp: [jallib] [Request] I2c_hardware.jal : Option for user-selected bus 
speed

Hi,

I was struggling with an I2C LCD display until I found out on the manufacturer 
website that, due to a design flaw, the I²C bus speed should be 50 kHz
(for the record: 
https://support.newhavendisplay.com/hc/en-us/community/posts/9600301114775-NHD-0220D3Z-NSW-BBW-V3-using-I2C-dropping-characters
 )

My request here is to allow the user to define the sspadd value directly in his 
application by modifying the following code in i2c_hardware.jal

   -- set correct speed
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
   elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
   elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
   elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
   elsesspadd = _i2c_100khz  -- default
   end if

so that the user may override the default 100 kHz value:
by defining _i2c_bus_speed = 0xFF and initialize sspadd with the needed value 
in his application

   if _i2c_bus_speed != 0xFF then
 -- set correct speed
   if_i2c_bus_speed == 10 then sspadd = _i2c_1mhz
elsif _i2c_bus_speed ==  4 then sspadd = _i2c_400khz
elsif _i2c_bus_speed ==  1 then sspadd = _i2c_100khz
elsif _i2c_bus_speed ==  0 then sspadd = _i2c_slowest
elsesspadd = _i2c_100khz  -- default
   end if
   end if

What do you think ?

Kind regards,

David


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/28c93aa1-8b14-4004-aa96-a4692f808654n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637ABCF1E78FC9E3837C64EE63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PWM modules in PIC16F177* family

2024-04-04 Thread Rob CJ

Hi David,

In 2022 I added PWM5 and PWM6 like the previous pwm's.

What is foreseen is what is requested  (and there is a need for it).

So it can be straight forward to add the 10-bit PWM 9 and PWM 10 but not sure
if there is a need for it.

For the 16-bit I think we need a complete new library, something like
pwm16_hardware.jal and add more features. That may take quite some time.

Do you - or does anybody else - have plans to use the 16-bit pwm with all its
nice features?

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: woensdag 3 april 2024 23:14
Aan: jallib
Onderwerp: [jallib] PWM modules in PIC16F177* family

Hi there,

It appears that the PIC16F177* family have PWM modules named up to PWM12, which
is not foreseen in Jallib

Is there anything foreseen for those in Jallib ?

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ab0fbea9-025c-49bf-b37f-18159885fa2fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637704DAF3E97583B455407E63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] [Request] "Reset_code" function

2024-04-04 Thread Rob CJ

Hi David,

Why not just define some masks that you use to determine the type of reset that 
occured.  Since it it all too PIC specific I think you could not make a decent 
library forit.

If I look at the status bits you cannot uniquely identify which reset occured.

So you could do the following but as said you cannot uniquely identify what 
happend (example for a PIC16F19155).

var word RESET_STATUS at PCON0

const word RESET_POR  = 0b__0111_0011
const word RESET_TO_POR   = 0b__0111_ -- Same as PD
const word RESET_PD_POR   = 0b__0111_ -- Same as TO
const word RESET_BROWNOUT = 0b__0011_0011

-- Check reset type.
if (RESET_STATUS & RESET_POR) == RESET_POR then
   -- Power on reset.
elsif (RESET_STATUS & RESET_BROWNOUT) == RESET_BROWNOUT then
   -- Brownout reset/
end if


Kind regards,

Rob

Van: jallib@googlegroups.com  namens David VB 

Verzonden: woensdag 3 april 2024 21:32
Aan: jallib 
Onderwerp: Re: [jallib] [Request] "Reset_code" function

Hi,

Still looking for this kind of function, returning a simple code to reflect the 
reset condition of the PIC.

My main problem here is to know how to deal with the "u" (unchanged) bits

In other words: if I evaluate the conditions in the order given in the table 
(reproduced earlier), and taking only the O and 1 into account (ignoring u and 
x), will it work ?

Does anyone know of an applicaiton note (from microchip) on the subject ?

Kind regards,
David

Le vendredi 9 juin 2023 à 19:31:10 UTC+2, Rob CJ a écrit :
Hi David,

I was wondering what I should do this weekend .

BTW. I am on Holiday - in The Netherlands - and I had a quick look at some PICs 
and it looks as if it is different for various PICs also from the same range 
(12F/16F/18F). Initially I thought you could make a library but it seems that 
you then have to add a piece of code for each specific PIC and that is a lot of 
work because of the number of PICs that should be supported.

Of course we could start small with some PICs and extend it when needed but 
still it would be a library with high maintenance. Not sure if we should go 
that way.

But maybe someone else has a bright idea on this topic.

Kind regards,

Rob




Van: jal...@googlegroups.com  namens 
pinhe...@gmail.com 
Verzonden: vrijdag 9 juni 2023 15:44
Aan: jallib 
Onderwerp: [jallib] [Request] "Reset_code" function

Hi,

A suggestion to keep Rob busy this week-end ;-)

I often have to test the Reset condition at start-up of a program.

Since I'm lazy (of course), wouldn't it be useful to write a "reset_code" 
function who returns a code depending on the condition that issued a reset in 
the pic (POR, WDT, Reset instruction, Stack overflow) ?

See an example from a DS for PIC16F1777 where the reset_code could be 0 (for 
POR, which is a normal condition) to 11, one per line in the table

The difficulty here is to take into account for the various possibilities 
existing in different families of PICs.   which is why I post my request 
here

[Capture d’écran 2023-06-09 154308.jpg]

Any help/suggestion/commitment welcome.

Enjoy your day

David

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/7431f8b1-4c70-4bc3-a640-6c1a3cbef875n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/7431f8b1-4c70-4bc3-a640-6c1a3cbef875n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/4f1245ea-2911-4800-a0ec-391f6ff683a6n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/4f1245ea-2911-4800-a0ec-391f6ff683a6n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637079CC783C7B09F6FCD9DE63C2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Jallib 1.9.0 Beta is available

2024-04-02 Thread Rob CJ

Hi David,

I never worked with those configurable blocks but it can be interesting.

BTW. I think if you order at Digikey I thougt you also had to pay costs for
customs (I think I had to pay that a long time ago since the components came
from the USA).

If I am right you live in Belgium. An option would be to order the chip at
Reichelt in Germany. They are not every expensive and the shipment costs are OK
(some other suppliers use DTP or others who are very expensive in shipment
costs).

Just an idea to save money (I hope), Dutch habbit .

E.g.
https://www.reichelt.nl/nl/nl/mcu-picmicro-14-kb-32-mhz-pdip-20-pic16f13145-ep-p370198.html?=pos_6=1
[https://www.reichelt.nl/nl/nl/index.html?ACTION=13=3=370198=300=300=1=1=93b87ff1a50f5ce04f0e0fb0dee94337766c1f5e1e10f2514c626=true]<https://www.reichelt.nl/nl/nl/mcu-picmicro-14-kb-32-mhz-pdip-20-pic16f13145-ep-p370198.html?=pos_6=1>
PIC16F13145-EP - MCU, PICmicro, 14 KB, 32 MHz,
PDIP-20<https://www.reichelt.nl/nl/nl/mcu-picmicro-14-kb-32-mhz-pdip-20-pic16f13145-ep-p370198.html?=pos_6=1>
De PIC16F13145-microcontrollerfamilie biedt een effectieve methode voor de
implementatie van op hardware gebaseerde oplossingen. Door de introductie van
de CLB-randapparatuur (Configurable Logic [...]
www.reichelt.nl
Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: dinsdag 2 april 2024 16:26
Aan: jallib
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Rob,

Thanks for your answer.
I have just bought the Curiosity Nano 16F13145 board, but have not yet tested
it.
I have several other references of that family (16F131xx) in my basket since
they now become available on Digikey, but for those, I waited to buy them
because I would like to test the CLB first.

Unfortunately, it seems that the CLB is only usable with the synthesis tool
available online or from MPLABX, and that the produced output cannot be
retrieved as "something" that could be integrated in a program written outside
of MPLABX.

The ideal would have been to be able to retrieve a kind of include file that
could be used as asm (after transformation, of course). That way, it would
have been usable in jal.

But by reading the documentation, it appears that not all involved registers
are available to the user, and that the synthesized model is embedded during
programming phase only

Well, it remains a bit obsure for now, I will have to dig (much) deeper to
completely understand it.

Anyway, the new CLB was the primary reason I was interested in that family, but
if it unusable outside of MPLABX, then I will pass .

I'll keep you posted

Kind regards,

David

Le lundi 1 avril 2024 à 19:12:07 UTC+2, Rob CJ a écrit :
Hi David,

I can answer that. They are not yet in the release because I did not yet have a
sample to test them.

I can only request a limited amount of samples from Microchip.

Normally only tested device files are in the release.

But you can get access to the device files since I have already created them
and uploaded them to Github but as said are not yet in the release.

You can find them here:
https://github.com/jallib/jallib/tree/master/include/device
[https://ci6.googleusercontent.com/proxy/Da09DxmVLZWy0GiJVgeskuRgaK-fb-w8AT_3RbfzduHkbMC0Vr8kHEJ4hJ0YmrII7N3NeRjymJJC5P0BtW1PuFe6IBx0KyI5kLIUd8D42gT7ql0tW6pdAscTjFHdQDlJBvITJ67aV5XDpM2aXt7q6eP51pNuRxAyowK_hmo8J7bhQRK7=s0-d-e1-ft#https://opengraph.githubassets.com/747a2c58f59fbdc8094f9a6e3ea582e2653dcd87ba04df437e09bf59b880b7fd/jallib/jallib]<https://github.com/jallib/jallib/tree/master/include/device>
jallib/include/device at master ·
jallib/jallib<https://github.com/jallib/jallib/tree/master/include/device>
Automatically exported from
code.google.com/p/jallib<http://code.google.com/p/jallib> - jallib/jallib
github.com<http://github.com>
If you have used the device file and it all works, let me know because then I
can add them to the next bee-package (I think we should not change the contents
of the release now).

Kind regards,

Rob

Van: jal...@googlegroups.com namens David VB

Verzonden: maandag 1 april 2024 17:05

Aan: jallib
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available
Hi Matt,

Besides the comment of Rob about i2c_hardware.jal, there is another thing I'd
like to mention:

MPLABX 6.20 introduces the new 16F131xx family.
The new device files for that family are include in the Github, but are not
listed in the list of changes.
Will they be part of the release of jallib 1.9.0 ?

Thanks,

Kind regards

David

Le samedi 30 mars 2024 à 18:49:54 UTC+1, Rob CJ a écrit :
Hi Matt,

Thanks for adding the compiler.

Can you also add the latest i2c_hardware.jal and the last version of the
changelog (both were updated yesterday just before your release).

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Matthew Schi

Re: [jallib] Jallib 1.9.0 Beta is available

2024-04-01 Thread Rob CJ

Hi David,

I can answer that. They are not yet in the release because I did not yet have a
sample to test them.

I can only request a limited amount of samples from Microchip.

Normally only tested device files are in the release.

But you can get access to the device files since I have already created them
and uploaded them to Github but as said are not yet in the release.

You can find them here:
https://github.com/jallib/jallib/tree/master/include/device
[https://opengraph.githubassets.com/747a2c58f59fbdc8094f9a6e3ea582e2653dcd87ba04df437e09bf59b880b7fd/jallib/jallib]<https://github.com/jallib/jallib/tree/master/include/device>
jallib/include/device at master ·
jallib/jallib<https://github.com/jallib/jallib/tree/master/include/device>
Automatically exported from code.google.com/p/jallib - jallib/jallib
github.com
If you have used the device file and it all works, let me know because then I
can add them to the next bee-package (I think we should not change the contents
of the release now).

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: maandag 1 april 2024 17:05
Aan: jallib
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Matt,

Besides the comment of Rob about i2c_hardware.jal, there is another thing I'd
like to mention:

Thanks,

Kind regards

David

Le samedi 30 mars 2024 à 18:49:54 UTC+1, Rob CJ a écrit :
Hi Matt,

Thanks for adding the compiler.

Can you also add the latest i2c_hardware.jal and the last version of the
changelog (both were updated yesterday just before your release).

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Matthew Schinkel

Verzonden: zaterdag 30 maart 2024 17:04

Aan: jallib
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available
Hi Rob, I've added it to jallib-1.9.0beta.zip

The other files have it already.

Thanks,
Matt.

On Saturday, March 30, 2024 at 5:10:46 AM UTC-4 rob...@hotmail.com wrote:
Hi Matt,

I downloaded the zip file. Seems that the compiler is missing.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 30 maart 2024 08:52
Aan: jallib
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Matt,

This version does not yet have the change i2c_hardware.jal version which I
uploaded yesterday that solves the issue reportedby David.

Maybe I was too late and it missed the release.

Is it possible to add this to the final release?

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Matthew Schinkel

Verzonden: zaterdag 30 maart 2024 01:10
Aan: jallib
Onderwerp: [jallib] Jallib 1.9.0 Beta is available

Hi Everyone,

Jallib 1.9.0 Beta is available. Please download and test this. There will be an
official release after 2 weeks.

If any changes are needed please let me know.

http://www.justanotherlanguage.org/downloads
jallib full
jallib_full-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib%20full%20jallib_full-1.9.0beta.zip>
jallib-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib-1.9.0beta.zip>
jallib_full_win_setup-1.9.0beta.exe<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib_full_win_setup-1.9.0beta.exe>

Changes since 1.8.0

device files:
- Added 16f18026.jal, 16f18046.jal.
- Added 16f18054.jal, 16f18055.jal, 16f18074.jal, 16f18075.jal.
- Added 18f26q71.jal, 18f46q71.jal, 18f56q71.jal.
- Added 16f17114.jal, 16f17115.jal, 16f17124.jal, 16f17125.jal, 16f17144.jal,
16f17145.jal
- Added 16f18114.jal, 16f18115.jal, 16f18124.jal, 16f18125.jal, 16f18144.jal,
16f18145.jal
- Added 16f17156.jal, 16f17176.jal
- Added 16f17154.jal, 16f17155.jal, 16f17174.jal, 16f17175.jal
- Added 16f18154.jal, 16f18155.jal, 16f18174.jal, 16f18175.jal
- Added 16f18126.jal, 16f18146.jal.

externals:
- Added library rda5807m.jal, single-chip broadcast FM radio tuner.
- Update of rtc_3231.jal. Added functions for reading the set alarm times.
- Added library nec_rc_decoder.jal, NEC Remote Control decoder.
- Added library philips_rc_decoder.jal, Philips RC5/RC6 Remote Control decoder.
- Update of gps_neo_6m.jal. Works on interrupt basis. GPS location added.
Note: This results in a breaking change is you have used the previous
version.
- Added library dcf77_decoder.jal, decoder for the DCF77 signal.
- Added library hcsr04.jal, HC-SR04 ultrasonic distance sensor

filesystem:
-

compiler:
- Update of jalv2 compiler documentation, fixing typo and adding operator
precedence.
- Added new compiler, version jalv25r8, fixing compiler issues #28, #30

Re: [jallib] Jallib 1.9.0 Beta is available

2024-03-30 Thread Rob CJ

Hi Matt,

Thanks for adding the compiler.

Can you also add the latest i2c_hardware.jal and the last version of the 
changelog (both were updated yesterday just before your release).

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Matthew Schinkel 

Verzonden: zaterdag 30 maart 2024 17:04
Aan: jallib 
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Rob, I've added it to jallib-1.9.0beta.zip

The other files have it already.

Thanks,
Matt.

On Saturday, March 30, 2024 at 5:10:46 AM UTC-4 rob...@hotmail.com wrote:
Hi Matt,

I downloaded the zip file. Seems that the compiler is missing.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: zaterdag 30 maart 2024 08:52
Aan: jallib 
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Matt,

This version does not yet have the change i2c_hardware.jal version which I 
uploaded yesterday that solves the issue reportedby David.

Maybe I was too late and it missed the release.

Is it possible to add this to the final release?

Thanks.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Matthew Schinkel 

Verzonden: zaterdag 30 maart 2024 01:10
Aan: jallib 
Onderwerp: [jallib] Jallib 1.9.0 Beta is available

Hi Everyone,

Jallib 1.9.0 Beta is available. Please download and test this. There will be an 
official release after 2 weeks.

If any changes are needed please let me know.

http://www.justanotherlanguage.org/downloads
jallib full 
jallib_full-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib%20full%20jallib_full-1.9.0beta.zip>
jallib-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib-1.9.0beta.zip>
jallib_full_win_setup-1.9.0beta.exe<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib_full_win_setup-1.9.0beta.exe>

Changes since 1.8.0

device files:
 - Added 16f18026.jal, 16f18046.jal.
 - Added 16f18054.jal, 16f18055.jal, 16f18074.jal, 16f18075.jal.
 - Added 18f26q71.jal, 18f46q71.jal, 18f56q71.jal.
 - Added 16f17114.jal, 16f17115.jal, 16f17124.jal, 16f17125.jal, 16f17144.jal, 
16f17145.jal
 - Added 16f18114.jal, 16f18115.jal, 16f18124.jal, 16f18125.jal, 16f18144.jal, 
16f18145.jal
 - Added 16f17156.jal, 16f17176.jal
 - Added 16f17154.jal, 16f17155.jal, 16f17174.jal, 16f17175.jal
 - Added 16f18154.jal, 16f18155.jal, 16f18174.jal, 16f18175.jal
 - Added 16f18126.jal, 16f18146.jal.


externals:
 - Added library rda5807m.jal, single-chip broadcast FM radio tuner.
 - Update of rtc_3231.jal. Added functions for reading the set alarm times.
 - Added library nec_rc_decoder.jal, NEC Remote Control decoder.
 - Added library philips_rc_decoder.jal, Philips RC5/RC6 Remote Control decoder.
 - Update of gps_neo_6m.jal. Works on interrupt basis. GPS location added.
   Note: This results in a breaking change is you have used the previous 
version.
 - Added library dcf77_decoder.jal, decoder for the DCF77 signal.
 - Added library hcsr04.jal, HC-SR04 ultrasonic distance sensor

filesystem:
 -

compiler:
 - Update of jalv2 compiler documentation, fixing typo and adding operator
   precedence.
 - Added new compiler, version jalv25r8, fixing compiler issues #28, #30 and 
#31.

jal:
 -

networking:
 -

peripherals:
 - Update of adc.jal to support newer PICs (alias added for ADCON0_GONDONE).
 - Update of stopwatch.jal and stopwatch2.jal to support newer PICs
 - Update of i2c_hardware.jal supporting a timeout to prevent hangup.

projects:
 -

protocols:
 -

samples:
 - Added 16f18026_blink_intosc.jal, 16f18046_blink_intosc.jal.
 - Added 16f18054_blink_intosc.jal, 16f18055_blink_intosc.jal,
 16f18074_blink_intosc.jal, 16f18075_blink_intosc.jal.
 - Added 18f26q71_blink_hs.jal, 18f26q71_blink_intosc.jal,
 18f46q71_blink_hs.jal, 18f46q71_blink_intosc.jal,
 18f56q71_blink_hs.jal, 18f56q71_blink_intosc.jal.
 - Added 16f1825_rda5807m.jal library for single-chip broadcast FM radio tuner.
 - Update of 16f1825_rtc_ds3231.jal. Added reading the set alarm times.
 - Added 16f15325_adc.jal. Newer PIC to test the updated adc.jal library.
 - Added 16f15325_stopwatch.jal, 16f15325_stopwatch2.jal
 - Added 16f877a_nec_rc_decoder.jal, 16f1825_nec_rc_decoder.jal,
 16f18857_nec_rc_decoder.jal for NEC Remote Control decoder library.
 - Added 16f877a_philips_rc_decoder.jal, 16f1825_philips_rc_decoder.jal,
 16f18857_philips_rc_decoder.jal for Philips Remote Control decoder 
library.
 - Added 16f17114_blink_hs.jal, 16f17114_blink_intosc.jal
 16f17115_blink_hs.jal, 16f17115_blink_intosc.jal
 16f17124_blink_hs.jal, 16f17124_blink_intosc.jal
 16f17125_blink_hs.jal, 16f17125_blink_intosc.jal
 16f17144_blink_hs.jal, 16f17144_blink_intosc.jal
 16f17145_blink_hs.jal, 16f17145_blink_intosc.jal
 - Added 16f18114_blink_hs.jal, 16f1811

Re: [jallib] Jallib 1.9.0 Beta is available

2024-03-30 Thread Rob CJ

Hi Matt,

I downloaded the zip file. Seems that the compiler is missing.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: zaterdag 30 maart 2024 08:52
Aan: jallib 
Onderwerp: Re: [jallib] Jallib 1.9.0 Beta is available

Hi Matt,

This version does not yet have the change i2c_hardware.jal version which I 
uploaded yesterday that solves the issue reportedby David.

Maybe I was too late and it missed the release.

Is it possible to add this to the final release?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Matthew Schinkel 

Verzonden: zaterdag 30 maart 2024 01:10
Aan: jallib 
Onderwerp: [jallib] Jallib 1.9.0 Beta is available

Hi Everyone,

Jallib 1.9.0 Beta is available. Please download and test this. There will be an 
official release after 2 weeks.

If any changes are needed please let me know.

http://www.justanotherlanguage.org/downloads
jallib full 
jallib_full-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib%20full%20jallib_full-1.9.0beta.zip>
jallib-1.9.0beta.zip<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib-1.9.0beta.zip>
jallib_full_win_setup-1.9.0beta.exe<http://www.justanotherlanguage.org/sites/default/files/ftp_server/builds/beta/jallib_full_win_setup-1.9.0beta.exe>

Changes since 1.8.0

device files:
 - Added 16f18026.jal, 16f18046.jal.
 - Added 16f18054.jal, 16f18055.jal, 16f18074.jal, 16f18075.jal.
 - Added 18f26q71.jal, 18f46q71.jal, 18f56q71.jal.
 - Added 16f17114.jal, 16f17115.jal, 16f17124.jal, 16f17125.jal, 16f17144.jal, 
16f17145.jal
 - Added 16f18114.jal, 16f18115.jal, 16f18124.jal, 16f18125.jal, 16f18144.jal, 
16f18145.jal
 - Added 16f17156.jal, 16f17176.jal
 - Added 16f17154.jal, 16f17155.jal, 16f17174.jal, 16f17175.jal
 - Added 16f18154.jal, 16f18155.jal, 16f18174.jal, 16f18175.jal
 - Added 16f18126.jal, 16f18146.jal.


externals:
 - Added library rda5807m.jal, single-chip broadcast FM radio tuner.
 - Update of rtc_3231.jal. Added functions for reading the set alarm times.
 - Added library nec_rc_decoder.jal, NEC Remote Control decoder.
 - Added library philips_rc_decoder.jal, Philips RC5/RC6 Remote Control decoder.
 - Update of gps_neo_6m.jal. Works on interrupt basis. GPS location added.
   Note: This results in a breaking change is you have used the previous 
version.
 - Added library dcf77_decoder.jal, decoder for the DCF77 signal.
 - Added library hcsr04.jal, HC-SR04 ultrasonic distance sensor

filesystem:
 -

compiler:
 - Update of jalv2 compiler documentation, fixing typo and adding operator
   precedence.
 - Added new compiler, version jalv25r8, fixing compiler issues #28, #30 and 
#31.

jal:
 -

networking:
 -

peripherals:
 - Update of adc.jal to support newer PICs (alias added for ADCON0_GONDONE).
 - Update of stopwatch.jal and stopwatch2.jal to support newer PICs
 - Update of i2c_hardware.jal supporting a timeout to prevent hangup.

projects:
 -

protocols:
 -

samples:
 - Added 16f18026_blink_intosc.jal, 16f18046_blink_intosc.jal.
 - Added 16f18054_blink_intosc.jal, 16f18055_blink_intosc.jal,
 16f18074_blink_intosc.jal, 16f18075_blink_intosc.jal.
 - Added 18f26q71_blink_hs.jal, 18f26q71_blink_intosc.jal,
 18f46q71_blink_hs.jal, 18f46q71_blink_intosc.jal,
 18f56q71_blink_hs.jal, 18f56q71_blink_intosc.jal.
 - Added 16f1825_rda5807m.jal library for single-chip broadcast FM radio tuner.
 - Update of 16f1825_rtc_ds3231.jal. Added reading the set alarm times.
 - Added 16f15325_adc.jal. Newer PIC to test the updated adc.jal library.
 - Added 16f15325_stopwatch.jal, 16f15325_stopwatch2.jal
 - Added 16f877a_nec_rc_decoder.jal, 16f1825_nec_rc_decoder.jal,
 16f18857_nec_rc_decoder.jal for NEC Remote Control decoder library.
 - Added 16f877a_philips_rc_decoder.jal, 16f1825_philips_rc_decoder.jal,
 16f18857_philips_rc_decoder.jal for Philips Remote Control decoder 
library.
 - Added 16f17114_blink_hs.jal, 16f17114_blink_intosc.jal
 16f17115_blink_hs.jal, 16f17115_blink_intosc.jal
 16f17124_blink_hs.jal, 16f17124_blink_intosc.jal
 16f17125_blink_hs.jal, 16f17125_blink_intosc.jal
 16f17144_blink_hs.jal, 16f17144_blink_intosc.jal
 16f17145_blink_hs.jal, 16f17145_blink_intosc.jal
 - Added 16f18114_blink_hs.jal, 16f18114_blink_intosc.jal
 16f18115_blink_hs.jal, 16f18115_blink_intosc.jal
 16f18124_blink_hs.jal, 16f18124_blink_intosc.jal
 16f18125_blink_hs.jal, 16f18125_blink_intosc.jal
 16f18144_blink_hs.jal, 16f18144_blink_intosc.jal
 16f18145_blink_hs.jal, 16f18145_blink_intosc.jal
 - Update of 16f1825_gps_neo_6m.jal (see remark on breaking change of library).
   Added 16f1825_gps_neo_6m_ssd1306_clock.jal
 - Added 16f1825_dcf77_decoder_serial.jal, 16f1825_dcf77_decoder_ssd1306.jal
 - Added 16f1825_hcsr04_led.jal, 16f1825_hcsr04_serial.jal
 - Added 16f17156_blink_hs.jal, 16f1715

Re: [jallib] Jallib 1.9.0 Beta is available

2024-03-30 Thread Rob CJ

Hi Matt,

This version does not yet have the change i2c_hardware.jal version which I 
uploaded yesterday that solves the issue reportedby David.

Maybe I was too late and it missed the release.

Is it possible to add this to the final release?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Matthew Schinkel 

Verzonden: zaterdag 30 maart 2024 01:10
Aan: jallib 
Onderwerp: [jallib] Jallib 1.9.0 Beta is available

Hi Everyone,

Jallib 1.9.0 Beta is available. Please download and test this. There will be an 
official release after 2 weeks.

If any changes are needed please let me know.

http://www.justanotherlanguage.org/downloads
jallib full 
jallib_full-1.9.0beta.zip
jallib-1.9.0beta.zip
jallib_full_win_setup-1.9.0beta.exe

Changes since 1.8.0

device files:
 - Added 16f18026.jal, 16f18046.jal.
 - Added 16f18054.jal, 16f18055.jal, 16f18074.jal, 16f18075.jal.
 - Added 18f26q71.jal, 18f46q71.jal, 18f56q71.jal.
 - Added 16f17114.jal, 16f17115.jal, 16f17124.jal, 16f17125.jal, 16f17144.jal, 
16f17145.jal
 - Added 16f18114.jal, 16f18115.jal, 16f18124.jal, 16f18125.jal, 16f18144.jal, 
16f18145.jal
 - Added 16f17156.jal, 16f17176.jal
 - Added 16f17154.jal, 16f17155.jal, 16f17174.jal, 16f17175.jal
 - Added 16f18154.jal, 16f18155.jal, 16f18174.jal, 16f18175.jal
 - Added 16f18126.jal, 16f18146.jal.


externals:
 - Added library rda5807m.jal, single-chip broadcast FM radio tuner.
 - Update of rtc_3231.jal. Added functions for reading the set alarm times.
 - Added library nec_rc_decoder.jal, NEC Remote Control decoder.
 - Added library philips_rc_decoder.jal, Philips RC5/RC6 Remote Control decoder.
 - Update of gps_neo_6m.jal. Works on interrupt basis. GPS location added.
   Note: This results in a breaking change is you have used the previous 
version.
 - Added library dcf77_decoder.jal, decoder for the DCF77 signal.
 - Added library hcsr04.jal, HC-SR04 ultrasonic distance sensor

filesystem:
 -

compiler:
 - Update of jalv2 compiler documentation, fixing typo and adding operator
   precedence.
 - Added new compiler, version jalv25r8, fixing compiler issues #28, #30 and 
#31.

jal:
 -

networking:
 -

peripherals:
 - Update of adc.jal to support newer PICs (alias added for ADCON0_GONDONE).
 - Update of stopwatch.jal and stopwatch2.jal to support newer PICs
 - Update of i2c_hardware.jal supporting a timeout to prevent hangup.

projects:
 -

protocols:
 -

samples:
 - Added 16f18026_blink_intosc.jal, 16f18046_blink_intosc.jal.
 - Added 16f18054_blink_intosc.jal, 16f18055_blink_intosc.jal,
 16f18074_blink_intosc.jal, 16f18075_blink_intosc.jal.
 - Added 18f26q71_blink_hs.jal, 18f26q71_blink_intosc.jal,
 18f46q71_blink_hs.jal, 18f46q71_blink_intosc.jal,
 18f56q71_blink_hs.jal, 18f56q71_blink_intosc.jal.
 - Added 16f1825_rda5807m.jal library for single-chip broadcast FM radio tuner.
 - Update of 16f1825_rtc_ds3231.jal. Added reading the set alarm times.
 - Added 16f15325_adc.jal. Newer PIC to test the updated adc.jal library.
 - Added 16f15325_stopwatch.jal, 16f15325_stopwatch2.jal
 - Added 16f877a_nec_rc_decoder.jal, 16f1825_nec_rc_decoder.jal,
 16f18857_nec_rc_decoder.jal for NEC Remote Control decoder library.
 - Added 16f877a_philips_rc_decoder.jal, 16f1825_philips_rc_decoder.jal,
 16f18857_philips_rc_decoder.jal for Philips Remote Control decoder 
library.
 - Added 16f17114_blink_hs.jal, 16f17114_blink_intosc.jal
 16f17115_blink_hs.jal, 16f17115_blink_intosc.jal
 16f17124_blink_hs.jal, 16f17124_blink_intosc.jal
 16f17125_blink_hs.jal, 16f17125_blink_intosc.jal
 16f17144_blink_hs.jal, 16f17144_blink_intosc.jal
 16f17145_blink_hs.jal, 16f17145_blink_intosc.jal
 - Added 16f18114_blink_hs.jal, 16f18114_blink_intosc.jal
 16f18115_blink_hs.jal, 16f18115_blink_intosc.jal
 16f18124_blink_hs.jal, 16f18124_blink_intosc.jal
 16f18125_blink_hs.jal, 16f18125_blink_intosc.jal
 16f18144_blink_hs.jal, 16f18144_blink_intosc.jal
 16f18145_blink_hs.jal, 16f18145_blink_intosc.jal
 - Update of 16f1825_gps_neo_6m.jal (see remark on breaking change of library).
   Added 16f1825_gps_neo_6m_ssd1306_clock.jal
 - Added 16f1825_dcf77_decoder_serial.jal, 16f1825_dcf77_decoder_ssd1306.jal
 - Added 16f1825_hcsr04_led.jal, 16f1825_hcsr04_serial.jal
 - Added 16f17156_blink_hs.jal, 16f17156_blink_intosc.jal,
 16f17176_blink_hs.jal, 16f17176_blink_intosc.jal
 - Added 16f17154_blink_hs.jal, 16f17154_blink_intosc.jal,
 16f17155_blink_hs.jal, 16f17155_blink_intosc.jal,
 16f17174_blink_hs.jal, 16f17174_blink_intosc.jal,
 16f17175_blink_hs.jal, 16f17175_blink_intosc.jal
 - Added

Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

2024-03-29 Thread Rob CJ

Hi David,

I did not see it as blaming, you just reported an issue with a library.

Good that you found it. I already uploaded the change to GitHub so it will be
in the next release.

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: vrijdag 29 maart 2024 20:03
Aan: jallib
Onderwerp: Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi Rob,

Thank you for your reactivity!
I will check your solution this week-end, but it seems to be OK.

(Btw: I hope you did not think I was blaming anyone my first message may
sound harsh, but it was not my intent my apologies if you felt hurt)

Enjoy your week-end,

Kind regards,

David
Le vendredi 29 mars 2024 à 07:22:10 UTC+1, Rob CJ a écrit :
Hi David,

Found a workaround for the library without breaking anything. Should work and
will upload it this weekend.

Solution is as follows:

if defined(i2c_scl_direction) then
-- User defined i2c pins.
i2c_scl_direction = input
i2c_sda_direction = input
else
-- Default i2c pins from device file.
pin_SCL_direction = input
pin_SDA_direction = input
end if

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: donderdag 28 maart 2024 18:51
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi David,

I had never noticed it but you are right. I am not sure if PPS existed when
that library was created.

There is another thing and that is that library violates with the style guide
rules. The style guide states that the user should set the pin direction, not
the library (I did not know this when I started with JAL so some of my first
libraries are not compliant with the style guide too).

When the change that you mentioned would be implemented, sample files will
break and the main program should define the aliases. But when taking the style
guide into account then pin_SCL_direction and pin_SDA_direction should be
removed completely from the library since the main program would set the
correct pins to input and so your program would work since you define which
pins should be set to input.

So I could make the change and update all sample files accordingly but it will
result in compile errors for JAL users that use this updated library.

And since this library can be 'swapped' with the i2c_software libarary, that
one also needs the change.

So I am interested in the opinion of the JAL users about this modification. To
do or not to do, that is the question.

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens David VB

Verzonden: woensdag 27 maart 2024 22:57
Aan: jallib
Onderwerp: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi,

Just found something (Jallib 1.8 - Official release, no bees)

In the header of i2c_hardware, it is mentionned that:
-- Define i2c pins like:
-- alias i2c_sclis pin_c3 -- optional
-- alias i2c_scl_direction is pin_c3_direction
-- alias i2c_sdais pin_c4 -- optional
-- alias i2c_sda_direction is pin_c4_direction

Later, in the code, procedure i2c_initialize, we use, instead:
pin_SCL_direction = input
pin_SDA_direction = input

The problem is that, in the device file we have, only for SCL the following
definition
alias pin_SCL_direction is pin_C3_direction

In my application, I use the PPS to reassign SCL to RB6

So, I cannot re-assign pin_SCL_direction to pin_B6_direction.

No big deal: I copied a local version of the library in my project and changed
the i2c_initialize procedure with:
i2c_SCL_direction = input
i2c_SDA_direction = input

I do not know if this has already be changed for 1.9, but I suggest something
be made.

(Just my 2 cents)

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/f465c30e-73ec-4ada-81f2-f8b41db093c4n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/f465c30e-73ec-4ada-81f2-f8b41db093c4n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEBB7BED481F975B2E91E63B2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEBB7BED481F975B2E91E63B2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_sou

Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

2024-03-29 Thread Rob CJ

Hi David,

Found a workaround for the library without breaking anything. Should work and
will upload it this weekend.

Solution is as follows:

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: donderdag 28 maart 2024 18:51
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi David,

I had never noticed it but you are right. I am not sure if PPS existed when
that library was created.

So I could make the change and update all sample files accordingly but it will
result in compile errors for JAL users that use this updated library.

And since this library can be 'swapped' with the i2c_software libarary, that
one also needs the change.

So I am interested in the opinion of the JAL users about this modification. To
do or not to do, that is the question.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: woensdag 27 maart 2024 22:57
Aan: jallib
Onderwerp: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi,

Just found something (Jallib 1.8 - Official release, no bees)

Later, in the code, procedure i2c_initialize, we use, instead:
pin_SCL_direction = input
pin_SDA_direction = input

The problem is that, in the device file we have, only for SCL the following
definition
alias pin_SCL_direction is pin_C3_direction

In my application, I use the PPS to reassign SCL to RB6

So, I cannot re-assign pin_SCL_direction to pin_B6_direction.

No big deal: I copied a local version of the library in my project and changed
the i2c_initialize procedure with:
i2c_SCL_direction = input
i2c_SDA_direction = input

I do not know if this has already be changed for 1.9, but I suggest something
be made.

(Just my 2 cents)

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/f465c30e-73ec-4ada-81f2-f8b41db093c4n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/f465c30e-73ec-4ada-81f2-f8b41db093c4n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEBB7BED481F975B2E91E63B2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEBB7BED481F975B2E91E63B2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637C12ECEAA62B63C868C60E63A2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

2024-03-28 Thread Rob CJ

Hi David,

I had never noticed it but you are right. I am not sure if PPS existed when
that library was created.

So I could make the change and update all sample files accordingly but it will
result in compile errors for JAL users that use this updated library.

And since this library can be 'swapped' with the i2c_software libarary, that
one also needs the change.

So I am interested in the opinion of the JAL users about this modification. To
do or not to do, that is the question.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens David VB

Verzonden: woensdag 27 maart 2024 22:57
Aan: jallib
Onderwerp: [jallib] i2c_hardware.jal incompatible with pic16f1778 family ?

Hi,

Just found something (Jallib 1.8 - Official release, no bees)

Later, in the code, procedure i2c_initialize, we use, instead:
pin_SCL_direction = input
pin_SDA_direction = input

The problem is that, in the device file we have, only for SCL the following
definition
alias pin_SCL_direction is pin_C3_direction

In my application, I use the PPS to reassign SCL to RB6

So, I cannot re-assign pin_SCL_direction to pin_B6_direction.

No big deal: I copied a local version of the library in my project and changed
the i2c_initialize procedure with:
i2c_SCL_direction = input
i2c_SDA_direction = input

I do not know if this has already be changed for 1.9, but I suggest something
be made.

(Just my 2 cents)

Kind regards,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/f465c30e-73ec-4ada-81f2-f8b41db093c4n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EEBB7BED481F975B2E91E63B2%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Linux Issues

2024-03-10 Thread Rob CJ

Hi Glenn,

Thanks for the update. Good to hear that it is working.

Have you ever tried Visual Studio Code on Linux? If you download the JAL
extension you get very beautiful syntax highlighting and you just invoke the
compiler by pressing ctrl-B (build). In case of errors you just ctrl-left-click
(mouse) on the error and it jumps to the line where the error occured.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Glenn Walsh

Verzonden: zondag 10 maart 2024 14:09
Aan: jallib
Onderwerp: Re: [jallib] Linux Issues

Thanks again guys.

I folllowed Rob's advice and have the compiler working perfectly on Linux Mint
20.3 with Geany as IDE and PicKit2 as programmer.

A 16F877a happily blinking!

All the best

Glenn

On Saturday, March 2, 2024 at 5:19:53 PM UTC Glenn Walsh wrote:
Hi Rob and everyone!

Apologies for the delay getting back to this, I've been working all week.

That sounds like the problem. The laptop I have in my workshop has a completely
different file structure for Jal compared to this new one.

I will download the 'bee' package and try that this evening.

Thanks for your help, much appreciated.

Glenn

On Thursday, February 29, 2024 at 10:00:08 AM UTC Rob Hamerling wrote:

Hi Glen,

On 27-02-2024 21:23, Glenn Walsh wrote:
$ jallib-master/compiler/jalv2-x86-64 projects/test/16f877a_blink.jal -s
/jallib-master/include/

>From the 'include' in this statement I suspect you downloaded/cloned from
>Github. This would work if the compiler would support searching
>subdirectories. Unfortunately it doesn't. All files in the include
>subdirectories need be copied to a single directory (e.g. 'lib') or you must
>specify with '-s' one-by-one all directories of the libraries which you
>include in your program.

It might be easier to download and work with the latest 'bee' package from
justanotherlanguage.org

Regards, Rob.

--
Rob Hamerling, Vianen, NL

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/132fc6b6-d4c3-4a67-92ba-deaf3d237de7n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637EF2C7F336168638FF8FCE6252%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: Linux Issues

2024-02-28 Thread Rob CJ

Hi Andreas, Glenn,

I think Andreas is right. It seems that the compiler cannot find the device
file for your PIC (in the lib directory) and so adding that path with the -s
option should fix it.

Welcome back Glenn and good luck getting started again.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: woensdag 28 februari 2024 10:49
Aan: jallib
Onderwerp: [jallib] Re: Linux Issues

Hi Glenn,

I'm also on Linux for a similar long time. There is no problem with the
compiler on Linux I'm aware off.
1.) In your case the library file called '16f877a.jal' can not be found.
Usually it will be seen in subdirectory 'lib' (same hirarchy as folder
compiler). First check if it is there.
2.) I usually add a path with '-s ' when I call the comiler to tell where
to search for includes e.g.:
/home/schloegl/Programme/jalv25r6/compiler/jalv2-x86-64 -no-variable-reuse -s
/home/schloegl/Programme/jalv25r6/lib/ -s
/home/schloegl/Projekte/KWS/kwsremote.v5/sender/jalv2/ kwsremote5_send.jal

Adding the path will fix this issue. Hope you can fix it.
Andreas

On Wednesday, February 28, 2024 at 10:34:34 AM UTC+1 Glenn Walsh wrote:
Hi guys.

I have been using JAL on and off for about 15 years, but haven't used it
recently. I downloaded the latest version and unpacked on my Linux Mint laptop
and cannot get the compiler to work. I have used JAL under LInux before without
problems, so this has been really frustrating.

It must be something to do with permissions to access the library folder
because the compiler runs, but cannot access the device files so throws errors.
I have tried lots of changes to the permissions without success and reloaded
jallib-master again tonight.

$ jallib-master/compiler/jalv2-x86-64 projects/test/16f877a_blink.jal -s
/jallib-master/include/

gives me

jal jalv25r8 (compiled May 20 2023)
generating p-code
projects/test/16f877a_blink.jal:26: cannot open '16f877a.jal'
projects/test/16f877a_blink.jal:32: unknown pragma target: osc
projects/test/16f877a_blink.jal:32: "osc" not defined
projects/test/16f877a_blink.jal:32: unexpected token: osc
4 errors, 0 warnings

Any ideas?

Thanks in advance

Glenn

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/1b8e8f6c-925c-4f08-bed3-3a08c422aa1dn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637FB6ECD714B13274ED840E6582%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Format.jal warning

2024-01-01 Thread Rob CJ

Hi Patrick,

Thanks and thanks for the update. Good to hear that it is working.

Next to new device files, sample files and libraries the Jallib Tutorial Book
was also updated.

Have fun!

Kind regards,

Rob

Van: jallib@googlegroups.com namens
arduin...@gmail.com
Verzonden: maandag 1 januari 2024 15:03
Aan: jallib
Onderwerp: Re: [jallib] Format.jal warning

Hi Rob,

Happy new Year,

I have installed the jallib and it works perfect now !
since i had the "Bert Van Dam books", I need "switchover" my mindset ;-) i see
some other commands...
let me first do some examples from the jallib folder and let's build up again
the jal technoligy ;-)

keep you posted ,

Br,

Patrick

Op maandag 1 januari 2024 om 10:04:59 UTC+1 schreef Rob CJ:
Hi Patrick,

Good luck and welcome back to JAL.

And of course a Happy New Year to you and all JAL users!

Kind regards,

Rob

Van: jal...@googlegroups.com namens
arduin...@gmail.com
Verzonden: zondag 31 december 2023 17:25
Aan: jallib
Onderwerp: Re: [jallib] Format.jal warning

Hi Rob,

Thanks for your feedback, let me download the last jallib release first, and
will see what happen.

Br,

Patrick

Op zondag 31 december 2023 om 17:02:38 UTC+1 schreef Rob CJ:
Hoi Patrick,

Je kunt beter je vraag in het Engels stellen (you better ask your questions in
English).

Je geeft te weinig informatie om antwoord te geven op jouw vraag. We
ondersteunen niet de Bert libraries maar alleen die van Jallib. Misschien
handig om de laatste Jallib release te downloaden? De libraries van Bert hebben
allerhande toevoegingen waardoor zijn projecten makkelijker konden worden
opgezet maar ze wijken daarmee af van de originele libraries. Het kan dus zijn
als je de librarie van Jallib gebruikt dat je oude programma niet compileert
maar daar kom je alleen maar achter als je het probeert.

Met vriendelijke groet,

Rob

Van: jal...@googlegroups.com namens
arduin...@gmail.com
Verzonden: zondag 31 december 2023 16:36
Aan: jallib
Onderwerp: [jallib] Format.jal warning

Hi,

Heb de spulleties weer eens aangesloten en geinstalleerd, maar ik krijg nu
telkens den warning format.jal in beeld, graag een advies waarom ik dit
verkrijg, ik gebruik voor nu de _bert linraries en werkte eigenlijk altijd o.k

Gr,

Patrick

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/252c1ba8-cd93-49a3-bfdb-e0c1973b8614n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/252c1ba8-cd93-49a3-bfdb-e0c1973b8614n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/aabc5a70-22ff-4a47-b5d5-29e0fd26440an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/aabc5a70-22ff-4a47-b5d5-29e0fd26440an%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/1ba54883-fd4b-4f24-b43b-ecd1f1d31e65n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/1ba54883-fd4b-4f24-b43b-ecd1f1d31e65n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637667A849A17E2A5418817E662A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Format.jal warning

2024-01-01 Thread Rob CJ

Hi Patrick,

Good luck and welcome back to JAL.

And of course a Happy New Year to you and all JAL users!

Kind regards,

Rob

Van: jallib@googlegroups.com namens
arduin...@gmail.com
Verzonden: zondag 31 december 2023 17:25
Aan: jallib
Onderwerp: Re: [jallib] Format.jal warning

Hi Rob,

Thanks for your feedback, let me download the last jallib release first, and
will see what happen.

Br,

Patrick

Op zondag 31 december 2023 om 17:02:38 UTC+1 schreef Rob CJ:
Hoi Patrick,

Je kunt beter je vraag in het Engels stellen (you better ask your questions in
English).

Met vriendelijke groet,

Rob

Van: jal...@googlegroups.com namens
arduin...@gmail.com
Verzonden: zondag 31 december 2023 16:36
Aan: jallib
Onderwerp: [jallib] Format.jal warning

Hi,

Gr,

Patrick

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/252c1ba8-cd93-49a3-bfdb-e0c1973b8614n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/252c1ba8-cd93-49a3-bfdb-e0c1973b8614n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/aabc5a70-22ff-4a47-b5d5-29e0fd26440an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/aabc5a70-22ff-4a47-b5d5-29e0fd26440an%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637F2AC7AC4836517C42FBDE662A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Format.jal warning

2023-12-31 Thread Rob CJ

Hoi Patrick,

Je kunt beter je vraag in het Engels stellen (you better ask your questions in
English).

Met vriendelijke groet,

Rob

Van: jallib@googlegroups.com namens
arduin...@gmail.com
Verzonden: zondag 31 december 2023 16:36
Aan: jallib
Onderwerp: [jallib] Format.jal warning

Hi,

Gr,

Patrick

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/252c1ba8-cd93-49a3-bfdb-e0c1973b8614n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163719FD9B24D2886740B6D0E663A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Camera_Gimbal

2023-11-12 Thread Rob CJ

Hi Hans,

The reason that they re-assigned the programming pins - I think - is because 
the 'original' programming pins are also the USB pins. For debugging it is much 
more convenient that you can both use the programmer and the USB port at the 
same time.

For example if you use an 18f14k50 you are constantly disconnecting the USB 
port when programming the device. Very unhandy.

You asked if it worked for an NRF24L01 and that it the case .

It will work with any other PIC as long it has sufficient ROM and RAM.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: zondag 12 november 2023 11:14
Aan: jallib 
Onderwerp: Re: [jallib] Camera_Gimbal

Hello Rob,
I don't think it will work. I need two ad inputs and pin_A2 is Vusb. I also 
don't understand why the programming pins are C0 and C1 instead of A0 and A1.
regards
hans

Op zaterdag 11 november 2023 om 17:02:34 UTC+1 schreef Rob CJ:
Hi Hans,

I think you can. Is has sufficient ROM and RAM and a SPI interface.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: zaterdag 11 november 2023 15:49

Aan: jallib 
Onderwerp: Re: [jallib] Camera_Gimbal
Hello Rob,
I have killed one of my 16F15325, is it possible to use the16F1455 for this  
nrf24101 project? I have two of them.
Hans

Op vrijdag 10 november 2023 om 08:17:30 UTC+1 schreef Hans van Veldhuizen:
Hello Matthew,
More than 10 years ago I made Marieke with your lib, 8 servos and a very 
expensive wireless command set
. (see https://youtu.be/U3uuH1cK8Dk)
   I used a 16F1827 as transmitter and a 16F648a as receiver. I am now trying 
to use this old set for this, but as always my old programs no longer work in 
the changed JAL world. Time and again I experience that a sample only works in 
that sample environment and as soon as I want to use another PIC I have to 
complain to you. For me, electronics is still a tool to achieve something and 
not a goal in itself.
I'll see what I can do with your advice,
Thank you
Hans

Op vrijdag 10 november 2023 om 00:27:13 UTC+1 schreef Matthew Schinkel:
Check your clock frequency. If it is half what it is supposed to be your 
servo's would only get half pulses and half movement.

Not sure if it helps here but I suggest you try the slip library sometime for 
sending data packets. See samples 18f4620_slip_isr.jal or 18f4620_slip_poll.jal.

Matt.

On Thursday, November 9, 2023 at 11:15:43 AM UTC-5 hanz...@zeelandnet.nl wrote:
Hi Mathew,
I've used your lib dozens of times on all kinds of servos and they always 
worked perfectly These servos also work on the special tester that also 
works on your lib. I'm pretty sure there is a conflict with the PIC here. If I 
now go from 0 to max with the potentiometer, the servo only moves half a turn. 
I just don't know what part of the frequency range they get.
In any case, very nice that you responded.
regards
Hans

Op donderdag 9 november 2023 om 15:12:13 UTC+1 schreef Matthew Schinkel:
Hi Hans,

Servo's move depending on the PWM signal sent to them. It is possible your 
servo's are expecting a different signal depending on the manufacturer. Do you 
have other servo's to test?

Do your servo's work correctly an un-modified Jallib sample?

Do you have an oscilloscope you can test the signal with? The PWM signal should 
be between 0.5ms and 2.5ms.

Thanks,
Matt.

On Wednesday, November 8, 2023 at 7:12:07 AM UTC-5 hanz...@zeelandnet.nl wrote:
I have now adapted both circuits for WiFi. (So the transmitter has a WiFi 
master and the receiver a slave)
  The data received is identical to the transmitter
. However, the servos only move half a turn. Apparently the Servo-lib can't 
handle the pic. Or I have to set something else. The programs are attached 
again.

Op zaterdag 4 november 2023 om 10:50:22 UTC+1 schreef Hans van Veldhuizen:
Hi Rob,
It has to do with the pin A2. If i change it to C2 the both are working

Op zaterdag 4 november 2023 om 07:56:20 UTC+1 schreef Rob CJ:
Hi Hans,

The only difference that I see is the looptime.

 Instead of 1 second it is 1 ms but it depends on how fast the data is 
received. If that is too fast will that disturb the servo movement?

Kind regards,

Rob




Van: jal...@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: vrijdag 3 november 2023 22:13
Aan: jallib 
Onderwerp: Re: [jallib] Camera_Gimbal

Have changed with attached basic. Same result. Changed 325 for 324 same result

Op vrijdag 3 november 2023 om 21:27:23 UTC+1 schreef Hans van Veldhuizen:
Hi Rob,
If I add this before the original forever loop then just servo 2 moves. Changed 
servo's same result
forever loop

servo_move(60,1)
servo_move(60,2)
delay_1S(2)

servo_move(150,1)
servo_move(150,2)
delay_1S(2)

 end loop

Op vrijdag 3 november 2023 om 19:11:13 UTC+1 schreef Rob CJ:
Hi Hans,

I cannot see any errors. So the data is received correctly but the servo's do

Re: [jallib] Camera_Gimbal

2023-11-11 Thread Rob CJ

Hi Hans,

I think you can. Is has sufficient ROM and RAM and a SPI interface.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: zaterdag 11 november 2023 15:49
Aan: jallib 
Onderwerp: Re: [jallib] Camera_Gimbal

Hello Rob,
I have killed one of my 16F15325, is it possible to use the16F1455 for this  
nrf24101 project? I have two of them.
Hans

Op vrijdag 10 november 2023 om 08:17:30 UTC+1 schreef Hans van Veldhuizen:
Hello Matthew,
More than 10 years ago I made Marieke with your lib, 8 servos and a very 
expensive wireless command set
. (see https://youtu.be/U3uuH1cK8Dk)
   I used a 16F1827 as transmitter and a 16F648a as receiver. I am now trying 
to use this old set for this, but as always my old programs no longer work in 
the changed JAL world. Time and again I experience that a sample only works in 
that sample environment and as soon as I want to use another PIC I have to 
complain to you. For me, electronics is still a tool to achieve something and 
not a goal in itself.
I'll see what I can do with your advice,
Thank you
Hans

Op vrijdag 10 november 2023 om 00:27:13 UTC+1 schreef Matthew Schinkel:
Check your clock frequency. If it is half what it is supposed to be your 
servo's would only get half pulses and half movement.

Not sure if it helps here but I suggest you try the slip library sometime for 
sending data packets. See samples 18f4620_slip_isr.jal or 18f4620_slip_poll.jal.

Matt.

On Thursday, November 9, 2023 at 11:15:43 AM UTC-5 hanz...@zeelandnet.nl wrote:
Hi Mathew,
I've used your lib dozens of times on all kinds of servos and they always 
worked perfectly These servos also work on the special tester that also 
works on your lib. I'm pretty sure there is a conflict with the PIC here. If I 
now go from 0 to max with the potentiometer, the servo only moves half a turn. 
I just don't know what part of the frequency range they get.
In any case, very nice that you responded.
regards
Hans

Op donderdag 9 november 2023 om 15:12:13 UTC+1 schreef Matthew Schinkel:
Hi Hans,

Servo's move depending on the PWM signal sent to them. It is possible your 
servo's are expecting a different signal depending on the manufacturer. Do you 
have other servo's to test?

Do your servo's work correctly an un-modified Jallib sample?

Do you have an oscilloscope you can test the signal with? The PWM signal should 
be between 0.5ms and 2.5ms.

Thanks,
Matt.

On Wednesday, November 8, 2023 at 7:12:07 AM UTC-5 hanz...@zeelandnet.nl wrote:
I have now adapted both circuits for WiFi. (So the transmitter has a WiFi 
master and the receiver a slave)
  The data received is identical to the transmitter
. However, the servos only move half a turn. Apparently the Servo-lib can't 
handle the pic. Or I have to set something else. The programs are attached 
again.

Op zaterdag 4 november 2023 om 10:50:22 UTC+1 schreef Hans van Veldhuizen:
Hi Rob,
It has to do with the pin A2. If i change it to C2 the both are working

Op zaterdag 4 november 2023 om 07:56:20 UTC+1 schreef Rob CJ:
Hi Hans,

The only difference that I see is the looptime.

 Instead of 1 second it is 1 ms but it depends on how fast the data is 
received. If that is too fast will that disturb the servo movement?

Kind regards,

Rob




Van: jal...@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: vrijdag 3 november 2023 22:13
Aan: jallib 
Onderwerp: Re: [jallib] Camera_Gimbal

Have changed with attached basic. Same result. Changed 325 for 324 same result

Op vrijdag 3 november 2023 om 21:27:23 UTC+1 schreef Hans van Veldhuizen:
Hi Rob,
If I add this before the original forever loop then just servo 2 moves. Changed 
servo's same result
forever loop

servo_move(60,1)
servo_move(60,2)
delay_1S(2)

servo_move(150,1)
servo_move(150,2)
delay_1S(2)

 end loop

Op vrijdag 3 november 2023 om 19:11:13 UTC+1 schreef Rob CJ:
Hi Hans,

I cannot see any errors. So the data is received correctly but the servo's do 
not work?

Have you tried to get the servo's working without the receive routines? So just 
hard-code some values to see if the servo's are working?

Kind regards,

Rob




Van: jal...@googlegroups.com  namens Hans van 
Veldhuizen 
Verzonden: donderdag 2 november 2023 13:09
Aan: jallib 
Onderwerp: [jallib] Camera_Gimbal

Hello all,
My question again. I'm trying to make a two-way camera Gimbal. I have modified 
working programs. The transmitter now has two ADC inputs and the receiver must 
control two servos. The signals arrive correctly at the receiver in fits and 
starts. I can't get the servos to work. Attached are the two files.
Please respond again,
regards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web vi

Re: [jallib] Re: 18f4431 problems

2023-11-06 Thread Rob CJ

Hi Peter,

If you use the Pickit3 software when the pickit programmer is in mplax mode, it 
will mention that.

As far as I know it will not give the programming error that was described by 
Jos.

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of Zet Weeh 

Sent: Monday, November 6, 2023 10:08:42 AM
To: jallib 
Subject: [jallib] Re: 18f4431 problems

Hi Jos

I think it isn't a microprocessor problem.
Did you use a new PICKit3 or use it with MPlab?
Because you can't load a program and seeing the code of the error-message I 
think the PICKit3 has the firmware for MPlab
and you wanna use the stand-alone version.

Do this to load the stand-alone firmware:
1 Start the PICKit3
2 Open 'Tools' - Download PICKit Operating system'
3 Now 'Open PK 3 OS file'
4 Go to C:\Program files\Microchip|PICKit3
5 Click: 'PK30SVO25.hex'
6 Click 'Open'
7 Follow the screen
8 When PICKit3 is ready: close and restart

Succes
Peter

Op zondag 5 november 2023 om 15:36:01 UTC+1 schreef jos smans:
Hello, I have a problem by programming a pic 18f4431. When i make a verry 
simple  program blink a led ,jaledit accept the HEX program, but ,when i put it 
in pic, error occurs on my pickit3"Programming failed at Program Memory 
0x00"
I also I attempt a sample from jalib directory"18f4431_blink_HS.jal"with the 
same error.
Can i have a litlle help?
Thanks

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/382a37f3-4a4a-4692-964d-c16e1bebb25cn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637F3EA4A8D4F3D2DC0D03CE6AAA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] 18f4431 problems

2023-11-06 Thread Rob CJ

Hi Jos,

The PICKitplus software is software you need to purchase. If you use a newer 
PIC you need it. Your PIC is not so new so it should be possible to program it 
with the old PICKit software.

Even with PICKitplus I got sometimes the same error that you mentioned. I have 
two Chinese copies of the PICKit3 and one often gives this error and the other 
does not.

There are some options you can try that worked for me:

  1.  Put decoupling capacitors close to your PIC.
  2.  Use IPE from MPLABX. For some reason that also solved the problem (maybe 
they use another programming algorithm).  Note that you  need to switch your 
PICKit3 then to MPLABX mode.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens jos smans 

Verzonden: zondag 5 november 2023 19:37
Aan: jallib 
Onderwerp: Re: [jallib] 18f4431 problems

hi EvanVenn
I use  software Pickit 3V 3.10 , and also jaleditV2. If PickitPlus is  a newer 
and better program, were can i download it?
Jos.

Op zondag 5 november 2023 om 17:03:06 UTC+1 schreef Evan Venn:
Can you share what programming software you are using with your PK3?

I am the developer of PICKitPlus and we have tested this chip family.

Evan


From: jal...@googlegroups.com  on behalf of jos smans 

Sent: 05 November 2023 13:06
To: jallib 
Subject: [jallib] 18f4431 problems

Hello, I have a problem by programming a pic 18f4431. When i make a verry 
simple  program blink a led ,jaledit accept the HEX program, but ,when i put it 
in pic, error occurs on my pickit3"Programming failed at Program Memory 
0x00"
I also I attempt a sample from jalib directory"18f4431_blink_HS.jal"with the 
same error.
Can i have a litlle help?
Thanks
--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/77b05aac-91b9-4246-abd1-04bf83fffc56n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/0707b257-95ef-48e0-8d33-5898b03bbe3fn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637578BEFDCE079AE1E964EE6AAA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Camera_Gimbal

2023-11-04 Thread Rob CJ

Hi Hans,

The only difference that I see is the looptime.

Instead of 1 second it is 1 ms but it depends on how fast the data is
received. If that is too fast will that disturb the servo movement?

Kind regards,

Rob

Van: jallib@googlegroups.com namens Hans van
Veldhuizen
Verzonden: vrijdag 3 november 2023 22:13
Aan: jallib
Onderwerp: Re: [jallib] Camera_Gimbal

Have changed with attached basic. Same result. Changed 325 for 324 same result

Op vrijdag 3 november 2023 om 21:27:23 UTC+1 schreef Hans van Veldhuizen:
Hi Rob,
If I add this before the original forever loop then just servo 2 moves. Changed
servo's same result
forever loop

servo_move(60,1)
servo_move(60,2)
delay_1S(2)

servo_move(150,1)
servo_move(150,2)
delay_1S(2)

end loop

Op vrijdag 3 november 2023 om 19:11:13 UTC+1 schreef Rob CJ:
Hi Hans,

I cannot see any errors. So the data is received correctly but the servo's do
not work?

Have you tried to get the servo's working without the receive routines? So just
hard-code some values to see if the servo's are working?

Kind regards,

Rob

Van: jal...@googlegroups.com namens Hans van
Veldhuizen
Verzonden: donderdag 2 november 2023 13:09
Aan: jallib
Onderwerp: [jallib] Camera_Gimbal

Hello all,
My question again. I'm trying to make a two-way camera Gimbal. I have modified
working programs. The transmitter now has two ADC inputs and the receiver must
control two servos. The signals arrive correctly at the receiver in fits and
starts. I can't get the servos to work. Attached are the two files.
Please respond again,
regards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ff970ccd-ffb8-473f-991f-1441f768da3cn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/ff970ccd-ffb8-473f-991f-1441f768da3cn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/8093b573-4fb8-492a-ab0f-5db352424ffcn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/8093b573-4fb8-492a-ab0f-5db352424ffcn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16377D53B002C26F3577CD5DE6A4A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Camera_Gimbal

2023-11-03 Thread Rob CJ

Hi Hans,

I cannot see any errors. So the data is received correctly but the servo's do
not work?

Have you tried to get the servo's working without the receive routines? So just
hard-code some values to see if the servo's are working?

Kind regards,

Rob

Van: jallib@googlegroups.com namens Hans van
Veldhuizen
Verzonden: donderdag 2 november 2023 13:09
Aan: jallib
Onderwerp: [jallib] Camera_Gimbal

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/ff970ccd-ffb8-473f-991f-1441f768da3cn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16373D4053C23D6009DBD311E6A5A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: Re: [jallib] English (function) question

2023-09-30 Thread Rob CJ

Hi Oliver,

OK, so it will be mm (word) and mil (dword). Sample output looks like this, see 
below. This is not yet with a module since I did not yet get it. I used another 
PIC to simulate the module.

Distance measured is: 25 mm or 1010 mil.
Distance measured is: 2.5 cm or 1.0 inch.

Distance measured is: 34 mm or 1350 mil.
Distance measured is: 3.4 cm or 1.3 inch.

Distance measured is: 58 mm or 2290 mil.
Distance measured is: 5.8 cm or 2.2 inch.

Distance measured is: 81 mm or 3180 mil.
Distance measured is: 8.1 cm or 3.1 inch.

Distance measured is: 95 mm or 3750 mil.
Distance measured is: 9.5 cm or 3.7 inch.

Distance measured is: 103 mm or 4060 mil.
Distance measured is: 10.3 cm or 4.0 inch.

Kind regards,

Rob



Van: 'Oliver Seitz' via jallib 
Verzonden: zaterdag 30 september 2023 12:06
Aan: jallib@googlegroups.com 
Onderwerp: AW: Re: [jallib] English (function) question

Yes, otherwise you could use 1/16" or 1/32" which is near a mm, but it seems to 
be a bit of a strange unit for me.

byte*3 would suffice for the maximum range of 197000 mils, but I'm not sure if 
it's wise to use that... for 5000mm word is enough :-)

Greets,
Kiste

Gesendet von Yahoo Mail auf 
Android<https://mail.onelink.me/107872968?pid=nativeplacement=Global_Acquisition_YMktg_315_Internal_EmailSignature_sub1=Acquisition_sub2=Global_YMktg_sub3=_sub4=10604_sub5=EmailSignature__Static_>

Am Sa., Sept. 30, 2023 at 11:49 schrieb Rob CJ
:
Hi Kiste,

Thanks for the suggestion. Question about the mils. The modules resoluiton is 
limited (see screenshot below). What would 1/000 of an inch bring? Is it 
because of the standard terminology mils?

[cid:Td1Ro5YW9BV93yihGG4h]

So your suggestion would be the following?
function hcsr04_get_distance_mm() return dword is
function hcsr04_get_distance_mils) return dword is

Thanks.

Kind regards,

Rob


Van: 'Oliver Seitz' via jallib 
Verzonden: zaterdag 30 september 2023 11:21
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] English (function) question

Hi Rob,

I wanted to suggest to name the functions after the return data type. I never 
use floats, so if I would have a function called "fine", it would return a 
length in mm (metric) or mils (=1/1000 inch imperial)

Even if you would return a length in micrometers, a dword would suffice for a 
range of over 4 kilometers, still by a smaller overhead than using a float.

Greets,
Kiste

Am Samstag, 30. September 2023 um 11:11:37 MESZ hat Rob CJ  
Folgendes geschrieben:


Hi Vasile,

Thanks 

I just came up with another idea. Using a float value makes the library big in 
ROM size (it easily adds 600 byte of ROM or more) and I only need one decimal.

So I have another idea and that is return the distance in mm. In that case I 
only need a word as return value.

So now I have only two functions:
function hcsr04_get_distance_mili_meter() return word is
function hcsr04_get_distance_mili_inch() return word is

I only do not know if mili-inch is an English term. Would like to know that.

Or should I use tens_of_cm and tens_of_inch?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: zaterdag 30 september 2023 10:51
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] English (function) question

For a non-native English speaker like me, the function names are perfect!

On Sat, Sep 30, 2023 at 11:40 AM rob...@hotmail.com<mailto:rob...@hotmail.com> 
mailto:rob...@hotmail.com>> wrote:
Hi all.

I have a question for English native speakers. I am working on a library for 
the HC-SR04 ultrasonic ranging module.

I have functions that return the distance in cm and inch.

My question is the following. One of the functions returns a word so the 
distance is without a decimal, so 2 cm, 5 inch, etc. The other function returns 
a float so the distance is with a decimal, so 3.5 cm, 5.1 inch.

I am looking for a good name for these functions. I now have the following 
names but I am wondering if there is a better name for them:

function hcsr04_get_distance_cm_coarse() return word is
function hcsr04_get_distance_inch_coarse() return word is
function hcsr04_get_distance_cm_fine() return float is
function hcsr04_get_distance_inch_fine() return float is

So I am looking for  a better name for these functions. Any suggestions?

Thanks.

Kind regards,

Rob




--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/655e1cd1-adaf-49d9-b645-9ddcef475248n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/655e1cd1-adaf-49d9-b645-9ddcef475248n%40googlegroups.com?utm_medium=emai

Re: [jallib] English (function) question

2023-09-30 Thread Rob CJ

Hi Kiste,

Thanks for the suggestion. Question about the mils. The modules resoluiton is 
limited (see screenshot below). What would 1/000 of an inch bring? Is it 
because of the standard terminology mils?

[cid:66f6db3f-ea9a-4d96-a557-25ff3a94e37a]

So your suggestion would be the following?
function hcsr04_get_distance_mm() return dword is
function hcsr04_get_distance_mils) return dword is

Thanks.

Kind regards,

Rob


Van: 'Oliver Seitz' via jallib 
Verzonden: zaterdag 30 september 2023 11:21
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] English (function) question

Hi Rob,

I wanted to suggest to name the functions after the return data type. I never 
use floats, so if I would have a function called "fine", it would return a 
length in mm (metric) or mils (=1/1000 inch imperial)

Even if you would return a length in micrometers, a dword would suffice for a 
range of over 4 kilometers, still by a smaller overhead than using a float.

Greets,
Kiste

Am Samstag, 30. September 2023 um 11:11:37 MESZ hat Rob CJ  
Folgendes geschrieben:


Hi Vasile,

Thanks 

I just came up with another idea. Using a float value makes the library big in 
ROM size (it easily adds 600 byte of ROM or more) and I only need one decimal.

So I have another idea and that is return the distance in mm. In that case I 
only need a word as return value.

So now I have only two functions:
function hcsr04_get_distance_mili_meter() return word is
function hcsr04_get_distance_mili_inch() return word is

I only do not know if mili-inch is an English term. Would like to know that.

Or should I use tens_of_cm and tens_of_inch?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: zaterdag 30 september 2023 10:51
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] English (function) question

For a non-native English speaker like me, the function names are perfect!

On Sat, Sep 30, 2023 at 11:40 AM rob...@hotmail.com<mailto:rob...@hotmail.com> 
mailto:rob...@hotmail.com>> wrote:
Hi all.

I have a question for English native speakers. I am working on a library for 
the HC-SR04 ultrasonic ranging module.

I have functions that return the distance in cm and inch.

My question is the following. One of the functions returns a word so the 
distance is without a decimal, so 2 cm, 5 inch, etc. The other function returns 
a float so the distance is with a decimal, so 3.5 cm, 5.1 inch.

I am looking for a good name for these functions. I now have the following 
names but I am wondering if there is a better name for them:

function hcsr04_get_distance_cm_coarse() return word is
function hcsr04_get_distance_inch_coarse() return word is
function hcsr04_get_distance_cm_fine() return float is
function hcsr04_get_distance_inch_fine() return float is

So I am looking for  a better name for these functions. Any suggestions?

Thanks.

Kind regards,

Rob




--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/655e1cd1-adaf-49d9-b645-9ddcef475248n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/655e1cd1-adaf-49d9-b645-9ddcef475248n%40googlegroups.com?utm_medium=email_source=footer>.


--
Vasi

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CABsDq%3D86Jh5W8jHyb8VdQvvOJbrin%2BEzLTHKnkOsfzbLsR7-XQ%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CABsDq%3D86Jh5W8jHyb8VdQvvOJbrin%2BEzLTHKnkOsfzbLsR7-XQ%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB163796241C555E0C1AB38BDBE6C7A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB163796241C555E0C1AB38BDBE6C7A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@

Re: [jallib] English (function) question

2023-09-30 Thread Rob CJ

Hi Vasile,

Thanks 

I just came up with another idea. Using a float value makes the library big in 
ROM size (it easily adds 600 byte of ROM or more) and I only need one decimal.

So I have another idea and that is return the distance in mm. In that case I 
only need a word as return value.

So now I have only two functions:
function hcsr04_get_distance_mili_meter() return word is
function hcsr04_get_distance_mili_inch() return word is

I only do not know if mili-inch is an English term. Would like to know that.

Or should I use tens_of_cm and tens_of_inch?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vasi vasi 

Verzonden: zaterdag 30 september 2023 10:51
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] English (function) question

For a non-native English speaker like me, the function names are perfect!

On Sat, Sep 30, 2023 at 11:40 AM rob...@hotmail.com 
mailto:rob...@hotmail.com>> wrote:
Hi all.

I have a question for English native speakers. I am working on a library for 
the HC-SR04 ultrasonic ranging module.

I have functions that return the distance in cm and inch.

My question is the following. One of the functions returns a word so the 
distance is without a decimal, so 2 cm, 5 inch, etc. The other function returns 
a float so the distance is with a decimal, so 3.5 cm, 5.1 inch.

I am looking for a good name for these functions. I now have the following 
names but I am wondering if there is a better name for them:

function hcsr04_get_distance_cm_coarse() return word is
function hcsr04_get_distance_inch_coarse() return word is
function hcsr04_get_distance_cm_fine() return float is
function hcsr04_get_distance_inch_fine() return float is

So I am looking for  a better name for these functions. Any suggestions?

Thanks.

Kind regards,

Rob




--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/655e1cd1-adaf-49d9-b645-9ddcef475248n%40googlegroups.com.


--
Vasi

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/CABsDq%3D86Jh5W8jHyb8VdQvvOJbrin%2BEzLTHKnkOsfzbLsR7-XQ%40mail.gmail.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB163796241C555E0C1AB38BDBE6C7A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] DAIKIN REMOTE

2023-09-05 Thread Rob CJ

Hi Hans and others,

I had a look at why some messages are not posted. Apparently Google Group has
some - artifical? - intelligence to determine that a message is spam. If so it
puts the message on hold and it has to be approved (or rejected) by the admin.
In the past there used to be an option to post these messages anyway even when
Google Groups saw this as spam. This option is no longer available and I do not
know why.

I do not know what the intelligence is but I have seen that some message where
all one-liners. Maybe that is one of the reasons it 'thinks' that it is spam.

And to answer your question (I hope). Next to pic_data_eeprom.jal there is also
pic_data_hef.jal for PICs that have no EEPROM but High Endurance Flash (HEF).

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: maandag 4 september 2023 22:34
Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE

Hi Rob,
This program is the regular Eeprom use,.
i was looking for the one that uses the free programarea part
regards
Hans

Op maandag 4 september 2023 om 22:28:02 UTC+2 schreef hans:
Apparently I am a very difficult customer and my forum questions and comments
are increasingly simply deleted.

Op maandag 4 september 2023 om 15:09:15 UTC+2 schreef Rob CJ:
Hi all,

Yes, recently I purchased this logic analyzer. In combination with the software
it is really handy. I solved some IIC problems with it.

And for Hans. I ported the sample program to a PIC16F1827 and have sent it
directly to you.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Pinhead

Verzonden: maandag 4 september 2023 13:00
Aan: jal...@googlegroups.com

Onderwerp: Re: [jallib] DAIKIN REMOTE

Yes, indeed, but less portable.

Anyway, I always had driver trouble with those kind of devices and finally
ended up buying a Scanalogic one.

Le 04-09-23 à 12:19, vsurducan a écrit :
There is something cheaper for debugging data. It worth more than a Tektronix
MSO4104 with logic analyzer but without having decoding card
https://www.aliexpress.com/item/1005002399378513.html

On Mon 4 Sep 2023, 12:46 PM David VB, wrote:
Hi,

In case you didn't know, this cute little device enables you to retrieve the
codes in hex format of IR emitter

DSO TC-3

It's inexpensive (around 65 €) and receives much appraisal in the reviews I've
seen so far.
It is also a portable basic oscilloscope, signal generator and component tester

There are several videos on YouTube that you can search for, and it is
available from Elektor, Amazon, AliExpress etc

Hope this helps

Le dimanche 3 septembre 2023 à 19:23:27 UTC+2, Rob CJ a écrit :
Hi Hans,

Your plan is to send Daikin commands to your airconditioning and you need some
software to get the commands that you need?

I think the commands you need can be found on the internet (you will nog be the
first person who wants to do that).

If you have the commands from the internet, then the only thing remaining is
sending out the data according to the protocol, correct?

I found this by Googlw: https://github.com/blafois/Daikin-IR-Reverse or
https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/
[https://ci4.googleusercontent.com/proxy/BRqNF9wimtB3JgB2gRLqH6MeRXKaArMTywfOY--zNHK7tTpl9zz1MTA5qQ7O9zjhNIiLCb-Lan29LGQtxe3xL65xyDGMsCssywpNqaRU9i31Nv3h7StxQDc2u-eE157HpDhk9OmtuJ2VYC-QX3jBrKzN_2KfJik=s0-d-e1-ft#https://content.instructables.com/FKG/HT5J/HRTWKE84/FKGHT5JHRTWKE84.jpg?auto=webp=1=2100]<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control
Protocol<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control Protocol: Hi, this is my
first instructable, hope you like it. To get into electronics I chose a home
automation project: a system allowing me to control and program both air
conditioner units in my flat. In this instructable I show how I got to understa…
www.instructables.com<http://www.instructables.com>

So when you have the commands you can use the software you already created to
send the data out.

Is my assumption correct or is it something else you want to achieve?

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 16:05

Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE
Okay Rob.
After 4 days of struggling and a mess of results, I followed my wife's advice.
I'm going to start with the old graphics approach.
Make an audio recording, greatly enlarge and print it and then write down the
series of zeros and ones
. For example, I made my circuit earlier and last winter it switched the air
conditioners on and off according to the program as heating.
Remains with me the respect for the programs you all can make.
regards
Han

Re: [jallib] DAIKIN REMOTE

2023-09-04 Thread Rob CJ

Hi all,

Yes, recently I purchased this logic analyzer. In combination with the software
it is really handy. I solved some IIC problems with it.

And for Hans. I ported the sample program to a PIC16F1827 and have sent it
directly to you.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Pinhead

Verzonden: maandag 4 september 2023 13:00
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] DAIKIN REMOTE

Yes, indeed, but less portable.

Anyway, I always had driver trouble with those kind of devices and finally
ended up buying a Scanalogic one.

On Mon 4 Sep 2023, 12:46 PM David VB,
mailto:pinhead...@gmail.com>> wrote:
Hi,

In case you didn't know, this cute little device enables you to retrieve the
codes in hex format of IR emitter

DSO TC-3

It's inexpensive (around 65 €) and receives much appraisal in the reviews I've
seen so far.
It is also a portable basic oscilloscope, signal generator and component tester

There are several videos on YouTube that you can search for, and it is
available from Elektor, Amazon, AliExpress etc

Hope this helps

Le dimanche 3 septembre 2023 à 19:23:27 UTC+2, Rob CJ a écrit :
Hi Hans,

Your plan is to send Daikin commands to your airconditioning and you need some
software to get the commands that you need?

I think the commands you need can be found on the internet (you will nog be the
first person who wants to do that).

If you have the commands from the internet, then the only thing remaining is
sending out the data according to the protocol, correct?

I found this by Googlw: https://github.com/blafois/Daikin-IR-Reverse or
https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/
[https://content.instructables.com/FKG/HT5J/HRTWKE84/FKGHT5JHRTWKE84.jpg?auto=webp=1=2100]<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control
Protocol<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control Protocol: Hi, this is my
first instructable, hope you like it. To get into electronics I chose a home
automation project: a system allowing me to control and program both air
conditioner units in my flat. In this instructable I show how I got to understa…
www.instructables.com<http://www.instructables.com>

So when you have the commands you can use the software you already created to
send the data out.

Is my assumption correct or is it something else you want to achieve?

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 16:05

Op donderdag 31 augustus 2023 om 18:48:01 UTC+2 schreef Rob CJ:
Hi Hans,

What you could do is modify the NEC decoder library and change the bit times
and the number of bits. Since you know which bit time is 1 and which is 0 this
should be douable.

The NEC prototol also starts with a pulse more or less the same as the Daikin,
followed by bytes of data and a stop bit.

You find the info in the library. The protocol is as follows.

-- Specification of NEC IR protocol:
-- Logical '0': A 562.5 us pulse burst followed by a 562.5 us space,
-- with a total transmit time of 1.125 ms
-- Logical '1': A 562.5 us pulse burst followed by a 1.6875ms space,
-- with a total transmit time of 2.25 ms
-- *) Start with 9 ms leading pulse burst (16 times the pulse burst length used
--for a logical data bit) followed by a a 4.5 ms space.
-- *) 8-bit address for the receiving device or 16 bit for the extended protocol
-- *) 8-bit logical inverse of the address or high byte for the extended
protocol.
-- *) 8-bit command.
-- *) 8-bit logical inverse of the command.
-- *) Final 562.5 us pulse burst to signify the end of message transmission.
-- *) The four bytes of data bits are each sent least significant bit first.
-- *) After a command is tranmitted and the key on the remote control is still
--pressed only a repeat message is sent consisting of a start pulse of
--9 ms, followed by a 2.25 ms space.

Kind regards,

Rob

Re: [jallib] Pic_program_eeprom.jal

2023-09-04 Thread Rob CJ

Hi all,

Sorry for the Dutch. I thought that Hans e-mailed me directly.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: maandag 4 september 2023 08:04
Aan: jallib
Onderwerp: Re: [jallib] Pic_program_eeprom.jal

Hoi Hans,

Dat bestand heet nu pic_data_eeprom.jal.

Groetjes,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 19:29
Aan: jallib
Onderwerp: [jallib] Pic_program_eeprom.jal

Hi, In my last search I wanted to use this lib. I had to divert to Bert's old
base.
There is the lib Bit array but I needed bytes.
Was this lib recorded under a different name?
regards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/afa874aa-196f-4160-a8a4-7a2614f8a26fn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/afa874aa-196f-4160-a8a4-7a2614f8a26fn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163765F326256DC2940DE488E6E9A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB163765F326256DC2940DE488E6E9A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D79CB9EBE837F8E7FE8BE6E9A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Pic_program_eeprom.jal

2023-09-04 Thread Rob CJ

Hoi Hans,

Dat bestand heet nu pic_data_eeprom.jal.

Groetjes,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zondag 3 september 2023 19:29
Aan: jallib 
Onderwerp: [jallib] Pic_program_eeprom.jal

Hi, In my last search I wanted to use this lib. I had to divert to Bert's old 
base.
 There is the lib Bit array but I needed bytes.
Was this lib recorded under a different name?
regards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/afa874aa-196f-4160-a8a4-7a2614f8a26fn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB163765F326256DC2940DE488E6E9A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] DAIKIN REMOTE

2023-09-04 Thread Rob CJ

Hi Hans,

I am this week on holiday this week but woke up with an idea. I hacked the
rc_nec_decoder software that I made and changed it into a bit-timer.

I am not able to test this but it works as follows:

1. It starts when an infra red receiver, connected to the external interrupt
goes low (active). That is, a signal is received.
2. It measures all bursts (H) and pauses (L) of the remote control signal
until no signal is received for 65 ms (timer 1 overflow)
3. After the overflow of timer 1 it wil indicate that something is received.
All bits are stored in us in a large array of words.

The only thing you need to do is get it working for your PIC where you have to
initialize timer 1 to run at 1 MHz. This because it gives all times in us. If
you run it at another clock you have to recalculate what the bit times are.

As said, this compiles, it is not tested. Try it out. Sample file is attached.
Do not look too much at the code of the rc_timer.jal file since as said it is
just a hack. I may want to make is nice so it could be used as a library if
there is a need for something like this

The sample files prints 'H:' followed by the bit times in us. In this case 'H'
means that there was an infra red signal (receiver is active low).

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 19:51
Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE

Hello Rob,
I know these sources and used this info at the time. Unfortunately didn't work.
I then used my graphical trick and discovered minimal differences which
apparently are crucial and depend on the type of device and type of remote
control. The values I found my way worked perfectly and so did the unit I made.
But only to switch the heating on and off in time.
Because my sight is getting less and less, I was dreading working this way
again. Unfortunately, I didn't manage to get the series of zeros and ones right
on my screen.
regards
Hans

Op zondag 3 september 2023 om 19:23:27 UTC+2 schreef Rob CJ:
Hi Hans,

Your plan is to send Daikin commands to your airconditioning and you need some
software to get the commands that you need?

I think the commands you need can be found on the internet (you will nog be the
first person who wants to do that).

If you have the commands from the internet, then the only thing remaining is
sending out the data according to the protocol, correct?

So when you have the commands you can use the software you already created to
send the data out.

Is my assumption correct or is it something else you want to achieve?

Thanks.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 16:05

Op donderdag 31 augustus 2023 om 18:48:01 UTC+2 schreef Rob CJ:
Hi Hans,

What you could do is modify the NEC decoder library and change the bit times
and the number of bits. Since you know which bit time is 1 and which is 0 this
should be douable.

The NEC prototol also starts with a pulse more or less the same as the Daikin,
followed by bytes of data and a stop bit.

You find the info in the library. The protocol is as follows.

-- Specification of NEC IR protocol:
-- Logical '0': A 562.5 us pulse burst followed by a 562.5 us space,
-- with a total transmit time of 1.125 ms
-- Logical '1': A 56

Re: [jallib] DAIKIN REMOTE

2023-09-03 Thread Rob CJ

Hi Hans,

Your plan is to send Daikin commands to your airconditioning and you need some
software to get the commands that you need?

I think the commands you need can be found on the internet (you will nog be the
first person who wants to do that).

If you have the commands from the internet, then the only thing remaining is
sending out the data according to the protocol, correct?

I found this by Googlw: https://github.com/blafois/Daikin-IR-Reverse or
https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/
[https://content.instructables.com/FKG/HT5J/HRTWKE84/FKGHT5JHRTWKE84.jpg?auto=webp=1=2100]<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control
Protocol<https://www.instructables.com/Reverse-engineering-of-an-Air-Conditioning-control/>
Reverse Engineering Air Conditioner IR Remote Control Protocol: Hi, this is my
first instructable, hope you like it. To get into electronics I chose a home
automation project: a system allowing me to control and program both air
conditioner units in my flat. In this instructable I show how I got to
understa...
www.instructables.com

So when you have the commands you can use the software you already created to
send the data out.

Is my assumption correct or is it something else you want to achieve?

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zondag 3 september 2023 16:05
Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE

Okay Rob.
After 4 days of struggling and a mess of results, I followed my wife's advice.
I'm going to start with the old graphics approach.
Make an audio recording, greatly enlarge and print it and then write down the
series of zeros and ones
. For example, I made my circuit earlier and last winter it switched the air
conditioners on and off according to the program as heating.
Remains with me the respect for the programs you all can make.
regards
Hans

Op donderdag 31 augustus 2023 om 18:48:01 UTC+2 schreef Rob CJ:
Hi Hans,

What you could do is modify the NEC decoder library and change the bit times
and the number of bits. Since you know which bit time is 1 and which is 0 this
should be douable.

The NEC prototol also starts with a pulse more or less the same as the Daikin,
followed by bytes of data and a stop bit.

You find the info in the library. The protocol is as follows.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: donderdag 31 augustus 2023 12:00

Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE
The remote control read on a KY-022 is HIGH at rest.
1. 350 us low
2. 120 us high
3. Then always the 19 bytes burst = 450 us, 0 =350 and 1 =1190
4. Followed by 19 bytes of which the first 4 are always equal 17,218,39,0

I am now reading this out in an audio program and then puzzle the matter out.
Is this a way for someone who handles pics ?? / Yes, for a klutz like me it is.
Unless some Jal_scholar can help me with a program that just reads that array
of values.

Op dinsdag 29 augustus 2023 om 19:44:02 UTC+2 schreef hans:
This info is not correct for my units but helped me to understand.
https://github.com/blafois/Daikin-IR-Reverse

Op dinsdag 29 augustus 2023 om 19:31:49 UTC+2 schreef hans:
Hi Rob
Thank you.
NEC is therefore:
-- Logical '0': A 562.5 us pulse burst followed by a 562.5 us space,
-- with a total transmit time of 1,125 ms
-- Logical '1': A 562.5 us pulse burst followed by a 1.6875ms space,
-- with a total transmit time of 2.25 ms

My system currently works with:
-- Logical '0': usec_delay(450) pulse burst followed by a usec_delay(350) space,
-- with a total transmit time of 800
-- Logical '1': usec_delay(450pulse burst followed by a usec_delay(1190) space,
-- with a total transmit time of 1640

Some publications mention 500 followed by 440 or 1300 uS
If I am able to read t

Re: [jallib] DAIKIN REMOTE

2023-08-31 Thread Rob CJ

Hi Hans,

What you could do is modify the NEC decoder library and change the bit times 
and the number of bits. Since you know which bit time is 1 and which is 0 this 
should be douable.

The NEC prototol also starts with a pulse more or less the same as the Daikin, 
followed by bytes of data and a stop bit.

You find the info in the library. The protocol is as follows.

-- Specification of NEC IR protocol:
-- Logical '0': A 562.5 us pulse burst followed by a 562.5 us space,
--  with a total transmit time of 1.125 ms
-- Logical '1': A 562.5 us pulse burst followed by a 1.6875ms space,
--  with a total transmit time of 2.25 ms
-- *) Start with 9 ms leading pulse burst (16 times the pulse burst length used
--for a logical data bit) followed by a a 4.5 ms space.
-- *) 8-bit address for the receiving device or 16 bit for the extended protocol
-- *) 8-bit logical inverse of the address or high byte for the extended 
protocol.
-- *) 8-bit command.
-- *) 8-bit logical inverse of the command.
-- *) Final 562.5 us pulse burst to signify the end of message transmission.
-- *) The four bytes of data bits are each sent least significant bit first.
-- *) After a command is tranmitted and the key on the remote control is still
--pressed only a repeat message is sent consisting of a start pulse of
--9 ms, followed by a 2.25 ms space.

Kind regards,

Rob



Van: jallib@googlegroups.com  namens hans 

Verzonden: donderdag 31 augustus 2023 12:00
Aan: jallib 
Onderwerp: Re: [jallib] DAIKIN REMOTE

The remote control read on a KY-022 is HIGH at rest.
1. 350 us low
2. 120 us high
3. Then always the 19 bytes burst = 450 us, 0 =350 and 1 =1190
4. Followed by 19 bytes of which the first 4 are always equal 17,218,39,0

I am now reading this out in an audio program and then puzzle the matter out.
Is this a way for someone who handles pics ?? / Yes, for a klutz like me it is. 
Unless some Jal_scholar can help me with a program that just reads that array 
of values.


Op dinsdag 29 augustus 2023 om 19:44:02 UTC+2 schreef hans:
This info is not correct for my units but helped me to understand. 
https://github.com/blafois/Daikin-IR-Reverse

Op dinsdag 29 augustus 2023 om 19:31:49 UTC+2 schreef hans:
Hi Rob
Thank you.
NEC is therefore:
-- Logical '0': A 562.5 us pulse burst followed by a 562.5 us space,
-- with a total transmit time of 1,125 ms
-- Logical '1': A 562.5 us pulse burst followed by a 1.6875ms space,
-- with a total transmit time of 2.25 ms

My system currently works with:
-- Logical '0': usec_delay(450) pulse burst followed by a usec_delay(350) space,
-- with a total transmit time of 800
-- Logical '1': usec_delay(450pulse burst followed by a usec_delay(1190) space,
-- with a total transmit time of 1640

Some publications mention 500 followed by 440 or 1300 uS
If I am able to read the different ranges of the remote control, I think I can 
get further.
regards
Hans

Op dinsdag 29 augustus 2023 om 18:43:48 UTC+2 schreef Rob CJ:
Hi Hans,

What I see on Internet about the Daikin protocol is that the message length is 
not always the same and that is not the same as the NEC protocol which has a 
fixed length.

But I may be wrong. I attached the two files to this discussion.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: dinsdag 29 augustus 2023 16:44
Aan: jallib 
Onderwerp: Re: [jallib] DAIKIN REMOTE

I think NEC is the same system and am therefore looking for the libs for this. 
I can't handle the Gitthub . Where can I find the libs
16F877a_nec_rc_decode.jalr and the nec_rc_decoder.jal

Op maandag 28 augustus 2023 om 20:46:19 UTC+2 schreef hans:
Hello Rob,
Searching the internet is my basic approach. What I found doesn't work for me.
I now know what a bit looks like and I know its structure.
  I would now like to have a program that can read those bits concatenated into 
bytes I have no idea how I would go about doing that.
regards
Hans

Op maandag 28 augustus 2023 om 19:04:20 UTC+2 schreef Rob CJ:
Hi Hans,

Maybe look on the internet if people already figured this out. I saw there is 
some info there but not sure if that is the info you are looking for.

BTW. A tip for your program. You are declaring an array with constant values as 
var. You can save RAM memory by defining the array as const. You have way more 
const memory than var memory.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens hans 

Verzonden: maandag 28 augustus 2023 13:33
Aan: jallib 
Onderwerp: [jallib] DAIKIN REMOTE

Daikin air conditioner remote control.
I have two daikins that are operated with infrared. After hours of puzzling, 
I've come to the point where I can turn them both on and off in the heating 
position. I would also like to know the other functions, but I dread all that 
work.
I read the remote control with a scope and then figure out the values.
Is there anyone who has

Re: [jallib] DAIKIN REMOTE

2023-08-29 Thread Rob CJ

Hi Hans,

What I see on Internet about the Daikin protocol is that the message length is
not always the same and that is not the same as the NEC protocol which has a
fixed length.

But I may be wrong. I attached the two files to this discussion.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: dinsdag 29 augustus 2023 16:44
Aan: jallib
Onderwerp: Re: [jallib] DAIKIN REMOTE

I think NEC is the same system and am therefore looking for the libs for this.
I can't handle the Gitthub . Where can I find the libs
16F877a_nec_rc_decode.jalr and the nec_rc_decoder.jal

Op maandag 28 augustus 2023 om 20:46:19 UTC+2 schreef hans:
Hello Rob,
Searching the internet is my basic approach. What I found doesn't work for me.
I now know what a bit looks like and I know its structure.
I would now like to have a program that can read those bits concatenated into
bytes I have no idea how I would go about doing that.
regards
Hans

Op maandag 28 augustus 2023 om 19:04:20 UTC+2 schreef Rob CJ:
Hi Hans,

Maybe look on the internet if people already figured this out. I saw there is
some info there but not sure if that is the info you are looking for.

BTW. A tip for your program. You are declaring an array with constant values as
var. You can save RAM memory by defining the array as const. You have way more
const memory than var memory.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: maandag 28 augustus 2023 13:33
Aan: jallib
Onderwerp: [jallib] DAIKIN REMOTE

Daikin air conditioner remote control.
I have two daikins that are operated with infrared. After hours of puzzling,
I've come to the point where I can turn them both on and off in the heating
position. I would also like to know the other functions, but I dread all that
work.
I read the remote control with a scope and then figure out the values.
Is there anyone who has already done this?
Otherwise I would like to have a system to read the signals from the remote
control.
regards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/2c2df2f5-f93b-403d-a414-a52cf4504571n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/2c2df2f5-f93b-403d-a414-a52cf4504571n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/7dda8812-a46c-49fe-b8f9-a3e42b86ad1an%40googlegroups.com<https://groups.google.com/d/msgid/jallib/7dda8812-a46c-49fe-b8f9-a3e42b86ad1an%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163703F64767C4CDC4C5185BE6E7A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

16f877a_nec_rc_decoder.jal
Description: 16f877a_nec_rc_decoder.jal

nec_rc_decoder.jal
Description: nec_rc_decoder.jal

Re: [jallib] Re: Releasing untested device files

2023-08-28 Thread Rob CJ

Hi Evan,

An update about his issue after e-mailing with Microchip and a lot of waiting.
I made a mistake in ordering free samples.

I selected a PIC for which there where no free samples available. Normally you
get this special icon that you need to click to order free samples. If the icon
is not there and you click on the PIC you want then you get a page with paid
samples.

So you have to check if the free sample icon is there. I ordered some PICs but
unfortunately there where no free samples in the package I wanted so I ordered
them in another package.

So it is still possible to test device files before releasing them .

Kind regards,

Rob

Van: 'evan@googlemail.com' via jallib
Verzonden: maandag 26 juni 2023 10:27
Aan: jallib
Onderwerp: [jallib] Re: Releasing untested device files

The strategy is a good one.

Microchip have improved the quality of the device descriptions with MPLAB-X.
If the JALLIB process recreates the device file upon each MPLAB-X / DFP release
(as Microchip do correct) then you have a robust process.

>From a GCBASIC point of view - we will do the same.

Evan

On Monday, 26 June 2023 at 08:35:49 UTC+1 rob...@hotmail.com wrote:
Hi all,

When new PICs are released, I create new device files using the data provided
in MPLABX.

Normally I do a test of a device file by running the blink-a-led sample
program. For that I order free samples from Microchip.

Microchip seems to change this and now you must have a business (and a VAT
number) in order to get samples and it seems that it is no longer free. Since I
have no business and did not plan to buy all available PIC microcontroller I
plan to release all new device files untested.

In the years that I have taken over the device file creation from Rob Hamerling
I did not found any issues lately with device files since Microchip is doing a
better job than in the past.

The advantage of this is that I can release a device file as soon as it is
available in MPLABX and you do not need to wait for me to get a sample to test
it.

Let me know what you think.

Thanks

Kind regards,

Rob

--
You received this message because you are subscribed to a topic in the Google
Groups "jallib" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jallib/XrU5caeqIxc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/136efd04-8bd0-4759-b5ed-361d785d4f4bn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637F9D2E253D96567DB7EA6E6E0A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] DAIKIN REMOTE

2023-08-28 Thread Rob CJ

Hi Hans,

Maybe look on the internet if people already figured this out. I saw there is 
some info there but not sure if that is the info you are looking for.

BTW. A tip for your program. You are declaring an array with constant values as 
var. You can save RAM memory by defining the array as const. You have way more 
const memory than var memory.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: maandag 28 augustus 2023 13:33
Aan: jallib 
Onderwerp: [jallib] DAIKIN REMOTE

Daikin air conditioner remote control.
I have two daikins that are operated with infrared. After hours of puzzling, 
I've come to the point where I can turn them both on and off in the heating 
position. I would also like to know the other functions, but I dread all that 
work.
I read the remote control with a scope and then figure out the values.
Is there anyone who has already done this?
Otherwise I would like to have a system to read the signals from the remote 
control.
regards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2c2df2f5-f93b-403d-a414-a52cf4504571n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB163731C14BF2857E2B4989F4E6E0A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] IF statement fails

2023-08-20 Thread Rob CJ

Hi Andreas,

I am using the Windows version. I compiled the same program under Linux and 
used the hexfile to program the PIC. The result is the same. I also compared 
the asm files and they are also the same.

Then I did a test by forcing the Z flag to be TRUE or FALSE before the first 
function but it made no difference, it all worked OK. So my first analysis of 
the assembly code was not correct. I am using the latest version of the JAL 
compiler (v25r8) but for Linux I compiled it for both v25r7 as well as v25r8 
but that does not make any difference for this issue.

I tested it all on a PIC16F18857.

The only way to find the root cause  - that I can think of - is if you can 
reduce the code to where the problem occurs and then send it to me so that I 
can reproduce it.

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: zondag 20 augustus 2023 11:20
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hello Rob,

thanks for trying this. Your test program is correct. This is (first test only) 
 how it fails in my case.
I'm running the LINUX compiler. What is yours? Don't know if this could be a 
reason for.
If you think it makes sense I could try to compile my program under Windows, 
too to see if there is any differnce.

Beside that I think I need to simplyfy my program to hopefully be able to still 
reproduce it, but simple enough to give you the code.
If so what PIC sould I use? Is there a chance to use a simulator to run the 
code and print the output via serial interface? That we are hardware 
independend and could ompare our results more easyly.

Best Regards,
Andreas

On Sunday, August 20, 2023 at 10:49:11 AM UTC+2 Rob CJ wrote:
Hi Andreas,

I made this test program to print messages via the serial port:

var byte dummy = 0
var byte i,j,k

function test1() return byte is
return 0
end function
i=test1()
if i>0 & i<13 then
  -- goes here but is wrong
  print_string(serial, "1: It should NOT come here! ")
  dummy = dummy + 1
else
   print_string(serial, "1: This is OK. ")
 dummy = dummy + 2
end if
print_crlf(serial)

function test2() return byte is
return 0
end function
-- but this code works:
j=test2()
if j<13 & j>0 then
   dummy = dummy + 3
  print_string(serial, "2: It should NOT come here! ")

else
   -- goes here and OK
 dummy = dummy + 4
   print_string(serial, "2: This is OK. ")

end if
print_crlf(serial)

-- if you remove the function, it works, too:
k=0
if k>0 & k<13 then
   dummy = dummy + 5
  print_string(serial, "3: It should NOT come here! ")
else
   -- goes here and OK
 dummy = dummy + 6
   print_string(serial, "3: This is OK. ")
end if
print_crlf(serial)

The output on the terminal is as follows:
1: This is OK.
2: This is OK.
3: This is OK.

So it does not happen in my case. Can you explain this?

Thanks.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 18 augustus 2023 22:02

Aan: jal...@googlegroups.com 
Onderwerp: Re: [jallib] IF statement fails
Hi Andreas, Vasile,

The reason I think it is an optimization issue is because I had a look at the 
assembly code when the code reduce option is switched off.

The original code that went wrong was this (where the Z flag is not affected):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

With the code reduce disabled the code is as follows (where the Z flag is 
affected, because of the subwf instruction):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movlw0
   subwfv_i,w
   bcf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

As said I will test both options on a PIC so see if this indeed solves the 
problem. If so, I need to have a look at the optimization routine that does 
this.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens vsurducan 

Verzonden: vrijdag 18 augustus 2023 19:12
Aan: jal...@googlegroups.com 
Onderwerp: Re: [jallib] IF statement fails

:) good idea, no effect...
Forcing the operation order does not change anything?

If (i<13) & (i>0) then

If not, then only some workaround on the if, separe it in two sentences, that 
usually works.


On Fri 18 Aug 2023, 6:12 PM 'off...@schloegl-software.at' via jallib, 
 wrote:
I remove d "-no-variable-reuse" from the compiler call to see if there is a 
different:
No it is not, but good idea!

Best Regards,
An

Re: [jallib] IF statement fails

2023-08-20 Thread Rob CJ

Hi Andreas,

I made this test program to print messages via the serial port:

var byte dummy = 0
var byte i,j,k

function test1() return byte is
return 0
end function
i=test1()
if i>0 & i<13 then
  -- goes here but is wrong
  print_string(serial, "1: It should NOT come here! ")
  dummy = dummy + 1
else
   print_string(serial, "1: This is OK. ")
 dummy = dummy + 2
end if
print_crlf(serial)

function test2() return byte is
return 0
end function
-- but this code works:
j=test2()
if j<13 & j>0 then
   dummy = dummy + 3
  print_string(serial, "2: It should NOT come here! ")

else
   -- goes here and OK
 dummy = dummy + 4
   print_string(serial, "2: This is OK. ")

end if
print_crlf(serial)

-- if you remove the function, it works, too:
k=0
if k>0 & k<13 then
   dummy = dummy + 5
  print_string(serial, "3: It should NOT come here! ")
else
   -- goes here and OK
 dummy = dummy + 6
   print_string(serial, "3: This is OK. ")
end if
print_crlf(serial)

The output on the terminal is as follows:
1: This is OK.
2: This is OK.
3: This is OK.

So it does not happen in my case. Can you explain this?

Thanks.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: vrijdag 18 augustus 2023 22:02
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] IF statement fails

Hi Andreas, Vasile,

The reason I think it is an optimization issue is because I had a look at the 
assembly code when the code reduce option is switched off.

The original code that went wrong was this (where the Z flag is not affected):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

With the code reduce disabled the code is as follows (where the Z flag is 
affected, because of the subwf instruction):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movlw0
   subwfv_i,w
   bcf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

As said I will test both options on a PIC so see if this indeed solves the 
problem. If so, I need to have a look at the optimization routine that does 
this.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vsurducan 

Verzonden: vrijdag 18 augustus 2023 19:12
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] IF statement fails

:) good idea, no effect...
Forcing the operation order does not change anything?

If (i<13) & (i>0) then

If not, then only some workaround on the if, separe it in two sentences, that 
usually works.


On Fri 18 Aug 2023, 6:12 PM 
'off...@schloegl-software.at<mailto:off...@schloegl-software.at>' via jallib, 
mailto:jallib@googlegroups.com>> wrote:
I remove d "-no-variable-reuse" from the compiler call to see if there is a 
different:
No it is not, but good idea!

Best Regards,
Andreas

On Friday, August 18, 2023 at 1:45:42 PM UTC+2 vsurducan wrote:
Hi Rob, I think it's about disabling reusing variable space and not about 
expression reduction.

On Fri 18 Aug 2023, 9:48 AM Rob CJ,  wrote:
Hi Andreas

Strange, I will do some testing this weekend.

Thanks for the update.

Met vriendelijke groet,
Rob Jansen

From: 'off...@schloegl-software.at' via jallib 
Sent: Friday, August 18, 2023 8:33:06 AM
To: jallib 
Subject: Re: [jallib] IF statement fails

Hi Rob,

I tried that. As a result the code size increased (+200 byte), but the program 
doesn't work any more, the output on my display stopped working, so it's hard 
to further debug this.
So it's not clear if this helps or not because then other problems come into.

Andreas

On Thursday, August 17, 2023 at 10:29:51 PM UTC+2 Rob CJ wrote:
Hi Andreas,

It might be a optimization issues.

Can you add the following to your program and test if the problem is gone?

  pragma opt expr_reduce no

It will disable code optimization.

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:42

Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails
Hi Rob,
thanks that you are digging into this problem and maybe found the issue already.
I'm a heavy Jal User I would call myself, but this is the first issue I found 
over the last years :-)

On Thursday, August 17, 2023 at 9:31:13 PM UTC+2 Rob CJ wrote:
Hi Andreas,

I had a quick look at the generated assemble code for a PIC16.

In your first code example the code is (I changed 3 times i into i, j and k

Re: [jallib] IF statement fails

2023-08-18 Thread Rob CJ

Hi Andreas, Vasile,

The reason I think it is an optimization issue is because I had a look at the 
assembly code when the code reduce option is switched off.

The original code that went wrong was this (where the Z flag is not affected):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

With the code reduce disabled the code is as follows (where the Z flag is 
affected, because of the subwf instruction):
;   14 i=test1()
   movlw0
   movwfv_i
;   15 if i>0 & i<13 then
   movlw0
   subwfv_i,w
   bcf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

As said I will test both options on a PIC so see if this indeed solves the 
problem. If so, I need to have a look at the optimization routine that does 
this.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vsurducan 

Verzonden: vrijdag 18 augustus 2023 19:12
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] IF statement fails

:) good idea, no effect...
Forcing the operation order does not change anything?

If (i<13) & (i>0) then

If not, then only some workaround on the if, separe it in two sentences, that 
usually works.


On Fri 18 Aug 2023, 6:12 PM 
'off...@schloegl-software.at<mailto:off...@schloegl-software.at>' via jallib, 
mailto:jallib@googlegroups.com>> wrote:
I remove d "-no-variable-reuse" from the compiler call to see if there is a 
different:
No it is not, but good idea!

Best Regards,
Andreas

On Friday, August 18, 2023 at 1:45:42 PM UTC+2 vsurducan wrote:
Hi Rob, I think it's about disabling reusing variable space and not about 
expression reduction.

On Fri 18 Aug 2023, 9:48 AM Rob CJ,  wrote:
Hi Andreas

Strange, I will do some testing this weekend.

Thanks for the update.

Met vriendelijke groet,
Rob Jansen

From: 'off...@schloegl-software.at' via jallib 
Sent: Friday, August 18, 2023 8:33:06 AM
To: jallib 
Subject: Re: [jallib] IF statement fails

Hi Rob,

I tried that. As a result the code size increased (+200 byte), but the program 
doesn't work any more, the output on my display stopped working, so it's hard 
to further debug this.
So it's not clear if this helps or not because then other problems come into.

Andreas

On Thursday, August 17, 2023 at 10:29:51 PM UTC+2 Rob CJ wrote:
Hi Andreas,

It might be a optimization issues.

Can you add the following to your program and test if the problem is gone?

  pragma opt expr_reduce no

It will disable code optimization.

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:42

Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails
Hi Rob,
thanks that you are digging into this problem and maybe found the issue already.
I'm a heavy Jal User I would call myself, but this is the first issue I found 
over the last years :-)

On Thursday, August 17, 2023 at 9:31:13 PM UTC+2 Rob CJ wrote:
Hi Andreas,

I had a quick look at the generated assemble code for a PIC16.

In your first code example the code is (I changed 3 times i into i, j and k so 
I could compile it):

 ;   10 i=test1()
   movlw0
   movwfv_i
;   11 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

In your last code example where you removed the function the code is:

  clrf v_k
;   35 if k>0 & k<13 then
   movf v_k,w
   bsf  v__bitbucket, 6 ; _btemp7
   btfscv__status, v__z

If I am right - and I hope I am not - the first piece of code does not work 
because the Z flag (v__z) of the status register (v__status) is never affected 
by any of these instructions. In the last code example the clrf instruction 
sets the Z flag.

In other words, moving the return value of 0 to v_i is not the same as clearing 
the value of v_k. So it might be a compiler bug. I wonder why it has not been 
discovered before.

Still need to see if my draft conclusion is correct.

Kind regards,

Rob




Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:07
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hello Rob,
PIC is a 18f26K83
compiler called with: ../jalv25r7/compiler/j

Re: [jallib] IF statement fails

2023-08-18 Thread Rob CJ

Hi Andreas

Strange, I will do some testing this weekend.

Thanks for the update.

Met vriendelijke groet,
Rob Jansen

From: 'off...@schloegl-software.at' via jallib 
Sent: Friday, August 18, 2023 8:33:06 AM
To: jallib 
Subject: Re: [jallib] IF statement fails

Hi Rob,

I tried that. As a result the code size increased (+200 byte), but the program 
doesn't work any more, the output on my display stopped working, so it's hard 
to further debug this.
So it's not clear if this helps or not because then other problems come into.

Andreas

On Thursday, August 17, 2023 at 10:29:51 PM UTC+2 Rob CJ wrote:
Hi Andreas,

It might be a optimization issues.

Can you add the following to your program and test if the problem is gone?

  pragma opt expr_reduce no

It will disable code optimization.

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:42

Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails
Hi Rob,
thanks that you are digging into this problem and maybe found the issue already.
I'm a heavy Jal User I would call myself, but this is the first issue I found 
over the last years :-)

On Thursday, August 17, 2023 at 9:31:13 PM UTC+2 Rob CJ wrote:
Hi Andreas,

I had a quick look at the generated assemble code for a PIC16.

In your first code example the code is (I changed 3 times i into i, j and k so 
I could compile it):

 ;   10 i=test1()
   movlw0
   movwfv_i
;   11 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

In your last code example where you removed the function the code is:

  clrf v_k
;   35 if k>0 & k<13 then
   movf v_k,w
   bsf  v__bitbucket, 6 ; _btemp7
   btfscv__status, v__z

If I am right - and I hope I am not - the first piece of code does not work 
because the Z flag (v__z) of the status register (v__status) is never affected 
by any of these instructions. In the last code example the clrf instruction 
sets the Z flag.

In other words, moving the return value of 0 to v_i is not the same as clearing 
the value of v_k. So it might be a compiler bug. I wonder why it has not been 
discovered before.

Still need to see if my draft conclusion is correct.

Kind regards,

Rob




Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:07
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hello Rob,
PIC is a 18f26K83
compiler called with: ../jalv25r7/compiler/jalv2-x86-64 -no-variable-reuse
no other specific setting
Thanks,
Andreas

On Thursday, August 17, 2023 at 9:00:33 PM UTC+2 Rob CJ wrote:
Hi,

For which PIC did you compile this? 12, 16, 18?

Did you use any compiler optimizations?

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: woensdag 16 augustus 2023 22:18
Aan: jallib 
Onderwerp: [jallib] IF statement fails

Hello everyone,

I found this code is not working (using jal jalv25r7, but also older versions). 
Can anyone pls verify:

var byte i
function test() return byte is
return 0
end function
i=test()
if i>0 & i<13 then
  -- goes here but is wrong
else
 ..
end if

but this code works:
var byte i
function test() return byte is
return 0
end function
i=test()
if i<13 & i>0 then
  ..
else
   -- goes here and OK
end if

if you remove the function, it works, too:
var byte i
i=0
if i>0 & i<13 then
  ..
else
   -- goes here and OK
end if


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group

Re: [jallib] IF statement fails

2023-08-17 Thread Rob CJ

Hi Andreas,

It might be a optimization issues.

Can you add the following to your program and test if the problem is gone?

  pragma opt expr_reduce no

It will disable code optimization.

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:42
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hi Rob,
thanks that you are digging into this problem and maybe found the issue already.
I'm a heavy Jal User I would call myself, but this is the first issue I found 
over the last years :-)

On Thursday, August 17, 2023 at 9:31:13 PM UTC+2 Rob CJ wrote:
Hi Andreas,

I had a quick look at the generated assemble code for a PIC16.

In your first code example the code is (I changed 3 times i into i, j and k so 
I could compile it):

 ;   10 i=test1()
   movlw0
   movwfv_i
;   11 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

In your last code example where you removed the function the code is:

  clrf v_k
;   35 if k>0 & k<13 then
   movf v_k,w
   bsf  v__bitbucket, 6 ; _btemp7
   btfscv__status, v__z

If I am right - and I hope I am not - the first piece of code does not work 
because the Z flag (v__z) of the status register (v__status) is never affected 
by any of these instructions. In the last code example the clrf instruction 
sets the Z flag.

In other words, moving the return value of 0 to v_i is not the same as clearing 
the value of v_k. So it might be a compiler bug. I wonder why it has not been 
discovered before.

Still need to see if my draft conclusion is correct.

Kind regards,

Rob




Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:07
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hello Rob,
PIC is a 18f26K83
compiler called with: ../jalv25r7/compiler/jalv2-x86-64 -no-variable-reuse
no other specific setting
Thanks,
Andreas

On Thursday, August 17, 2023 at 9:00:33 PM UTC+2 Rob CJ wrote:
Hi,

For which PIC did you compile this? 12, 16, 18?

Did you use any compiler optimizations?

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: woensdag 16 augustus 2023 22:18
Aan: jallib 
Onderwerp: [jallib] IF statement fails

Hello everyone,

I found this code is not working (using jal jalv25r7, but also older versions). 
Can anyone pls verify:

var byte i
function test() return byte is
return 0
end function
i=test()
if i>0 & i<13 then
  -- goes here but is wrong
else
 ..
end if

but this code works:
var byte i
function test() return byte is
return 0
end function
i=test()
if i<13 & i>0 then
  ..
else
   -- goes here and OK
end if

if you remove the function, it works, too:
var byte i
i=0
if i>0 & i<13 then
  ..
else
   -- goes here and OK
end if


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/f2b66222-389b-4f41-8705-41e46aad4528n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/f2b66222-389b-4f41-8705-41e46aad4528n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jalli

Re: [jallib] IF statement fails

2023-08-17 Thread Rob CJ

Hi Andreas,

I had a quick look at the generated assemble code for a PIC16.

In your first code example the code is (I changed 3 times i into i, j and k so 
I could compile it):

 ;   10 i=test1()
   movlw0
   movwfv_i
;   11 if i>0 & i<13 then
   movf v_i,w
   bsf  v__bitbucket, 0 ; _btemp1
   btfscv__status, v__z

In your last code example where you removed the function the code is:

  clrf v_k
;   35 if k>0 & k<13 then
   movf v_k,w
   bsf  v__bitbucket, 6 ; _btemp7
   btfscv__status, v__z

If I am right - and I hope I am not - the first piece of code does not work 
because the Z flag (v__z) of the status register (v__status) is never affected 
by any of these instructions. In the last code example the clrf instruction 
sets the Z flag.

In other words, moving the return value of 0 to v_i is not the same as clearing 
the value of v_k. So it might be a compiler bug. I wonder why it has not been 
discovered before.

Still need to see if my draft conclusion is correct.

Kind regards,

Rob




Van: 'off...@schloegl-software.at' via jallib 
Verzonden: donderdag 17 augustus 2023 21:07
Aan: jallib 
Onderwerp: Re: [jallib] IF statement fails

Hello Rob,
PIC is a 18f26K83
compiler called with: ../jalv25r7/compiler/jalv2-x86-64 -no-variable-reuse
no other specific setting
Thanks,
Andreas

On Thursday, August 17, 2023 at 9:00:33 PM UTC+2 Rob CJ wrote:
Hi,

For which PIC did you compile this? 12, 16, 18?

Did you use any compiler optimizations?

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: woensdag 16 augustus 2023 22:18
Aan: jallib 
Onderwerp: [jallib] IF statement fails

Hello everyone,

I found this code is not working (using jal jalv25r7, but also older versions). 
Can anyone pls verify:

var byte i
function test() return byte is
return 0
end function
i=test()
if i>0 & i<13 then
  -- goes here but is wrong
else
 ..
end if

but this code works:
var byte i
function test() return byte is
return 0
end function
i=test()
if i<13 & i>0 then
  ..
else
   -- goes here and OK
end if

if you remove the function, it works, too:
var byte i
i=0
if i>0 & i<13 then
  ..
else
   -- goes here and OK
end if


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/69c9a49a-e83c-4824-a27c-074f25bf0c29n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637C20F0C62C86CBF345E3BE61AA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] IF statement fails

2023-08-17 Thread Rob CJ

Hi,

For which PIC did you compile this? 12, 16, 18?

Did you use any compiler optimizations?

Thanks.

Kind regards,

Rob


Van: 'off...@schloegl-software.at' via jallib 
Verzonden: woensdag 16 augustus 2023 22:18
Aan: jallib 
Onderwerp: [jallib] IF statement fails

Hello everyone,

I found this code is not working (using jal jalv25r7, but also older versions). 
Can anyone pls verify:

var byte i
function test() return byte is
return 0
end function
i=test()
if i>0 & i<13 then
  -- goes here but is wrong
else
 ..
end if

but this code works:
var byte i
function test() return byte is
return 0
end function
i=test()
if i<13 & i>0 then
  ..
else
   -- goes here and OK
end if

if you remove the function, it works, too:
var byte i
i=0
if i>0 & i<13 then
  ..
else
   -- goes here and OK
end if


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2b197dbf-4628-4acd-b13c-11e3b6ba2228n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16374EDB654DAD8B037B6A39E61AA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] bee packages

2023-07-06 Thread Rob CJ

Hi Rob,

Due to a compiler issue the samples do not compile and so a bee-package is not
created.

The latest version of the compiler is not automatically picked up on Kyle's
server.

Matt is working on creating the bee-packages on his server. Work in progress.

I asked Kyle if he could manually install the latest compiler version but I
think he did not see my e-mail yet.

Kind regards,

Rob

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: donderdag 6 juli 2023 16:40
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] bee packages

Natural swarming?

On Thu, Jul 6, 2023 at 5:27 PM Rob Hamerling
mailto:robhamerl...@gmail.com>> wrote:

Hi guys,

I'm missing recent bee packages, the latest I see is of April 30. Where are the
newer ones?

Regards, Rob.

--
Rob Hamerling, Vianen, NL

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/d64c8802-6783-83b5-5c1a-f44fbb9c17ae%40gmail.com.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D88jphmpO5qnS%3DV0Cgmzu0DbcA4%2BmJLcF2%2B4%2B6U8z4n_g%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637229D969BF73A79F7AA5EE62CA%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Releasing untested device files

2023-06-29 Thread Rob CJ

Hi Vasile,

I am using a single chip FM radio chip for my alarm clock that uses IIC as
interface.

I even made a JAL library for it (rda5807m.jal) and a video:
https://youtu.be/ou3_I3khLIU

Kind regards,

Rob

Van: jallib@googlegroups.com namens vsurducan

Verzonden: woensdag 28 juni 2023 20:16
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Releasing untested device files

Rob, why don't you use the FM i2c radio module as clock alarm? :) It's a cool
chip. Perhaps you can program it to wake up on different FM frequencies each
morning

On Tue 27 Jun 2023, 9:13 PM Rob CJ,
mailto:rob...@hotmail.com>> wrote:
Hi David,

Why not use the syntax highlighting in Visual Studio Code using the JAL
extension made by Sunish? VS Code is free.

Looks very nice (and I find VS Code a very nice editor since you can easily
spilt a JAL file and edit in 2 windows at the same time) and it works on
Windows, Linux and MAC. A screenshot is given below.

The installation of installing the VS Code plug-in is described in the Jallib
Tutorial.

Nowadays I only use VS Code for all my development.

And you are correct. RobBest on Instructables is me since my name is Rob and I
live in Best in The Netherlands . I indeed post these project to promote JAL.

Currently I am working on my Digital Alarm Clock project. The clock broke down
but instead of throwing it away I decided to make the a version using a PIC and
JAL. I can then finally make use of some of the libraries that I created
earlier . The project will be posted on Instructable once I have completed
the project.

Kind regards,

Rob

[cid:784e5b50-ce5a-48c3-b90e-b721fa157dd7]

Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>> namens Rob Hamerling
mailto:robhamerl...@gmail.com>>
Verzonden: dinsdag 27 juni 2023 19:59
Aan: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
mailto:jallib@googlegroups.com>>
Onderwerp: Re: [jallib] Releasing untested device files

Hi David,

On 27-06-2023 18:04, pinhe...@gmail.com<mailto:pinhe...@gmail.com> wrote:

One thing I always wanted but was also too lazy to set up, as a configuraiton
file for setting up the syntax coloring and complier command lines for jal in
NotePad++.
And maybe also other popular editors you may know of.

Although I'm not doing much with JAL these days I made a Jal syntax
highlighting file for XED and GEDIT not so long ago. Maybe it can help you to
make something alike for NotePad++ (whatever that may be). In that case see:

https://gitlab.com/robhamerling/jal_language_highlighting_with_gtksourceview

Regards, Rob.

--
Rob Hamerling, Vianen, NL

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/e13fe273-174d-b1d9-3059-0dbb3f047df3%40gmail.com<https://groups.google.com/d/msgid/jallib/e13fe273-174d-b1d9-3059-0dbb3f047df3%40gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16374DFE707BC64A43168C2EE627A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16374DFE707BC64A43168C2EE627A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsuNJUjz%3DzxQj1E_gUm4Gp5gQmboBROqmFvmo-JWTdWhw%40mail.gmail.com<https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsuNJUjz%3DzxQj1E_gUm4Gp5gQmboBROqmFvmo-JWTdWhw%40mail.gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163701DA3202759A4689BD26E625A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Releasing untested device files

2023-06-27 Thread Rob CJ

Hi David,

Why not use the syntax highlighting in Visual Studio Code using the JAL
extension made by Sunish? VS Code is free.

The installation of installing the VS Code plug-in is described in the Jallib
Tutorial.

Nowadays I only use VS Code for all my development.

And you are correct. RobBest on Instructables is me since my name is Rob and I
live in Best in The Netherlands . I indeed post these project to promote JAL.

Kind regards,

Rob

[cid:784e5b50-ce5a-48c3-b90e-b721fa157dd7]

Van: jallib@googlegroups.com namens Rob Hamerling

Verzonden: dinsdag 27 juni 2023 19:59
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Releasing untested device files

Hi David,

On 27-06-2023 18:04, pinhe...@gmail.com wrote:

https://gitlab.com/robhamerling/jal_language_highlighting_with_gtksourceview

Regards, Rob.

--
Rob Hamerling, Vianen, NL

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/e13fe273-174d-b1d9-3059-0dbb3f047df3%40gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16374DFE707BC64A43168C2EE627A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Releasing untested device files

2023-06-27 Thread Rob CJ

yway, it's not the point here.
My opinion is that the more externals peripherals are available in the library, 
the more JAL will become an attractive language.
See for example (beware, I will write the ugly word) the libraries 
available for Arduino.
Why not porting some of them ?

- The emulation of internal harware in software can come very handy when for 
example you need a second I²C bus when the chosen PIC only has the hardware to 
handle one.   A lot of time (and sometimes money) can be saved with that kind 
of libraries.  So, in my opinion, they should be continued to be maintained and 
enhanced when a new major PIC family is distributed.

- No discussion about the internal peripherals routines: this is mandatory and 
should also be maintained and enhanced with each new major family

- The device files are, in my understanding, automatically generated based on 
information retrieved from MPLABX and from Microchip themselves.   Therefore, 
we can easily trust their content, and unless proven otherwise, there's no need 
to exhaustively test every one and each of them

OK.  Now, what's the problem faced by Rob ?
Since apparently Microchip does not distribute samples anymore to hobbyist, Rob 
cannot afford to buy each variant of a new PIC to test them.
That's understandable, and Rob is not to blame.

My proposal for debate is:
WHEN A NEW MODEL OF PIC IS SOLD:
- Don't exhaustively create a blink example for each PIC anymore
- Consider the generated device file as trustfully.
- If that PIC contains changes in the way an internal peripheral works, adapt 
the corresponding jallib file.   If possible, test it in hardware (can be done 
also by someone else than Rob).   Otherwise, test it in the simulator.  As 
suggested, a warning can be issued during compilation to point that the library 
is not totally tested, but anyway, it should also be mentionned in the comments 
of it (the user of a library will then be responsible to check if all goes 
well).It can be asked to the community of users (how many are we ?) to 
report any problem with the library, but ALSO to report when all went well.  In 
that case the library or at least some of the procedures in it can be 
considered validated.  (As a sidenote, this would probably imply new releases 
of the lib more often than once a year... another topic to discuss)
- Emulation of hardware in software would probably not be affected by the use 
in a new PIC, so, don't bother.
- The same goes for the libraries for external devices

I also think that there are not enough people available to help Rob in 
maintaining and enhancing jallib.
This is also (correct me if I'm wrong) almost a one-man labour of love.   
and we all know, from our own experience, what risks this implies

I am not as good a programmer nor a hardware designer than most of you (I am an 
electronics engineer how graduated 30 years ago, but never professionnaly 
worked in electronics  I worked in computer science, but at a management 
level, so I'm completely incompetent ;-)  ), but I'm OK to submit whatever work 
I do in jal for peer reviewing and inclusion in jallib if it can help the 
community.
BUT I HOPE MORE WILL JOIN THE EFFORT !!!

One last suggestion (to Rob): As I understood, you know some people at 
Microchip with whom you have contact to get technical data about the PICS that 
are not publicely available.  Have you considered to contact them or Microchip 
Sales Support to explain your problematic, and maybe they could consider to 
continue to send you the samples you need, freely ?
Since jal is a non-profit initiative, and that by promoting it, it also 
promotes the use of PIC's, this could help in your argumentation.

Just my 2c, because I really think jal and jallib deserve more visibility than 
they receive for now, even with the books of Bert Van Dam.

I'm eager to read your reactions,
Have a nice day,

David



Le mardi 27 juin 2023 à 11:45:40 UTC+2, hans a écrit :

Hi Rob,

Possibly a stupid comment on my part, but why must all types be included in the 
JAL package. I can imagine that companies have very specific wishes, but is 
this also the case with the JALLERS?

A JAL extract from this would at least be much easier for me and save you a lot 
of time answering my nagging .

regards

Hans

Op dinsdag 27 juni 2023 om 10:16:55 UTC+2 schreef Rob CJ:
Hi Oliver,

Nice suggestion.

I could adapt the Python script that creates the device file to add a list of 
untested device files and add a compiler warning to these device files.

There is one thing I am not sure about. Normally all samples are validated and 
build when something changes and when that fails (compiler errors) no new 
bee-package is released.  What I am not sure about if all goes well if some 
samples will create compiler warnings. The fact is that these device files are 
tested with the corresponding blink samples so that will then create compiler 
warnings.

Question for anybody else who knows this. Is

Re: [jallib] Releasing untested device files

2023-06-27 Thread Rob CJ

Hi Oliver,

Nice suggestion.

I could adapt the Python script that creates the device file to add a list of
untested device files and add a compiler warning to these device files.

There is one thing I am not sure about. Normally all samples are validated and
build when something changes and when that fails (compiler errors) no new
bee-package is released. What I am not sure about if all goes well if some
samples will create compiler warnings. The fact is that these device files are
tested with the corresponding blink samples so that will then create compiler
warnings.

Question for anybody else who knows this. Is it allowed to have samples files
that create warnings when being compiled? Does that not break the build?

Thanks.

Kind regards,

Rob

Van: 'Oliver Seitz' via jallib
Verzonden: maandag 26 juni 2023 11:05
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Releasing untested device files

Hi all,

If you would maintain a list of tested devices, all untested ones could have a
compiler warning in the device file. That way, users would be warned that
issues may arise, and they can be asked to inform Rob if no issues arise (and
the device can be added to the "tested" list).

Greets,
Kiste

Am Montag, 26. Juni 2023 um 09:35:51 MESZ hat rob...@hotmail.com
Folgendes geschrieben:

Hi all,

When new PICs are released, I create new device files using the data provided
in MPLABX.

Normally I do a test of a device file by running the blink-a-led sample
program. For that I order free samples from Microchip.

In the years that I have taken over the device file creation from Rob Hamerling
I did not found any issues lately with device files since Microchip is doing a
better job than in the past.

The advantage of this is that I can release a device file as soon as it is
available in MPLABX and you do not need to wait for me to get a sample to test
it.

Let me know what you think.

Thanks

Kind regards,

Rob

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/32e0d734-ab4e-455e-b66f-828dc78bd531n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/1800797843.2813413.1687770347855%40mail.yahoo.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16379D250DBC22E53387DF0AE627A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] r 4x64-LED-Matrix-Screen-Modul

2023-06-25 Thread Rob CJ

Hi Hans,

According to your info it uses a MAX7219. There is a JAL library for that 
display made by Rob Hamerling.

Since there are more displays I think you need to use the library max2719_n 
where you can define the number of modules with n.

So give it a try .

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zaterdag 24 juni 2023 18:42
Aan: jallib 
Onderwerp: [jallib] r 4x64-LED-Matrix-Screen-Modul

Hello all,
Has someone used a module like this?
regards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/abd5bbe3-f218-4cf6-9551-d6000b1fa470n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16375EDDC13F882B6AD5AA46E621A%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] AS5600

2023-06-25 Thread Rob CJ

Hi Hans,

Very nice project!

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zaterdag 24 juni 2023 18:56
Aan: jallib 
Onderwerp: Re: [jallib] AS5600

Hello all,
In the meantime I have my wind set working with the AS5600. I had some problems 
with the included magnet and replaced it with a small radial bar magnet. I also 
made the axle from non-magnetic material. It works flawlessly.
regards
Hans

Op woensdag 4 januari 2023 om 21:29:33 UTC+1 schreef hans:
Hello all,
Was trial and error. The first delivery was defective, the second was missing 
the magnet, the third works fine. I2C from Bert's book used. When the case 
definitions are built in I'm going to pour everything full. Thanks for your 
suggestions.
Hans

Op dinsdag 27 december 2022 om 08:59:11 UTC+1 schreef Kiste:
And just there my suggestion looses its worth: You can sink your AS5600 board 
moisture-proof in a block of epoxy resin (including the wire ends). The magnet, 
nickel plated, can be moisture-proof. Magnetic coupling is one of the few 
environmentally independent means of data transfer.

Greets,
Kiste

Am Dienstag, 27. Dezember 2022, 08:52:06 MEZ hat vsurducan  
Folgendes geschrieben:


Hans, designing a thing to work at -20C+45C and IP67 (protected from dust and 
rain from all directions) is a very difficult task, even if you'll use 
something like Kiste pointed to ( I have the Japanese resistive version of that 
position sensor in 2% linearity).  One thing you should care about is the dew 
point.
https://www.vaisala.com/en/expert-article/dew-point-temperature-what-does-it-mean-and-how-can-it-be-calculated
That's because you will have humidity even in a completely closed box. The most 
dangerous temperature for dewpoint in my area is around +8C.
The only way you can avoid moisture problems is to immerse your PCB completely 
in transformer varnish ( several times, not once) and dry it each time after. 
Of course no more HW debugging after that.
P.S: I think your wife is right. :)
best wishes,

On Mon, Dec 26, 2022 at 11:40 PM hans  wrote:
Hi Tom/ Kiste
, Thank you for your detailed response. Years ago I tried an Arduino set, but I 
didn't get further than a few simple examples. After my C64 and C-basic period, 
I don't feel like tripping over all those small changes in the language again. 
I'm happy to stay with JAL. I've had so much fun with it already.
I made my anemometer about fifteen years ago. I read the 16 positions with 4 
light barriers and one IC shows the LEDs along a cable to our living room. . 
For the wind speed I adapted a bicycle spedometer.
Now there are some moisture problems and I want to make some adjustments.
I will take your experience with me in my adventure
What Kiste indicates is quite a nice thing, but according to my wife I am done 
much too quickly. And she is often right.
Anyway, as soon as the Chinese package arrives, I can continue.
 Happy new year and best wishes to all.
regards
Hans

Op maandag 26 december 2022 om 19:42:18 UTC+1 schreef Tom:

(resent with smaller photo files...)


 Forwarded Message 
Subject:Re: [jallib] AS5600
Date:   Mon, 26 Dec 2022 13:34:09 -0500
From:   Tom Crawford 
Reply-To:   tomc...@gmail.com
To: jal...@googlegroups.com


Some answers to the several questions some of you have asked; hopefully they 
are helpful.
First, most of my 8 bit work is with Arduino, and their IDE.  I have used PICs 
and JAL in the past, but not recently.

1. Cold weather:
- I do not know yet, although I believe it will work fine.  The new device has 
only been bench tested indoors so far.  So many projects, so little time!  
Also, the new device is for the weather station parts of our Little Free 
Library (LFL, see https://littlefreelibrary.org/ for more info), located at the 
end of our driveway.  It was renovated this summer, and re-installed without 
the weather station or the internal computer systems, since it was getting 
colder, and the reno work had already taken too long.  It is now more difficult 
to add the items to the LFL, and to test them...
We have had a LFL for about 7 years, with Arduino Nano's, solar power, 
batteries, and digital radio. The system has worked near perfectly all this 
time, summer and winter, snow, rain, wind...
It is unfortunate I did not have this weather station outside this past week; 
temperatures down to about -20C, winds gusting to about 100 kph!  my location 
is in southern Ontario, Canada.  Some regions around us declared disaster 
emergencies!  We were fortunate not to lose power...

2. Outputs:
My testing has been done only with the I2C interface, and has worked very well. 
 I will include test code below.  I have checked that the analog output works 
okay, but I use only the I2C outputs for my application.

3. Wireless:
I have used the NRF24L01 transceiver module  at both remote and in-house ends, 
for data collection and some control, for years also.  Again, has worked

Re: [jallib] Software PWM

2023-06-21 Thread Rob CJ

Hi David,

The reason for choosing for a step increment of 2 is to limit the number of 
steps. If I had chosen to use a step increment of 1 then the timer has to run 
256 times faster than the chosen period time in order to be able to have 256 
steps in one period.. So in case of 80 Hz frequency timer has to run at around 
20 kHz or an interrupt time of 50 us. That would not leave much time left for 
the main program so that's why I used a step increment of 2 and to reducing the 
timer frequency around 10 kHz. Of course you can decide to go for 20 kHz so 
that you can use the 8 bit value  of the ADC. I assume your PIC runs at a 
higher frequency than 4 MHz.

Below another example using four LEDs, using timer 2. STEP_BRIGHT is called 
UP_BRIGHT here but you get the idea.

procedure pwm_cycle is pragma interrupt
   if PIR1_TMR2IF & PIE1_TMR2IE then
  PIR1_TMR2IF = FALSE

  ; First check the if we need to start a new period.
  if (pwm_period == 0) then
 ; New period. Switch leds on and start a new duty cycle.
 pwm_period = PWM_PERIOD_TIME
 led_1_timer = duty_cycle_1
 led_2_timer = duty_cycle_2
 led_3_timer = duty_cycle_3
 led_4_timer = duty_cycle_4
 led_1 = LED_ON
 led_2 = LED_ON
 led_3 = LED_ON
 led_4 = LED_ON
   else
  pwm_period = pwm_period - 1
   end if


   ; If the timer of the LED is 0 then the duty cycle time has passed.
   if led_1_timer >= UP_BRIGHT then
  led_1_timer = led_1_timer - UP_BRIGHT
   else
  led_1 = LED_OFF
   end if

   if led_2_timer >= UP_BRIGHT then
  led_2_timer = led_2_timer - UP_BRIGHT
   else
  led_2 = LED_OFF
   end if

   if led_3_timer >= UP_BRIGHT then
  led_3_timer = led_3_timer - UP_BRIGHT
   else
  led_3 = LED_OFF
   end if

   if led_4_timer >= UP_BRIGHT then
  led_4_timer = led_4_timer - UP_BRIGHT
   else
  led_4 = LED_OFF
   end if

   end if
end procedure


Kind regards,

Rob


Van: jallib@googlegroups.com  namens 
pinhe...@gmail.com 
Verzonden: woensdag 21 juni 2023 11:33
Aan: jallib 
Onderwerp: Re: [jallib] Software PWM

@Kiste (Got it ;-)   )
Clever way to do it !   I guess it took some time to figure that out, and get 
it running properly, specially if you further had to manage the LED 
multiplexing.
Hats off !
I guess the PIC is running at a fairly high speed to be able to achieve all 
that process ?
BTW: My nickname "Pinhead" is usually a term referring to a pinball freak 
(which I am).   Furthermore, I like horror movies, and Pinhead is the name of 
one of those bad guys we love to hate (in the Hellraiser franchise).   That's 
why ;-)

@Rob
The resolution is not critical for dimming LED's in the way I intend: 127 
steps, as in your solution, are enough.   But why limit it with STEP_BRIGHT = 2 
?
If, for example, I would like to use the ADC value of a LDR to set the 
duty_cycle, I'd simply use the 8 MSB's of the ADC value, and that would give me 
8 bits resolution...
What was the requirement in your application to limit the resolution to 128 
steps ?
Also, is the PWM frequency critical ?  Otherwise, maybe you could get rid of 
the "pwm_period = PWM_PERIOD_TIME" line, isn't it ?

All in all, those two answers are food for thoughts, and I will certainly take 
your good advices.   Thanks for that !

Le mercredi 21 juin 2023 à 07:59:57 UTC+2, Rob CJ a écrit :
Hi David, Oliver,

What should be the resolution of the PWM? I sometimes made it in software using 
one timer and controlling several LEDS. In the example below I control one LED 
using 128 steps (step increment of 2 (STEP_BRIGHT)) but can be extended with 
more LEDs. Would that be sufficient for your application?

This was running on a 12F675 running at 4 MHz. The refresh rate was about 80 Hz 
to prevent flicker.  Below this program you find some calculations. Normally I 
used Timer 2 because of the automatic reload but this PIC did not have that.

; Interrupt routine for timer 0, handling the PWM signal in software.
; This routine is called every 107 us (measured) and takes between 18-28 us.
procedure timer_0_interrupt() is pragma interrupt

   if INTCON_T0IF then

  ; First preset the time for the next interrupt.
  TMR0 = TIMER_0_RELOAD
  INTCON_T0IF = FALSE

  ; Check the if we need to start a new period.
  if (pwm_period == 0) then
 ; New period. Switch LEDs on and start a new duty cycle.
 pwm_period = PWM_PERIOD_TIME
 pwm_timer = duty_cycle
 ; Only turn LED on if it has a duty cycle to prevent flashing.
 if (pwm_timer > 0) then
LED = LED_ON
 end if
  else
 pwm_period = pwm_period - 1
  end if

  ; If the timer of the LED is at the mininum brightness then time has 
passed.
  if (pwm_timer >= BRIGHT_MIN) then

Re: [jallib] Software PWM

2023-06-21 Thread Rob CJ

Hi David, Oliver,

What should be the resolution of the PWM? I sometimes made it in software using 
one timer and controlling several LEDS. In the example below I control one LED 
using 128 steps (step increment of 2 (STEP_BRIGHT)) but can be extended with 
more LEDs. Would that be sufficient for your application?

This was running on a 12F675 running at 4 MHz. The refresh rate was about 80 Hz 
to prevent flicker.  Below this program you find some calculations. Normally I 
used Timer 2 because of the automatic reload but this PIC did not have that.

; Interrupt routine for timer 0, handling the PWM signal in software.
; This routine is called every 107 us (measured) and takes between 18-28 us.
procedure timer_0_interrupt() is pragma interrupt

   if INTCON_T0IF then

  ; First preset the time for the next interrupt.
  TMR0 = TIMER_0_RELOAD
  INTCON_T0IF = FALSE

  ; Check the if we need to start a new period.
  if (pwm_period == 0) then
 ; New period. Switch LEDs on and start a new duty cycle.
 pwm_period = PWM_PERIOD_TIME
 pwm_timer = duty_cycle
 ; Only turn LED on if it has a duty cycle to prevent flashing.
 if (pwm_timer > 0) then
LED = LED_ON
 end if
  else
 pwm_period = pwm_period - 1
  end if

  ; If the timer of the LED is at the mininum brightness then time has 
passed.
  if (pwm_timer >= BRIGHT_MIN) then
 pwm_timer = pwm_timer - STEP_BRIGHT
  else
 LED = LED_OFF
  end if


   end if

end procedure

Some constants I used.

; Specify the values for the minimum and maximum brightness of the LEDs and
; the value to increase or decrease it. The minimum value is not zero since
; we want to know if the device is on or off so there always has to be a
; minium brightness when the device is switched on.
const byte BRIGHT_MIN  = 10  ; Must be >= STEP_BRIGHT.
const byte BRIGHT_MAX  = 254 ; Must be even and <= 254
const byte STEP_BRIGHT = 2   ; This gives 254 / 2 = 127 steps.

; Timer reload value. The clock is 4 MHz so the timer clock is 1 MHz. Let's
; use 80 Hz as PWM frequency for the LEDs. This means that the timer has to
; run at 80 * 125 steps = 10.000 Hz or a period time of 100 us. With a prescale
; of 2 (minimum) the we need a timer value of 1.000.000 / 2 / 10.000 = 50.
; Since we use the timer overflow the reload value becomes 256 - 50 = 206.
; The measured value is 9.333 Hz, most like due to processing time.
const byte TIMER_0_RELOAD = 206.

; See timer init, 10.000 Hz / 125 gives 80 Hz. Measured is 74 Hz.
const byte PWM_PERIOD_TIME = 125

Kind regards,

Rob


Van: 'Oliver Seitz' via jallib 
Verzonden: woensdag 21 juni 2023 07:38
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Software PWM

Salut pinhead,

If I had to extend an existing controller with PWMs, I'd use e.g. PIC16F18313. 
It has 8 pins, I2C and 4 independent PWMs at a cost of less than 1,50€. I 
cannot tell however if the MCLR pin can be used for I2C. A safe choice would be 
12F1572 which is even cheaper and has 4x 16bit PWM. You can use serial_software 
for communication, as the PWMs run happily on their own.

Yes, the way you're describing you could dim LEDs, but each time something else 
is happening, like new I2C-input is processed, all your LEDs would slightly 
flicker.

When I did bitbang-dim 120 multiplexed LEDs, i did it binarily: If bit 7 is 
set, light up the LED for 128µs. Then, if bit 6 is set, light up the LED for 
another 64µs and so on. The brightness sums up in the eye of the beholder. I've 
programmed a timer to generate an interrupt in succession after 128, then 64, 
then 32... µs. However, 4,2 and 1 µs I did without leaving the ISR. I did not 
use any "if" for that, I had an 8x8bit matrix with the dimming values, which I 
rotated by 90°, so I had a byte full of "bit7" of each channel, a "bit6" of 
each channel and so on. So, the ISR had nothing to do but move the "bit7"-byte 
to the output port right before the 128µs interrupt delay, the "bit6"-byte 
before the 64µs delay... That way I could dim 8 LEDs (all on e.g. PORTA) for 
the price of one.

Oliver is my real name, but Kiste (=Carton(fr) =Doos(nl) =Box(en)) is my very 
common nickname, even in real life.

Greets,
Kiste

Am Dienstag, 20. Juni 2023 um 22:10:07 MESZ hat pinhe...@gmail.com 
 Folgendes geschrieben:


Hello Oliver,

Indeed, PIC18F27J13 could be a candidate.  I overlooked this one too quickly (I 
already ranted about the parametric search tool on the µchip site :-{   )
I'll check for the other characteristics.
No internal OPAMP and internal VREF are a bit annoying, but if it's the only 
missing parts, it's ok.

Anyway, what about a PIC that would be programmed as a I²C generator with 
several independant channels, and I²C slave.

He would have nothing else to do than generating the signals.
Consider one channel:
- A register contains the value of its duty cycle (from 0 to 255)
- In the main

Re: [jallib] Peripheral hardware and interrupts

2023-06-02 Thread Rob CJ

Hi Vasile,

Before testing this I gave this some more thought and had a short look at the 
assembly file.

The issue is that as soon at I do any IIC ibrary call from an interrupt 
routine, all these routines become 'interrupt routines' if you know what I 
mean. I think that means that these routines can no longer be called from a 
non-interrupt location like the main program.

For example a non-interrupt routine to transmit something over the IIC looks 
like this:

;  102 function i2c_transmit_byte(byte in data) return bit is
l_i2c_transmit_byte
   movlb0
   movwfv___data_80
;  104PIR1_SSPIF = false  ; clear pending flag
   bcf  v_pir1, 3 ; pir1_ssp1if
;  105sspbuf = data   ; write data
   movf v___data_80,w
   movlb4
   movwfv_ssp1buf
;  108while ! PIR1_SSPIF loop end loop
l__l524
   movlb0
   btfscv_pir1, 3 ; pir1_ssp1if
   goto l__l525
   goto l__l524
l__l525
;  113if SSPCON2_ACKSTAT == low  then
   movlb4
   btfscv_ssp1con2, 6 ; ssp1con2_ackstat
   goto l__l528
;  114   return true -- okay
   movlb0
   bsf  v__pic_temp, 0 ; _pic_temp
   return

But if you do a call to the same IIC procedure from an interrupt the code 
becomes this:

;  102 function i2c_transmit_byte(byte in data) return bit is
l_i2c_transmit_byte
   incf v__ri2c_transmit_byte,f
   decfsz   v__ri2c_transmit_byte,w
   goto l__l712
   movlpHIGH l__l713
   goto l__l713
l__l712
   movf v__pic_stkptr+1,w
   movwfv__fsr0h
   movf v__pic_stkptr,w
   movwfv__fsr0l
   decf v__pic_stkptr,f
   decf v__fsr0l,f
   movf v__fi2c_transmit_byte,w
   movwfv__ind
l__l713
   movf v__pic_temp,w
   movwfv___data_80
;  104PIR1_SSPIF = false  ; clear pending flag
   bcf  v_pir1, 3 ; pir1_ssp1if
;  105sspbuf = data   ; write data
   movf v___data_80,w
   movlb4
   movwfv_ssp1buf
;  108while ! PIR1_SSPIF loop end loop
l__l524
   movlpHIGH l__l525
   movlb0
   btfscv_pir1, 3 ; pir1_ssp1if
   goto l__l525
   goto l__l524
l__l525
;  113if SSPCON2_ACKSTAT == low  then
   movlb4
   btfscv_ssp1con2, 6 ; ssp1con2_ackstat
   goto l__l528
;  114   return true -- okay
   movlb0
   bsf  v__pic_temp, 0 ; _pic_temp
   goto l__l523
;  115else
l__l528
;  116   sspcon1_sspen = false;
   bcf  v_ssp1con1, 5 ; ssp1con1_sspen
;  117   sspcon1_sspen = true;
   bsf  v_ssp1con1, 5 ; ssp1con1_sspen
;  119   return false -- no response
   movlb0
   bcf  v__pic_temp, 0 ; _pic_temp
;  120end if
;  121 end function
l__l523
   decfsz   v__ri2c_transmit_byte,f
   goto l__l715
   return
l__l715
   movf v__pic_stkptr+1,w
   movwfv__fsr0h
   movf v__pic_stkptr,w
   movwfv__fsr0l
   movf v__ind,w
   movwfv__fi2c_transmit_byte
   incf v__fsr0l,w
   movwfv__pic_stkptr
l__l714
   return

I think it cannot be mixed. The only solution I can think of is making separate 
routines that access the IIC hardware registers directly without a call to any 
other - common - routine.

Kind regards,

Rob



Van: jallib@googlegroups.com  namens Rob CJ 

Verzonden: donderdag 1 juni 2023 21

Re: [jallib] Peripheral hardware and interrupts

2023-06-01 Thread Rob CJ

Hi Vasile,

Good suggestion. I will give it a try.

Thanks.

Kind regards,

Rob

Van: jallib@googlegroups.com namens vsurducan

Verzonden: donderdag 1 juni 2023 20:58
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Peripheral hardware and interrupts

Hi Rob,
Perhaps you should disable/enable interrupts within the I2c procedures and not
for the entire main program.
The way you did it, by writing a flag in the ISR and reading it in the main is
correct. If you need less delay between the main execution and interrupt flag
refresh, you should have just one interrupt routine and keep it as short as
possible. Nowadays the JAL libraries are using multiple ISR's which are
controlled entirely by the compiler. This feature does not give too many
options to the user except writing his own procedures for sensitive interrupt
applications instead of using libraries with their own ISR's.

best wishes

On Thu, Jun 1, 2023 at 9:34 PM rob...@hotmail.com
mailto:rob...@hotmail.com>> wrote:
Hi all,

I have the following issue and I am interested in either your suggestions or if
you encountered the same problem. The example is based on the sample program I
made for the real time clock library DS3231.

The DS3231 has two alarms and uses the IIC interface. The device has an
interrupt line that can be activated when an alarm is triggered. I connected
this line to the external interrupt of the PIC.

The main program read the time and sends it to the serial port. Since the main
program calls DA3231 functions, the IIC interface is used to access the DS3231.
When an interrupt occurs, a register has to be read from the DS3231 to see
which alarm was activated also using the IIC interface of course.

In order to prevent that halfway an IIC transmission initiated by a library
call from the main program, I disable the external interrupt of the PIC at the
start of the main program an enable it again at the end of the main program. In
that way I am sure that the interrupt does not interrupt an IIC transmission
initiated by the main program. There is a delay at the end of the main program,
sufficient for any pending interrupt to be handled.

The problem is that it does not work. The PIC just hangs and does not start.
The only solution I found is setting a flag in the interrupt routine and let
the main program poll this flag and read the register from the DS3231 to check
which alarm was activated. But in this way the whole idea of the interrupt is
gone.

Looking forward to your reactions and suggestions.

Thanks.

Kind regards,

Rob

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/679a0f81-03fe-4310-b401-ac69f2d2aeadn%40googlegroups.com.

--
You received this message because you are subscribed to a topic in the Google
Groups "jallib" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jallib/13BABaIMXzs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qt%3DKi2pGVDwyLkzHmZJAsaX0qkoQPxM-p580W4BC%3DKNMw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163770A10C791A2D2901350EE6499%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] [jallib build] buildbot failure in jallib on jallib-bee

2023-05-30 Thread Rob CJ

Hi Vasile,

Are you refering to the problem with the Linux compiler I posted?

I found this page about the subject you mentioned (never heard of it btw):
https://wiki.musl-libc.org/building-llvm.html

It does not seem an easy task to do.

About the Linux compiler. I had compiled it with gcc version 9.0 due to an
upgrade of my Ubuntu system which cause the issue with GLIBC. The problem was
solved by recompiling it with gcc version 7. The server of Kyle should work
with that version but for some reason the new compiler is not picked up so the
build (the validation of the samples and the compile of all samples) keeps
failing.

I am working with Matt to move the validation, compilation and release to the
server of Matt that also hosts the website since the compiler works there
without a problem and it seems more logical to have it all on the same server.

In parallel I am doing the validation and compilation of all samples after a
check-in on GitHub using GitHub actions. In fact it does the same validation
that the server of Kyle does when you commit someting to GitHub. GitHub sends
me a nice e-mail about this validation task if it is succesfull or not ,
screenshot below. And since I was playing with GitHub actions I also managed to
create a JAL Linux compiler and a JAL MAC compiler both only 64-bit. I also
created a 64-bit Windows compiler but the strange thing is that I cannot run it
on my Windows 10 system (access denied) even when all rights are set correctly.
Internet does not provide a solution for this specific problem. A complete
mystery to me. For now I will still create the compilers locally but if needed
they can also be build using GitHub Actions by a press of a button (I do not
create the compilers after a push to GitHub, only to be started by hand).

[cid:af156801-2e71-4ae6-bb8c-3f5ff30118b7]

Van: jallib@googlegroups.com namens vasi vasi

Verzonden: dinsdag 30 mei 2023 15:39
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] [jallib build] buildbot failure in jallib on jallib-bee

If the binary files of the compiler are distributed anyway, for Linux what
about compiling it in a musl/llvm based system (as gcc in Linux can't compile
static if math lib from libc is required) as a truly static binary?

On Sun, May 28, 2023 at 4:09 PM mailto:bu...@sirloon.net>>
wrote:
Hi guys,

This is buildbot speaking. I have finished a build of jallib-bee on jallib.
Buildslave for this Build: sebbot

Build Reason: The Nightly scheduler named 'weekly build (bee)' triggered this
build
Build Source Stamp: HEAD
Blamelist:

BUILD FAILED: failed package
Logs are attached.

sincerely,
-The Buildbot

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/E1q3G8t-00089o-Fj%40casadeyork.com.

--
Vasi

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CABsDq%3D-DD%2BNeLtQPXB7%3DUOAZHKi9wcnXn3jBUypCa9aj9h4Msw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D68AC2D4081307062909E64B9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: 16F15325 blink a led

2023-04-22 Thread Rob CJ

Hi Hans,

I adapted the adc library so it also works for your PIC and made a sample file 
for your PIC as well. I tested it and it works OK.

Note that for this sample file I used RA2 and RC2 for 2 reasons:

  1.  Easy testing since the the pins for the programmer do not interfere (they 
are on RA0 and RA1).
  2.  I wanted to inform users that the channel numbers have to be checked with 
the datasheet. So in this case RA2 = channel 2 and RC2 = channel 18.

I called the sample just 16f15325_adc.jal. I am not sure why 'dependent' and 
independent' where used in the past, maybe that was important before the adc 
library was adapted.

I used one of the previous sample files but made some modifications because of 
the use of other channel numbers.

Attached you find the update of the adc library and the sample file for your 
PIC.

I will add this to GitHub so it will be in the bee-package of coming Sunday.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zaterdag 22 april 2023 17:24
Aan: jallib 
Onderwerp: Re: [jallib] Re: 16F15325 blink a led

I have read the data sheet, I have slept with it, dreamed of it……(wouter said 
once) …. A nightmare.
  May you all just solve this  WOW

Op zaterdag 22 april 2023 om 16:00:03 UTC+2 schreef Rob CJ:
Hi Hans,

There are two issues:

  1.  ADCON1_ADNPREF does not exist so should be removed.
  2.  The adc library assumes a register called ADCON0_GO but it is called 
ADCON0_GONDONE for this chip. I added an alias to solve that (will also fix it 
in the adc library.

So this code compiles.

-- Step 1: ADC analog input pin setup
const byte ADC_CHANNEL = 2 -- Potmeter connected to pin_A2
ANSELA_ANSA2 = TRUE -- Channel 2is analog input
-- Step 2: Set VDD and VSS as Vref
ADCON1_ADPREF = 0b00
-- Step 3: Use Frc as ADC clock
ADCON1_ADCS = 0b111
const ADC_RSOURCE = 10_000 -- Input resistance: 10K potmeter
-- Define alias to solve problem with ADC library
alias ADCON0_GO is ADCON0_GONDONE
-- Now we can include the library
include adc
-- And initialize the whole with our parameters
adc_init()


Kind regards,

Rob



Van: jal...@googlegroups.com  namens hans 

Verzonden: zaterdag 22 april 2023 15:50
Aan: jallib 
Onderwerp: [jallib] Re: 16F15325 blink a led

Thanks to Rob I got the beginning of my circuit working but now I'm stuck with 
another problem.
I want to use pin_A2 as analog input and have used the basics below have tried 
everything. I now get all sorts of errors, both in the 16F15325 lib and also in 
e adc lib.
Can someone help me with the right setting?
-- Step 1: ADC analog input pin setup
?const byte ADC_CHANNEL = 2 -- Potentiometer connected to pin_A2
?ANSELA_ANSA2 = TRUE -- Channel 2 is analog input
-- Step 2: Set VDD and VSS as Vref
?ADCON1_ADPREF = 0b00
?ADCON1_ADNREF = FALSE
-- Step 3: Use Frc as ADC clock
ADCON1_ADCS = 0b111
?const ADC_RSOURCE = 10_000 -- Input resistance: 10K potentiometer
-- Now we can include the library
include adc
-- And initialize the whole with our parameters
?adc_init()

Op donderdag 20 april 2023 om 12:35:15 UTC+2 schreef hans:
Sorry, have used a damaged led, now the blink is working. Up to the next step.

Op donderdag 20 april 2023 om 11:05:50 UTC+2 schreef hans:
I am working with the 16F15325 to use for the NRF24101 but it does not work. So 
i have tried the blink a led from the sample and that  works also not. Used 
anaother pic.. same result.
atached the files
The old man's problems???
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/c733f6eb-f4ba-4822-b79f-974ca34dc7f1n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c733f6eb-f4ba-4822-b79f-974ca34dc7f1n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/233e7b34-8e10-4c26-bb02-02758e70c744n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/233e7b34-8e10-4c26-bb02-02758e70c744n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16378C6CD9B7D820ADD2DE8CE6619%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: 16F15325 blink a led

2023-04-22 Thread Rob CJ

Hi Hans,

There are two issues:

  1.  ADCON1_ADNPREF does not exist so should be removed.
  2.  The adc library assumes a register called ADCON0_GO but it is called 
ADCON0_GONDONE for this chip. I added an alias to solve that (will also fix it 
in the adc library.

So this code compiles.

-- Step 1: ADC analog input pin setup
const byte ADC_CHANNEL = 2 -- Potmeter connected to pin_A2
ANSELA_ANSA2 = TRUE -- Channel 2is analog input
-- Step 2: Set VDD and VSS as Vref
ADCON1_ADPREF = 0b00
-- Step 3: Use Frc as ADC clock
ADCON1_ADCS = 0b111
const ADC_RSOURCE = 10_000 -- Input resistance: 10K potmeter
-- Define alias to solve problem with ADC library
alias ADCON0_GO is ADCON0_GONDONE
-- Now we can include the library
include adc
-- And initialize the whole with our parameters
adc_init()


Kind regards,

Rob



Van: jallib@googlegroups.com  namens hans 

Verzonden: zaterdag 22 april 2023 15:50
Aan: jallib 
Onderwerp: [jallib] Re: 16F15325 blink a led

Thanks to Rob I got the beginning of my circuit working but now I'm stuck with 
another problem.
I want to use pin_A2 as analog input and have used the basics below have tried 
everything. I now get all sorts of errors, both in the 16F15325 lib and also in 
e adc lib.
Can someone help me with the right setting?
-- Step 1: ADC analog input pin setup
?const byte ADC_CHANNEL = 2 -- Potentiometer connected to pin_A2
?ANSELA_ANSA2 = TRUE -- Channel 2 is analog input
-- Step 2: Set VDD and VSS as Vref
?ADCON1_ADPREF = 0b00
?ADCON1_ADNREF = FALSE
-- Step 3: Use Frc as ADC clock
ADCON1_ADCS = 0b111
?const ADC_RSOURCE = 10_000 -- Input resistance: 10K potentiometer
-- Now we can include the library
include adc
-- And initialize the whole with our parameters
?adc_init()

Op donderdag 20 april 2023 om 12:35:15 UTC+2 schreef hans:
Sorry, have used a damaged led, now the blink is working. Up to the next step.

Op donderdag 20 april 2023 om 11:05:50 UTC+2 schreef hans:
I am working with the 16F15325 to use for the NRF24101 but it does not work. So 
i have tried the blink a led from the sample and that  works also not. Used 
anaother pic.. same result.
atached the files
The old man's problems???
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/c733f6eb-f4ba-4822-b79f-974ca34dc7f1n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637E0104390CA103BEEBB44E6619%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] missing devicefile for 16F18075.jal

2023-04-12 Thread Rob CJ

Hi Andreas,

Thanks.to Mic

I do not buy the chips but I order free samples at Microchip. You can only do
that if you have a business which I do not have so I explained to Microchip
that I need them for our Jallib community to test device files. The number of
samples you can order is limited in quantity and in the time period so I cannot
order samples for all new devices at the same time. That is also the reason why
your devicefile was not yet in. It was available on GitHub (like other new
chips) but it was not yet tested and so not release.

The testing of the device is quite simple. I run the available LED blink sample
files to see if they work. It can still be that the device file contains a bug
so if you run into one, just report it. I have not encountered real errors over
the last years. I do see that Microchip sometimes fixes incorrect register
names when a new version of MPLABX comes out. I always update all new device
files as to keep it consistent.

Once a sample works, all related devices for that same family are added to the
Jallib release. You can download the bee-package if you want the latest and
greatest device files and libraries.

Today I ran into one issue, I ordered a sample of a PIC18F46q71 and it did not
work. I was already informed by Rob Hamerling that he encountered the same
issue but I had no sample to test it. It seems that the bug is in the MPLABX
IPE software of Microchip since I wanted to program it with the SNAP programmer
(the newer chips are not supported by Microchip with the PICkit3 software) but
as said it did not work. Luckily I had received the latest version of the
PICKit+ software from Evan and that did the job. If I had not know it up front
I would have spent hours to find it out but Rob Hamerling had it already
working with his own programmer so the chip and the device file should be OK.

And about the compiler. There are issues reported that I would like to fix but
in some cases it is very hard to do since it is not code that I have written.
So sometimes I do an attempt and if it is not successful then I stop and try
again some other time. You can find the reported issues on GitHub under
Jallib/compiler. Most of the time there is a workaround but it would be better
to get the bugs out.

Good luck with your project.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: woensdag 12 april 2023 19:28
Aan: jallib
Onderwerp: Re: [jallib] missing devicefile for 16F18075.jal

I never thought you are buying new chips to physically test them before release
the new device files. Outstanding quality comitment!! Now I understand why the
compiler does such a great job over all the years! Thank you Rob!
Andreas

On Wednesday, April 12, 2023 at 7:02:19 PM UTC+2 rob...@hotmail.com wrote:
Hi Andreas,

I received the PIC16F18075 and tested and, as you already mentioned, it works.
I added the device to the Jallib release so it will be in the next bee-package.

In the change log you can see which other device files and libraries have been
added.

Kind regards,

Rob

Op zondag 2 april 2023 om 09:36:00 UTC+2 schreef rob...@hotmail.com:
Thanks for the feedback.

I ordered the samples for this PIC and do some testing too and add the device
file to the release.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: zaterdag 1 april 2023 20:32
Aan: jallib
Onderwerp: Re: [jallib] missing devicefile for 16F18075.jal

Hi, I have been working with this file for a while now, and all seems fine as
it usually does.

On Tuesday, March 28, 2023 at 11:34:26 PM UTC+2 off...@schloegl-software.at
wrote:
Thanks a lot Rob! I will let you know if I can see anything wrong with it in a
few days.
Thanks for the superfast response!
Andreas

On Tuesday, March 28, 2023 at 2:19:43 PM UTC+2 Rob CJ wrote:
Hi,

That device file is not yet released since it was not tested yet.

You can give it a try, see attached device file. I assume it works since I did
not encounter any problems over the last year.

I am curretly using an 16F18076 without problems in the device file (not in the
chip though ).

Can you let us know if it works?

Thanks.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: dinsdag 28 maart 2023 13:16
Aan: jallib
Onderwerp: [jallib] missing devicefile for 16F18075.jal

Hello everyone, I started a new projet based on this device, but no devicefile
yet. Can anyone provide one? Thank you!

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/a8f785f8-ac3f-4fe1-af7e-42a324fa0ac3n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/

Re: [jallib] Device file for PIC16F17156

2023-04-10 Thread Rob CJ

Hi David,

Same issue, not yet in MPLABX so not able to generate a device file yet.

I wanted to suggest the site of Microchip to select the device but I saw you
already found it.

It is indeed not a handy site or you must be very patient.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Pinhead

Verzonden: maandag 10 april 2023 19:13
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] Device file for PIC16F17156

Thanks Rob,

In the meantime, I was also looking also for another model and found 18F24Q71
that could meet my expectations, but it is not (yet) supported by jal
either.

What I need:

MANDATORY:

- Two SPI bus (CLK and Data will be shared; /CS will select the chip)
- One I²C bus
- One simple serial port (DT + CK)
- One OPA that can be configured in Unity gain mode
- ADC (8 bit resolution is enough)
- At least two 16-bit timers
- At least two 8-bit timers
- 28-pins form factor with 25 I/O pins (/MCLR not included)
- 128-bits of EEPROM or HEF or NVRAM

- A fair amount of program memory since my application will include a lot of
strings (at least 7 k)

NICE TO HAVE:

- PPS
- ADC can be configured to internally connect to OPA_Output as input
- RTCC

I will not buy or order samples as long as I am not sure at 80% of which
reference I will use, so I will not be able to test a device file in real
condition, but thanks for the proposal.

By the way, The Microchip selection tool on their website really sucks. Does
anyone know of a simplier way to enter criteria to search for a suitable part ?

Have a nice day

Le 10-04-23 à 18:58, Rob CJ a écrit :
Hi David,

As soon as the devices is part of MPLABX I can create a device file. Since it
is not yet available in MPLABX 6.05 I also did not yet order a sample for
testing.

When a new version of MPLABX is out where and that device is in, I can send you
an untested device file.

I do not know when a new version of MPLABX is released so we have to wait for
it.

Kind regards,

Rob

Van: jallib@googlegroups.com<mailto:jallib@googlegroups.com>
<mailto:jallib@googlegroups.com> namens
pinhe...@gmail.com<mailto:pinhe...@gmail.com>
<mailto:pinhead...@gmail.com>
Verzonden: maandag 10 april 2023 17:41
Aan: jallib <mailto:jallib@googlegroups.com>
Onderwerp: [jallib] Device file for PIC16F17156

Hi there,

Starting a new project, I was considering using the 16F17156. But the device
is still very new and the device file apparently does not exists yet.
Do you have an idea if and when it could be available ? Otherwise, I can also
consider using another PIC

Thanks for your answer, and have a nice day,

David
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/97722f64-5f8b-495c-afe4-d9f97c3e56c2n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/97722f64-5f8b-495c-afe4-d9f97c3e56c2n%40googlegroups.com?utm_medium=email_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163791E6F225FA4A4B994CABE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB163791E6F225FA4A4B994CABE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/d162cc1d-8f79-5230-2a28-be44ba631dbb%40gmail.com<https://groups.google.com/d/msgid/jallib/d162cc1d-8f79-5230-2a28-be44ba631dbb%40gmail.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637FA596ED77699EE57BDFDE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Device file for PIC16F17156

2023-04-10 Thread Rob CJ

Hi David,

As soon as the devices is part of MPLABX I can create a device file. Since it
is not yet available in MPLABX 6.05 I also did not yet order a sample for
testing.

When a new version of MPLABX is out where and that device is in, I can send you
an untested device file.

I do not know when a new version of MPLABX is released so we have to wait for
it.

Kind regards,

Rob

Van: jallib@googlegroups.com namens
pinhe...@gmail.com
Verzonden: maandag 10 april 2023 17:41
Aan: jallib
Onderwerp: [jallib] Device file for PIC16F17156

Hi there,

Thanks for your answer, and have a nice day,

David

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/97722f64-5f8b-495c-afe4-d9f97c3e56c2n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163791E6F225FA4A4B994CABE6959%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] missing devicefile for 16F18075.jal

2023-04-02 Thread Rob CJ

Thanks for the feedback.

I ordered the samples for this PIC and do some testing too and add the device
file to the release.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: zaterdag 1 april 2023 20:32
Aan: jallib
Onderwerp: Re: [jallib] missing devicefile for 16F18075.jal

Hi, I have been working with this file for a while now, and all seems fine as
it usually does.

On Tuesday, March 28, 2023 at 2:19:43 PM UTC+2 Rob CJ wrote:
Hi,

That device file is not yet released since it was not tested yet.

You can give it a try, see attached device file. I assume it works since I did
not encounter any problems over the last year.

I am curretly using an 16F18076 without problems in the device file (not in the
chip though ).

Can you let us know if it works?

Thanks.

Kind regards,

Rob

Van: 'off...@schloegl-software.at' via jallib
Verzonden: dinsdag 28 maart 2023 13:16
Aan: jallib
Onderwerp: [jallib] missing devicefile for 16F18075.jal

Hello everyone, I started a new projet based on this device, but no devicefile
yet. Can anyone provide one? Thank you!

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/a8f785f8-ac3f-4fe1-af7e-42a324fa0ac3n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/a8f785f8-ac3f-4fe1-af7e-42a324fa0ac3n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/bd47bfff-c658-497d-b54c-b322cbe1d527n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/bd47bfff-c658-497d-b54c-b322cbe1d527n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB163756745DAF9781A3EF2C6FE68D9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Re: problem with filling a sector buffer

2023-03-23 Thread Rob CJ

Hi Peter,

In general it is recommended to put a 100 nF capacitors close to every IC that 
you use for correct operation.

It might have been the cause of your issue.

Kind regards,

Rob

Van: jallib@googlegroups.com  namens ZetWeeh 

Verzonden: zondag 19 maart 2023 15:22
Aan: jallib@googlegroups.com 
Onderwerp: RE: [jallib] Re: problem with filling a sector buffer


Hi Matt

I waited some time for an answer (just like you).

Today I looked myself again. I removed the resistor and all kept working.

I was not surprised because ‘byte for byte’ had worked.

I used a micro sd card holder and on the website I saw that between 3V3 and GND 
a 100nF was placed.

When I used my original program of ‘byte for byte’ and ‘sector buffer’ that 
gave the problem earlier: problem was solved with the 100nF.

I think this is the explanation for the problem instead of the resistor.





Regards,

Peter



Van: Matthew Schinkel
Verzonden: dinsdag 14 maart 2023 22:03
Aan: jallib
Onderwerp: Re: [jallib] Re: problem with filling a sector buffer



Hi, Glad you got it to work. I had suggested the pull up resistor because I 
know some PICs have some open-drain pins. If you have any more issues add pull 
ups to sdi/sdo/clk pins as well.



I just looked through the 18f4455 manual. It doesn't look like pin_a5 has an 
open drain.



Does anyone know why this worked for him?



Matt.





On Monday, March 13, 2023 at 5:26:50 PM UTC-4 zet@gmail.com wrote:

Hi Matt and Rob



It works!



Inverting the serial port gave rubbish and 1 stopbit I use standard.

But Matt wrote a mail: ‘I asked Rob ….’ and then a short second mail: try a 
pull-up resistor of 1K on CS and that was the solution for me.



And not so funny: sometimes I got about ten of ‘A’ and then rubbish.

I thought the ‘A’ is of earlier attemps and I even formatted the SD card!

In the capture of Rob I saw the whole Marilyn and it started with ‘’.

I thougt the writing did not succeed but now I know the reading crashed.



Rob: in the original code the writing and reading per byte of Marilyn was 
succesfull.

So there could not be a hardware problem.



I already changed the writing in writing the hex-code.



Thank you both for your help.



Regards,

Peter



Van: rob...@hotmail.com
Verzonden: zaterdag 11 maart 2023 15:36
Aan: jallib
Onderwerp: Re: [jallib] Re: problem with filling a sector buffer



Hi Peter, Matt,



I had a PIC 18F4550 which is from the same family as the 18F4455 and ran the 
program. I only had to change the serial port to invert the output and use 1 
stopbit instead of 2 but that cannot be the issue. I did not make any other 
changes.



It seems to work OK so there must be something wrong with either the PIC, the 
hardware or the SD card. I ran the PIC at 5 Volt using a level shifter to 
connect to the SD car which was at 3.3 Volt.



I used the Marilyn data that was given in this post. Attached the program and 
the terminal output.



Kind regards,

Rob







Op maandag 27 februari 2023 om 23:16:48 UTC+1 schreef zet@gmail.com:

Hi Matthew



I sent you the code of the 18F4455 so you could bettter see what is goning 
wrong.

In the meantime I rewrote the code for the 16F18877. Also here byte for byte 
was working but the sample with a sector buffer refused to do what it had to do.



Regards,

Peter



Van: Matthew Schinkel
Verzonden: woensdag 22 februari 2023 03:14
Aan: jallib
Onderwerp: Re: [jallib] Re: problem with filling a sector buffer



Hi, this works from example 3, assuming the array is a constant (you didn't 
show the array in your example).



   const byte MARILYN[504] = {0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,0x41,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,
  0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,0x42,

Re: [jallib] double LCD

2023-02-16 Thread Rob CJ

Hi Hans,

Not sure if I understand you correctly but you have 2 enable pins, 1 for each 
display. Why do you want to change the alias of a pin? Why not just use the 2 
pins and use 2 aliases? I do not understand the difference between changing 
aliases and changing pins.

Can you explain it in more detail?

Thanks

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: woensdag 15 februari 2023 21:00
Aan: jallib 
Onderwerp: [jallib] double LCD

Hi all,
I have a few LCDs which have 2 x 2 character lines. All connections are common, 
but each part has its own enable. So if I change the enable I can control both. 
Is there a way to change the alias of the enable in the program to change to 
another pin?
regards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/37f2b309-6b73-465a-be49-dda946113510n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637F619FB2BC70ABBFC7718E6A09%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] interrupt on change 12F1840

2023-02-04 Thread Rob CJ

Hi Matt,

Maybe indeed a good suggestion to only keep the samples that do not use the
library.

I am thinking if there is another way to build the library so let's wait a
while before removing samples.

For now I would just keep it in the upcoming release.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Matthew Schinkel

Verzonden: dinsdag 31 januari 2023 23:51
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

We could remove the samples related to the interrupt on change library, and
keep the lib where it is or rename it.

Rob, is there a better way to make a library? Ideally we would want one library
that works on all devices.

Matt.

On Tuesday, January 31, 2023 at 12:58:14 PM UTC-5 rob...@hotmail.com wrote:
Hi Matt,

I had a look at the library but with the current - but clever - set-up it is
not easy to change by using the same set-up.

Since I updated the sample program of Hans I can add that too as a sample file
that does not use the library.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: dinsdag 31 januari 2023 07:47

Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Matt,
Please leave it so it is, i use it in older programs.
regards
Hans

Op maandag 30 januari 2023 om 23:35:12 UTC+1 schreef mattsc...@hotmail.com:
Should we remove the interrupt on change library?

This sample shows a good example of how to use interrupt on change without a
library:
18f4620_interrupt_on_change_pin_b0.jal

Or does someone want to update the library?

Matt.

On Saturday, January 28, 2023 at 2:42:08 PM UTC-5 rob...@hotmail.com wrote:
Hi Hans,

Good to hear that. I could add it as sample file as a version that does not use
a library.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 20:33

Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Rob,
Works fine,, base for a sample ??
regards
Hans

Op zaterdag 28 januari 2023 om 17:15:05 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

It was easier to update your program than changing the library. I think with
the current set-up is it not easy to change the library but maybe someone else
has a brilliant idea.

Attached your program version that compiles and not using the library. It was
not tested, I leave that up to you.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 16:46

Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Hans,

I had a look at the library but with the current set-up I cannot solve it with
aliases since PICs can have multiple ports that support interrupt on change and
the library only works for one port (B).

I will give it some more thought

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 15:00
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I saw indeed that the library supports only port b. It can be fixed with
aliases to also support port a but that need some work because the library is
quite large.

I tried to see if it compiles when I add aliases for only port a and only 1 pin
and that compiles. Attached your program with using only one pin and a draft
update of the change. You can at least test if 1 pin works 

Note that this library is just a hack and far from complete! I was thinking of
making the change in a different way so that it requires less work.

So if you are patient I can make the change.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 11:53
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Op zaterdag 28 januari 2023 om 11:49:07 UTC+1 schreef hans:
Hi Rob,
I have tried but Yes but this one has no port B

Op zaterdag 28 januari 2023 om 10:43:37 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com?utm_medium=email_

Re: [jallib] interrupt on change 12F1840

2023-01-31 Thread Rob CJ

Hi Matt,

I had a look at the library but with the current - but clever - set-up it is
not easy to change by using the same set-up.

Since I updated the sample program of Hans I can add that too as a sample file
that does not use the library.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: dinsdag 31 januari 2023 07:47
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Matt,
Please leave it so it is, i use it in older programs.
regards
Hans

Op maandag 30 januari 2023 om 23:35:12 UTC+1 schreef mattsc...@hotmail.com:
Should we remove the interrupt on change library?

This sample shows a good example of how to use interrupt on change without a
library:
18f4620_interrupt_on_change_pin_b0.jal

Or does someone want to update the library?

Matt.

On Saturday, January 28, 2023 at 2:42:08 PM UTC-5 rob...@hotmail.com wrote:
Hi Hans,

Good to hear that. I could add it as sample file as a version that does not use
a library.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 20:33

Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Rob,
Works fine,, base for a sample ??
regards
Hans

Op zaterdag 28 januari 2023 om 17:15:05 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

It was easier to update your program than changing the library. I think with
the current set-up is it not easy to change the library but maybe someone else
has a brilliant idea.

Attached your program version that compiles and not using the library. It was
not tested, I leave that up to you.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 16:46

Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Hans,

I had a look at the library but with the current set-up I cannot solve it with
aliases since PICs can have multiple ports that support interrupt on change and
the library only works for one port (B).

I will give it some more thought

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 15:00
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I saw indeed that the library supports only port b. It can be fixed with
aliases to also support port a but that need some work because the library is
quite large.

Note that this library is just a hack and far from complete! I was thinking of
making the change in a different way so that it requires less work.

So if you are patient I can make the change.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 11:53
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Op zaterdag 28 januari 2023 om 11:49:07 UTC+1 schreef hans:
Hi Rob,
I have tried but Yes but this one has no port B

Op zaterdag 28 januari 2023 om 10:43:37 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com?utm_medium=email_source=footer>.

Re: [jallib] interrupt on change 12F1840

2023-01-28 Thread Rob CJ

Hi Hans,

Good to hear that. I could add it as sample file as a version that does not use
a library.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 20:33
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Rob,
Works fine,, base for a sample ??
regards
Hans

Op zaterdag 28 januari 2023 om 17:15:05 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

It was easier to update your program than changing the library. I think with
the current set-up is it not easy to change the library but maybe someone else
has a brilliant idea.

Attached your program version that compiles and not using the library. It was
not tested, I leave that up to you.

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 16:46

Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840
Hi Hans,

I had a look at the library but with the current set-up I cannot solve it with
aliases since PICs can have multiple ports that support interrupt on change and
the library only works for one port (B).

I will give it some more thought

Kind regards,

Rob

Van: jal...@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 15:00
Aan: jal...@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I saw indeed that the library supports only port b. It can be fixed with
aliases to also support port a but that need some work because the library is
quite large.

Note that this library is just a hack and far from complete! I was thinking of
making the change in a different way so that it requires less work.

So if you are patient I can make the change.

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 11:53
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Op zaterdag 28 januari 2023 om 11:49:07 UTC+1 schreef hans:
Hi Rob,
I have tried but Yes but this one has no port B

Op zaterdag 28 januari 2023 om 10:43:37 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D991F751610ED0CDBB30E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637D991F751610ED0CDBB30E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib&

Re: [jallib] interrupt on change 12F1840

2023-01-28 Thread Rob CJ

Hi Hans,

It was easier to update your program than changing the library. I think with
the current set-up is it not easy to change the library but maybe someone else
has a brilliant idea.

Attached your program version that compiles and not using the library. It was
not tested, I leave that up to you.

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 16:46
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I had a look at the library but with the current set-up I cannot solve it with
aliases since PICs can have multiple ports that support interrupt on change and
the library only works for one port (B).

I will give it some more thought

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 15:00
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I saw indeed that the library supports only port b. It can be fixed with
aliases to also support port a but that need some work because the library is
quite large.

Note that this library is just a hack and far from complete! I was thinking of
making the change in a different way so that it requires less work.

So if you are patient I can make the change.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 11:53
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Op zaterdag 28 januari 2023 om 11:49:07 UTC+1 schreef hans:
Hi Rob,
I have tried but Yes but this one has no port B

Op zaterdag 28 januari 2023 om 10:43:37 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D991F751610ED0CDBB30E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB1637D991F751610ED0CDBB30E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16379D9B310305C234584D32E

Re: [jallib] interrupt on change 12F1840

2023-01-28 Thread Rob CJ

Hi Hans,

I had a look at the library but with the current set-up I cannot solve it with
aliases since PICs can have multiple ports that support interrupt on change and
the library only works for one port (B).

I will give it some more thought

Kind regards,

Rob

Van: jallib@googlegroups.com namens Rob CJ

Verzonden: zaterdag 28 januari 2023 15:00
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] interrupt on change 12F1840

Hi Hans,

I saw indeed that the library supports only port b. It can be fixed with
aliases to also support port a but that need some work because the library is
quite large.

Note that this library is just a hack and far from complete! I was thinking of
making the change in a different way so that it requires less work.

So if you are patient I can make the change.

Kind regards,

Rob

Van: jallib@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 11:53
Aan: jallib
Onderwerp: Re: [jallib] interrupt on change 12F1840

Op zaterdag 28 januari 2023 om 11:49:07 UTC+1 schreef hans:
Hi Rob,
I have tried but Yes but this one has no port B

Op zaterdag 28 januari 2023 om 10:43:37 UTC+1 schreef rob...@hotmail.com:
Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob

Van: jal...@googlegroups.com namens hans

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+un...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/c8e79cd7-4a56-4c8c-80e4-c8d6afb18388n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com<mailto:jallib+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM<https://groups.google.com/d/msgid/jallib/GVXP195MB16371BC45D3D327F9AF3DDB0E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D991F751610ED0CDBB30E6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] interrupt on change 12F1840

2023-01-28 Thread Rob CJ

Hi Hans,

Did you check the interrupt on change sample file?

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: zaterdag 28 januari 2023 10:05
Aan: jallib 
Onderwerp: [jallib] interrupt on change 12F1840

Hello all,
I would like to apply an interrupt on change in a 12F1840. Does anyone have an 
example of this?
retgards
Hans

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/65c3df4a-bc83-487b-b058-e67fa7ef3029n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637D1F265BA164E5B24B30BE6CD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PIC Simulator (free software)

2023-01-26 Thread Rob CJ

Hi Vasile,

Hi have played with this one but it is not free: https://oshonsoft.com/pic.php
[https://www.oshonsoft.com/picscreenshot2.png]
OshonSoft PIC Simulator IDE with PIC Basic
Compiler
PIC SIMULATOR IDE (with pic basic compiler) HOMEPAGE. PIC Simulator IDE is
powerful application that supplies Microchip microcontroller users with
user-friendly graphical development environment for Windows with integrated
simulator (emulator), pic basic compiler, assembler, disassembler and debugger.
PIC Simulator IDE supports the extensive number of microcontrollers (MCUs) from
the Microchip ...
oshonsoft.com

I also did some debugging using MPLABX. You can load your hexfile and step
through the code. When using a PICkit3 you can also set a breakpoint and stop
but it is not easy since you need the asm file to find out where you are.

Kind regards,

Rob

Van: jallib@googlegroups.com namens vsurducan

Verzonden: donderdag 26 januari 2023 04:45
Aan: jallib@googlegroups.com
Onderwerp: Re: [jallib] PIC Simulator (free software)

Beware, you will not be able to simulate your code as is, just non delayed
routines, some math computations, etc. Old jal had a built in simulator for
this, it was good stuff at that time...

On Wed 25 Jan 2023, 9:50 PM flyway38
mailto:fsfon...@gmail.com> wrote:
Hello all,

Does anyone know any PIC simulator, free software for PC to check some basic
stuff code and able to read the HEX file?
Thank you very much.

Kind regards,
Filipe Santos.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/aed6af05-ad9e-4f33-953d-17a35a8058bfn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/CAM%2Bj4qsdmLEe29vunsCGKBHmRgPdawKpUcFv%3D%3Da2hvjihrOPKQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jallib/GVXP195MB1637B9D44D2D629E65275ADBE6CF9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Jallib - 1.7 Beta

2023-01-20 Thread Rob CJ

Hi Vasile,

Note that these are items that are on GitHub and are not yet part of the 
release. Some because e.g. the device could not yet be tested or samples are 
not yet available.

The contents of the items which will be part of the new release are in the 
Changelog (see attachment) .

These items are already part of the bee-packages.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens vsurducan 

Verzonden: vrijdag 20 januari 2023 04:44
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] Jallib - 1.7 Beta

The jal growth is fantastic! Congrats guys!


On Fri 20 Jan 2023, 4:44 AM Matthew Schinkel 
mailto:mattschin...@hotmail.com> wrote:
Here's the output of torelease.py. Thanks Rob.

If anyone wants any of these in the release, please add them to TORELEASE.

Unreleased libraries and device files

include/device/12lf1840t39a.jal
include/device/12lf1840t48a.jal
include/device/16f17114.jal
include/device/16f17115.jal
include/device/16f17124.jal
include/device/16f17125.jal
include/device/16f17144.jal
include/device/16f17145.jal
include/device/16f18026.jal
include/device/16f18046.jal
include/device/16f18054.jal
include/device/16f18055.jal
include/device/16f18074.jal
include/device/16f18075.jal
include/device/16f18114.jal
include/device/16f18115.jal
include/device/16f18124.jal
include/device/16f18125.jal
include/device/16f18126.jal
include/device/16f18144.jal
include/device/16f18145.jal
include/device/16f18146.jal
include/device/16f1829lin.jal
include/device/16f83.jal
include/device/16f84.jal
include/device/16lf1824t39a.jal
include/device/18f26q71.jal
include/device/18f46q71.jal
include/device/18f56q71.jal
include/device/18f86j72.jal
include/device/18f87j72.jal
include/external/battery/ltc2942.jal
include/external/lcd/glcd_digits.jal
include/external/oxygen/goel370.jal
include/external/pressure/bmp085.jal
include/external/rtc/rtc_mcp7940.jal
include/external/sound/beep.jal
include/external/storage/flash_sst25vf.jal
include/jal/debug_queue.jal

39 unreleased libraries and device files


Unreleased samples (including basic blink samples)
---
sample/12f1572_steppermotor.jal
sample/12lf1840t39a_blink_hs.jal
sample/12lf1840t39a_blink_intosc.jal
sample/12lf1840t48a_blink_hs.jal
sample/12lf1840t48a_blink_intosc.jal
sample/16f1519_bmp085.jal
sample/16f1615_steppermotor.jal
sample/16f17114_blink_hs.jal
sample/16f17114_blink_intosc.jal
sample/16f17115_blink_hs.jal
sample/16f17115_blink_intosc.jal
sample/16f17124_blink_hs.jal
sample/16f17124_blink_intosc.jal
sample/16f17125_blink_hs.jal
sample/16f17125_blink_intosc.jal
sample/16f17144_blink_hs.jal
sample/16f17144_blink_intosc.jal
sample/16f17145_blink_hs.jal
sample/16f17145_blink_intosc.jal
sample/16f1765_steppermotor.jal
sample/16f18026_blink_intosc.jal
sample/16f18046_blink_intosc.jal
sample/16f18054_blink_intosc.jal
sample/16f18055_blink_intosc.jal
sample/16f18074_blink_intosc.jal
sample/16f18075_blink_intosc.jal
sample/16f18114_blink_hs.jal
sample/16f18114_blink_intosc.jal
sample/16f18115_blink_hs.jal
sample/16f18115_blink_intosc.jal
sample/16f18124_blink_hs.jal
sample/16f18124_blink_intosc.jal
sample/16f18125_blink_hs.jal
sample/16f18125_blink_intosc.jal
sample/16f18126_blink_hs.jal
sample/16f18126_blink_intosc.jal
sample/16f18144_blink_hs.jal
sample/16f18144_blink_intosc.jal
sample/16f18145_blink_hs.jal
sample/16f18145_blink_intosc.jal
sample/16f18146_blink_hs.jal
sample/16f18146_blink_intosc.jal
sample/16f1829lin_blink_hs.jal
sample/16f1829lin_blink_intosc.jal
sample/16f18325_steppermotor.jal
sample/16f83_blink_hs.jal
sample/16f84_blink_hs.jal
sample/16lf1824t39a_blink_hs.jal
sample/16lf1824t39a_blink_intosc.jal
sample/18f06q41_blink_hs.jal
sample/18f2585_oxygen_goel370.jal
sample/18f26k22_sst25vf.jal
sample/18f26q71_blink_hs.jal
sample/18f26q71_blink_intosc.jal
sample/18f27j53_sst25vf.jal
sample/18f27q84_blink_hs.jal
sample/18f4620_rotary_encoder_e6b2.jal
sample/18f4620_rtc_mcp7940.jal
sample/18f4620_timer.jal
sample/18f46q71_blink_hs.jal
sample/18f46q71_blink_intosc.jal
sample/18f47q84_blink_hs.jal
sample/18f56q71_blink_hs.jal
sample/18f56q71_blink_intosc.jal
sample/18f57q84_blink_hs.jal
sample/18f67j50_debug_queue.jal
sample/18f86j72_blink_hs.jal
sample/18f86j72_blink_intosc.jal
sample/18f86j72_blink_intosc_usb.jal
sample/18f87j72_blink_hs.jal
sample/18f87j72_blink_intosc.jal
sample/18f87j72_blink_intosc_usb.jal

72 unreleased sample files


Unreleased Project files

project/catpad_mw/Handset_16f877.jal
project/catpad_mw/adc_channels.jal
project/catpad_mw/adc_clock.jal
project/catpad_mw/analogue.jal
project/catpad_mw/array_storage.jal
project/catpad_mw/bcd_utils.jal
project/catpad_mw/calendar.jal
project/catpad_mw/cat_ft817.jal
project/catpad_mw/catpad_main.jal
project/catpad_mw/catpatv2.jal
project/catpad_mw/delay.jal
project/catpad_mw/dev_glcd_ks0108.jal

Re: [jallib] 12F1840 sample ADC and usart

2023-01-17 Thread Rob CJ

Hi Hans,

Step 2 and step 3 should change:

-- Step 2: Set VDD as Vref
ADCON1_ADPREF = 0b00
-- Step 3: Use Frc as ADC clock
ADCON1_ADCS = 0b011

I hope this works.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens hans 

Verzonden: dinsdag 17 januari 2023 17:28
Aan: jallib 
Onderwerp: [jallib] 12F1840 sample ADC and usart

Hello ,
Does anyone have an example for this pic, I want an2 in adc and A0 as Tx and A1 
as Rx. I've tried to derive some from other programs but I keep stumbling on 
the datasheet.
Hans

-- chip setup
include 12f1840

-- Internal oscillator at 8 MHz with PLL enabled -> 32 MHz
pragma target clock32_000_000 -- oscillator frequency

pragma target OSC  INTOSC_NOCLKOUT-- internal oscillator
pragma target WDT  DISABLED   -- watchdog off
pragma target PWRTEENABLED-- power up delay
pragma target MCLR EXTERNAL   -- reset externally
pragma target BROWNOUT DISABLED   -- no brownout
pragma target CLKOUTEN DISABLED   -- no clock out
pragma target IESO DISABLED   -- no osc switchover
pragma target FCMENDISABLED   -- no clock monitoring
pragma target PLLENENABLED-- PLL enabled
pragma target LVP  DISABLED-- allow LVP

OSCCON_IRCF   = 0b1110-- 8 MHz (+ PLL -> 32 MHz)
OSCCON_SCS= 0b00  -- Clock determined by fuses
-- OSCCON_PLLEN  = TRUE   -- PLL fixed enabled by configuration 
bits

enable_digital_io()   -- all pins digital

const byte ADC_CHANNEL = 2  -- potmeter connected to pin_AN3
ADCON0_CHS2 = TRUE   -- port 3 is analog input 
(default)
pin_AN2_direction = input
-- Step 2: Set VDD and VSS as Vref
FVRCON_FVREN = true
-- Step 3: Use Frc as ADC clock
ANSEL_ADCS = 0b011
const ADC_RSOURCE = 4_700   -- Input resistance: 4.7K 
potmeter
-- Now we can include the library
include adc
-- And initialize the whole with our parameters
adc_init()
var byte DIR
forever loop
DIR = adc_read_low_res(ADC_CHANNEL)
end loop

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/17f8ecc8-484d-4763-aa30-fa7b15395f64n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637830EB78526ED57F9D78CE6C69%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] Jallib - 1.7 Beta

2023-01-16 Thread Rob CJ

Hi Matt,

I will run the script and if needed I will update TORELEASE.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens Matthew Schinkel 

Verzonden: maandag 16 januari 2023 03:09
Aan: jallib 
Onderwerp: [jallib] Jallib - 1.7 Beta

Hi Everyone, It's time for a new release. I'll be creating a new beta in 2 
weeks.

Thanks for all the contributions over the past year.

Can someone please run totrelease.py and share the results?

Thanks,
Matt.


--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/a236bbdb-88b7-4c8e-b969-34050c4167ban%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16375A47D41F71DBB634C7ADE6C19%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PIC16F19176 use same function to check 2 input pins

2023-01-12 Thread Rob CJ

Hi Oliver,

Thanks for the feedback. I was not sure indeed.

Kind regards,

Rob


Van: 'Oliver Seitz' via jallib 
Verzonden: donderdag 12 januari 2023 19:29
Aan: jallib@googlegroups.com 
Onderwerp: Re: [jallib] PIC16F19176 use same function to check 2 input pins

Sorry, Rob, little mistake:

You need to check the PORTC register. The LATC register contains the output 
pattern, not the input state of the port pins.

Otherwise a good idea :-)

Greets,
Kiste

Am Donnerstag, 12. Januar 2023 um 19:11:43 MEZ hat flyway38 
 Folgendes geschrieben:


Hi Rob,

WOW, nice trick.
Will check if works.
Thank you very much.

Cheers,
FS

On Thursday, January 12, 2023 at 6:06:35 PM UTC rob...@hotmail.com wrote:
Hi Filipe,

I never tried this but here is a thought.

The pin on a specific port can be found in the LATx register, example below for 
portc this is LATC.

You find this in your device file for e.g. pin_C2
var volatile bitLATC_LATC2at LATC : 2
var volatile bitpin_C2at PORTC : 2

So if you have for example your buttons on port C you could pass a 'mask' as 
parameter to the procedure. Example below (not compiled):

function pin_active(byte in pin_mask) return bit
   return (LATC & pin_mask)
end function

So if you want to if test pin C1 is active (HIGH) or pin C7 is active (HIGH) 
you do:

if  pin_active(0b_0010) then
   -- Do something for bin C1
   end if
   if pin_active(0b1000_) then
  --  Do something for pin C7
end if

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: donderdag 12 januari 2023 12:07
Aan: jallib 
Onderwerp: [jallib] PIC16F19176 use same function to check 2 input pins

Hello,

Need help to use same function wich cheks for an input pin as a buttn.
But now need to implement new input pin as another button.
How to pass to that function which pin to read?
Can I use "byte in device" in its input parameters?
Thank you very much.

Kind regards,
Filipe Santos

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/f5fa42aa-c132-49d8-b5ae-5b141a9d927fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/404b1de4-c3cd-47b4-a12e-1f7dce577e91n%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/1273200153.331767.1673548195785%40mail.yahoo.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16372CFC54AA6E018BBB28A3E6FD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PIC16F19176 use same function to check 2 input pins

2023-01-12 Thread Rob CJ

Hi Filipe,

One correction. The return statement should be something like.
   return (LATC & pin_mask) != 0

Let me know if it works, I never tried it myself.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: donderdag 12 januari 2023 19:11
Aan: jallib 
Onderwerp: Re: [jallib] PIC16F19176 use same function to check 2 input pins

Hi Rob,

WOW, nice trick.
Will check if works.
Thank you very much.

Cheers,
FS

On Thursday, January 12, 2023 at 6:06:35 PM UTC rob...@hotmail.com wrote:
Hi Filipe,

I never tried this but here is a thought.

The pin on a specific port can be found in the LATx register, example below for 
portc this is LATC.

You find this in your device file for e.g. pin_C2
var volatile bitLATC_LATC2at LATC : 2
var volatile bitpin_C2at PORTC : 2

So if you have for example your buttons on port C you could pass a 'mask' as 
parameter to the procedure. Example below (not compiled):

function pin_active(byte in pin_mask) return bit
   return (LATC & pin_mask)
end function

So if you want to if test pin C1 is active (HIGH) or pin C7 is active (HIGH) 
you do:

if  pin_active(0b_0010) then
   -- Do something for bin C1
   end if
   if pin_active(0b1000_) then
  --  Do something for pin C7
end if

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: donderdag 12 januari 2023 12:07
Aan: jallib 
Onderwerp: [jallib] PIC16F19176 use same function to check 2 input pins

Hello,

Need help to use same function wich cheks for an input pin as a buttn.
But now need to implement new input pin as another button.
How to pass to that function which pin to read?
Can I use "byte in device" in its input parameters?
Thank you very much.

Kind regards,
Filipe Santos

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/f5fa42aa-c132-49d8-b5ae-5b141a9d927fn%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/404b1de4-c3cd-47b4-a12e-1f7dce577e91n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB1637E957AAEFEBD9A4E8E18FE6FD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PIC16F19176 use same function to check 2 input pins

2023-01-12 Thread Rob CJ

Hi Filipe,

I never tried this but here is a thought.

The pin on a specific port can be found in the LATx register, example below for 
portc this is LATC.

You find this in your device file for e.g. pin_C2
var volatile bitLATC_LATC2at LATC : 2
var volatile bitpin_C2at PORTC : 2

So if you have for example your buttons on port C you could pass a 'mask' as 
parameter to the procedure. Example below (not compiled):

function pin_active(byte in pin_mask) return bit
   return (LATC & pin_mask)
end function

So if you want to if test pin C1 is active (HIGH) or pin C7 is active (HIGH) 
you do:

if  pin_active(0b_0010) then
   -- Do something for bin C1
   end if
   if pin_active(0b1000_) then
  --  Do something for pin C7
end if

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: donderdag 12 januari 2023 12:07
Aan: jallib 
Onderwerp: [jallib] PIC16F19176 use same function to check 2 input pins

Hello,

Need help to use same function wich cheks for an input pin as a buttn.
But now need to implement new input pin as another button.
How to pass to that function which pin to read?
Can I use "byte in device" in its input parameters?
Thank you very much.

Kind regards,
Filipe Santos

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/f5fa42aa-c132-49d8-b5ae-5b141a9d927fn%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/GVXP195MB16376797E65DD89AC3F288C6E6FD9%40GVXP195MB1637.EURP195.PROD.OUTLOOK.COM.

Re: [jallib] PIC16F19176 rtc help

2023-01-12 Thread Rob CJ

Hi Filipe,

That timer library is using interrupts but if the code in your forever loop has 
a delay you will not benefit from it.

So what should be done is that the action you want to execute when the timer 
has an interrupt should be part of that timer0 interrupt routine and not in 
your forever loop. Some libraries - but not this one - have an option to call a 
user defined procedure when it is defined.

A quick - and dirty - fix is to make a local copy of this timer library and add 
your specific code to the procedure ISR() in timer0_isr_interval. Note that 
when you do that, your code must be fast since interrupt routine should be a 
short as possible.

An option would be to extend this library and call a user defined procedure 
from the timer interrupt if it was defined by the user.

Kind regards,

Rob


Van: jallib@googlegroups.com  namens flyway38 

Verzonden: donderdag 12 januari 2023 12:02
Aan: jallib 
Onderwerp: Re: [jallib] PIC16F19176 rtc help

Hello Rob,

Yes, am using this code:
-- This program uses the internal oscillator at 32 MHz.
pragma target clock32_000_000  -- oscillator frequency
pragma target OSC  OFF -- internal oscillator
pragma target RSTOSC   HFINT32 -- select 32 MHz
pragma target CLKOUTEN DISABLED-- no clock output
pragma target WDT  DISABLED-- watchdog
pragma target BROWNOUT DISABLED-- no brownout reset
pragma target FCMENDISABLED-- no clock monitoring
pragma target CSWENENABLED -- allow writing OSCCON1 NOSC and NDIV
pragma target LVP  ENABLED -- low voltage programming
pragma target MCLR INTERNAL-- internal reset
--
OSCFRQ_HFFRQ = 0b110   -- Fosc 32 -> 32 MHz
--OSCCON2 = 0x00   -- 32 MHz and no division
--
-- Enable weak pull up for all inputs.
--WPUA = 0b_
WPUB = 0b_
WPUC = 0b_
WPUD = 0b_
WPUE = 0b_

...

-- Timer0_isr_interval Lib
const DELAY_SLOTS = 1  -- support 2 delays at the same time
const word TIMER0_ISR_RATE = 1000  -- 1 kHz isr rate
include timer0_isr_interval
timer0_isr_init()  -- init timer0 isr
--
set_delay(0, 2_000)-- Init timer0 pointer
var word wTimeSync = 0 -- Init Time Sync clock

And inside FOREVER LOOP:
   -- Checking TIMER0 - Time Sync
   if (check_delay(0)) then
  wTimeSync = wTimeSync + 1
  --
  -- ticks (of 2s) on delay-slot 0
  set_delay(0, 2_000)
  --
 if (!LedAM & wTimeSync%10 == 0) then
 Krnl_CheckModem()
  end if
   end if

Problem is this code don't use interrupts.
So my var "wTimerSync" don't get updated when PIC is doing longer time 
consuming tasks...
Can you help?
Thank you.

Cheers,
FS
On Thursday, January 12, 2023 at 9:59:11 AM UTC rob...@hotmail.com wrote:
Hi Filipe,

In that case you could use a timer. Did you have a look at a timer library?

Met vriendelijke groet,
Rob Jansen

From: jal...@googlegroups.com  on behalf of flyway38 

Sent: Thursday, January 12, 2023 10:16:41 AM
To: jallib 
Subject: Re: [jallib] PIC16F19176 rtc help

Hi Rob and Vasile,

Thank you for your input.
My code is very big (and confuse) by now.
Anyways, only need an effective RTC to increment a variable, no matter what PIC 
is doing...
Problem is I have no experience using interrupts (software ones) with PICs.

Good point about that second oscillator. Remember now, my eyes crossing that 
info in the datasheet...
But, I think that will not need that. I don't need a precise RTC. My code will 
use a time base of 10seconds.
Problem is when PIC is doing some actions like reading SMSs, deleting SMSs, 
resetting modem, etc those actions take almost a minute, so I need 
interrupts to keep track of elapsed time.
Thank you very much.

Cheers,
FS

On Thursday, January 12, 2023 at 5:09:14 AM UTC vasile wrote:
Yep. If a secondary oscillator available, definitely yes for the RTC, except 
maybe for running at -20C where a good TCXO is expensive, using only one could 
be an option.
Apples with pears are still fruits, not very bad comparison. :)

On Wed, Jan 11, 2023 at 7:46 PM Rob CJ  wrote:
Hi Filipe,

It helps if you send your program otherwise we are comparing apples with pears.

There is another possibility. Your PIC has a secondary oscillator, meant for 
connecting a 32 kHz crystal. If you use that, you can make your own RTC and the 
only thing you need is a 32 kHz crystal and a small piece of software.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: woensdag 11 januari 2023 14:53
Aan: jallib 
Onderwerp: Re: [jallib] PIC16F19176 rtc help

Hello Vasile,

I think that have already tried that sample, but as said before, think i fall 
into some LIB errors...
Will check again, but maybe get stuck while adapting it to my PIC...
Will back here with results.
Thank you very much.

Cheers,
FS

On Wednesday, Janu

Re: [jallib] PIC16F19176 rtc help

2023-01-12 Thread Rob CJ

Hi Filipe,

In that case you could use a timer. Did you have a look at a timer library?

Met vriendelijke groet,
Rob Jansen

From: jallib@googlegroups.com  on behalf of flyway38 

Sent: Thursday, January 12, 2023 10:16:41 AM
To: jallib 
Subject: Re: [jallib] PIC16F19176 rtc help

Hi Rob and Vasile,

Thank you for your input.
My code is very big (and confuse) by now.
Anyways, only need an effective RTC to increment a variable, no matter what PIC 
is doing...
Problem is I have no experience using interrupts (software ones) with PICs.

Good point about that second oscillator. Remember now, my eyes crossing that 
info in the datasheet...
But, I think that will not need that. I don't need a precise RTC. My code will 
use a time base of 10seconds.
Problem is when PIC is doing some actions like reading SMSs, deleting SMSs, 
resetting modem, etc those actions take almost a minute, so I need 
interrupts to keep track of elapsed time.
Thank you very much.

Cheers,
FS

On Thursday, January 12, 2023 at 5:09:14 AM UTC vasile wrote:
Yep. If a secondary oscillator available, definitely yes for the RTC, except 
maybe for running at -20C where a good TCXO is expensive, using only one could 
be an option.
Apples with pears are still fruits, not very bad comparison. :)

On Wed, Jan 11, 2023 at 7:46 PM Rob CJ  wrote:
Hi Filipe,

It helps if you send your program otherwise we are comparing apples with pears.

There is another possibility. Your PIC has a secondary oscillator, meant for 
connecting a 32 kHz crystal. If you use that, you can make your own RTC and the 
only thing you need is a 32 kHz crystal and a small piece of software.

Kind regards,

Rob


Van: jal...@googlegroups.com  namens flyway38 

Verzonden: woensdag 11 januari 2023 14:53
Aan: jallib 
Onderwerp: Re: [jallib] PIC16F19176 rtc help

Hello Vasile,

I think that have already tried that sample, but as said before, think i fall 
into some LIB errors...
Will check again, but maybe get stuck while adapting it to my PIC...
Will back here with results.
Thank you very much.

Cheers,
FS

On Wednesday, January 11, 2023 at 3:50:33 AM UTC vasile wrote:
Hi Fellipe,
You will not like my ideea but any rtc can be implemented in any pic, much 
better than using an external RTC, by using Bresenham zero error algorithm.

It's in the sample and works perfect with all timers.

It's set to seconds but works down to 1ms for fast pics.
You have just to set a flag in the isr when time passed and reset it in the 
main after you have read it.

The only thing to care is the total lenght of your isr, including your own 
application which must be shorter than time genetated (aka 1 second or shorter).


On Tue 10 Jan 2023, 9:25 PM flyway38  namens flyway38 

Verzonden: dinsdag 10 januari 2023 19:04
Aan: jallib 
Onderwerp: [jallib] PIC16F19176 rtc help

Hello all,

Need help on coding for an rtc for the 16F19176.
Have tried many samples with no luck. They get alot of failures, like not 
defined terms...
Need to implement a simple RTC code to keep track of time even if PIC is 
handling "closed loop" routines, like reading Comm Port or resetting the gsm 
modem, etc...
Need these routines to get interrupted, and finished after RTC updates time.
It would be a very fast code, only to increment a variable.
Need some sample code adapted for this PIC, please.
Thank you

Kind regards,
Filipe Santos

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/4b03768d-331b-4a4c-aa10-afbf73fc952cn%40googlegroups.com<https://groups.google.com/d/msgid/jallib/4b03768d-331b-4a4c-aa10-afbf73fc952cn%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/792ae118-9ffe-496b-b214-9ef697d45133n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/792ae118-9ffe-496b-b214-9ef697d45133n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jallib+un...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jallib/2cd70652-2a40-4954-bfef-1b9ec4730363n%40googlegroups.com<https://groups.google.com/d/msgid/jallib/2cd70652-2a40-4954-bfef-1b9ec4730363n%40googlegroups.com?utm_medium=email_source=footer>.

--
You received this message because you are subscribed

1 2 3 4 5 >

1 - 100 of 470 matches

Mail list logo