Hi Wouter,


> Very good work!
>
> To make feedback easier, could you provide a printable version that has
> line numbers in the (left) margin?
>

I'm afraid it may not be possible... Documentation is written using DITA (
http://dita.xml.org/ and http://dita-ot.sourceforge.net/), and XSL
stylesheets to produce PDF (and HTML). This would need quite complicated XSL
rules, which probably go way too far from my very basic knowledge...

Maybe pointing to DITA source files would do the trick ?

     http://code.google.com/p/jallib/source/browse/trunk/doc/dita/tutorials/



Cheers,
Seb


> --
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: www.voti.nl/hvu
>
>
>



--
Sébastien Lelong
http://www.sirloon.net
http://sirbot.org


[Non-text portions of this message have been removed]

>> To make feedback easier, could you provide a printable version that has
>> line numbers in the (left) margin?
>>
>
> I'm afraid it may not be possible...

A next-best option is to have some kind of ruler at the side,
referencing for instance millimeters? This can be a static image.

--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu

Can you please compress the project using jaledit backup and send it for
testing.

Sunish
--- In jallist@yahoogroups.com, "Vasile" <vsurducan@...> wrote:
>
> Hi
>
> This message is for the IDE developers.
>
> Both Picshell and jalledit locks when trying to compile an initial version of
JalV2 code (non jallib structured ).
>
> Picshell reports in dos windows:
> traceball (most recent call last):
> File "PicShell py:" line 612, in OnCompile
> File "picshell/ui/UIManager.pyc", line 255, incompileProject
> File "picshell/engine/core/pics.pyc/, line46391, in PicFactory
> Keyerror: "pic16F876A"
>
> Jaledit hangs either on a blank screen or in a normal screen after
compilation.
>
>  thx,
> Vasile
>

I have added my FAT32 library to the Jallib SVN

library file:
http://jallib.googlecode.com/svn/trunk/include/filesystem/fat32.jal
sample file:
http://jallib.googlecode.com/svn/trunk/sample/18f452_fat32_sd_card.jal

You will also need the recent jallib-bee package from:
http://code.google.com/p/jallib/downloads/list

If you got your SD card to work in your circuit, you may use this. It is still
in testing and may have bugs, let me know if it works for you, please give me
some feedback.

If you wish to save some memory, you can reduce the size of the following
constands within fat32.jal

const word FAT32_FILES_MAX = 100 -- max files per dir listing
const BYTE FAT32_FILENAME_SIZE = 100 - max file name size
const FAT32_DIR_FRAGMENTS_TO_ALLOW = 10
const FAT32_FILE_FRAGMENTS_TO_ALLOW = 10

I will later add support for an external memory source so you can save more PIC
memory.

Matt.

Thanks- it works well


Regards,
Michael

--- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@...> wrote:
>
> You can also change it so if the user is holding the button, it will slowly
increment:
>
> forever loop
>
> while up ; loop untill button is released
>
>   if volume == 0xff then ; 0xFF is the maximum value of a var byte
>     volume = 0xff
>   else
>     volume = volume + 1
>   end if
>   delay_100ms (5) -- choose how fast volume increments.
>
> loop
>
> -- main program here
>
> end loop
>
>
>
> Matt.
>
> --- In jallist@yahoogroups.com, Andrea Campagnolo <campagnoloandrea@> wrote:
> >
> > Something like this I suppose....
> >
> > if up then
> > if volume == 0xff then ; 0xFF is the maximum value of a var byte
> > volume = volume
> > else
> > volume = volume + 1
> > end if
> > while up ; loop untill button is released
> > loop
> > delay_100ms (1)
> > end loop
> > end if
> >
> >
> >
> >
> >   _____
> >
> > Van: jallist@yahoogroups.com [mailto:jallist@yahoogroups.com] Namens
> > matthewschinkel
> > Verzonden: zaterdag 21 november 2009 21:16
> > Aan: jallist@yahoogroups.com
> > Onderwerp: [jallist] Re: Simple push-button interface question
> >
> >
> >
> >
> > You have to increment your volume before the while loop so when you press
> > the button you see the volume go up (not when it is released). It's more
> > user friendly.
> >
> > I put a 100ms delay within the while statement to make it a "bounch-less
> > switch" so you don't accidently increment twice or more. Also, it is hard to
> > press a button for less then 100ms.
> >
> > Matt.
> >
> > --- In jallist@yahoogroups <mailto:jallist%40yahoogroups.com> .com,
> > "campagnoloandrea" <campagnoloandrea@> wrote:
> > >
> > >
> > >
> > > Hi try this:
> > >
> > > if up then
> > > while up ; loop untill button is released
> > > loop
> > > delay_10us (1)
> > > end loop
> > > volume = volume + 1
> > > Else ; This line is not necessary
> > > volume = volume ; This line is not necessary
> > > end if
> > >
> > >
> > > The above code will keep incrementing Volume untill it's maximum value and
> > the drop suddenly to 0.
> > > I don't know what your application of the code is but if you want the
> > volume to stay at maximum level once it reaches its maximum value then you
> > need to replace the line "volume = volume + 1" with
> > >
> > > if volume == 0xff then ; 0xFF is the maximum value of a var byte
> > > volume = volume
> > > else
> > > volume = volume + 1
> > > end if
> > >
> > > So your code will look something like this:
> > >
> > > if up then
> > > while up ; loop untill button is released
> > > loop
> > > delay_10us (1)
> > > end loop
> > > if volume == 0xff then ; 0xFF is the maximum value of a var byte
> > > volume = volume
> > > else
> > > volume = volume + 1
> > > end if
> > > end if
> > >
> > >
> > > Let us know if it works.
> > >
> >
> >
> >
> >
> >
> > Geen virus gevonden in het binnenkomende-bericht.
> > Gecontroleerd door AVG - www.avg.com
> > Versie: 8.5.425 / Virusdatabase: 270.14.76/2517 - datum van uitgifte:
> > 11/21/09 07:47:00
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

good evening together,

does anyone know a program which can display values, i send by sr232 to
my pc? with MICterm i can only display values <= 255! (or did i make a
mistake?) i need to see values<=65025 (word variable)! can anyone help?

thank you and best regards,

Rappl

If you are using jallib, you can use the library format.jal

var word value = 65025
format_word_dec(serial_hw_data,value,6,0)

It will send an ascii string "65025" via serial port.

Matt

--- In jallist@yahoogroups.com, "Rappl" <rappl@...> wrote:
>
>
> good evening together,
>
> does anyone know a program which can display values, i send by sr232 to
> my pc? with MICterm i can only display values <= 255! (or did i make a
> mistake?) i need to see values<=65025 (word variable)! can anyone help?
>
> thank you and best regards,
>
> Rappl
>

>does anyone know a program which can display values, i send by sr232 to
>my pc? with MICterm i can only display values <= 255! (or did i make a
>mistake?) i need to see values<=65025 (word variable)! can anyone help?

RS232 connections use bytes, so you cannot send values larger than 255. If
you need to send word values you can convert them to a string first, and
then send them character by character.

Have fun,
Bert

www.vandam.tk

thanks for your fast answer!

i have all the jallib libraries, but i'm working with bert van dams libraries (i
started to learn jal by reading his books), and i have the feeling that this
libraries don't like each other! ;)
perhaps I should switch compleately to jallib libraries (these are much more
extensive!?), but then I have to sart at nearly zero again!?

Rappl

--- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@...> wrote:
>
> If you are using jallib, you can use the library format.jal
>
> var word value = 65025
> format_word_dec(serial_hw_data,value,6,0)
>
> It will send an ascii string "65025" via serial port.
>
> Matt
>
> --- In jallist@yahoogroups.com, "Rappl" <rappl@> wrote:
> >
> >
> > good evening together,
> >
> > does anyone know a program which can display values, i send by sr232 to
> > my pc? with MICterm i can only display values <= 255! (or did i make a
> > mistake?) i need to see values<=65025 (word variable)! can anyone help?
> >
> > thank you and best regards,
> >
> > Rappl
> >
>

this is quite logic...
...if you know what you have to do! ;)
but finally i understood this principle!

alternatively i also found an other way! I added both variables manual:

var word timer

timer = ( tmr1H * 256 ) + tmr1L

regards,
Rappl

--- In jallist@yahoogroups.com, "Gordon Williams" <gwilliams@...> wrote:
>
> Hi,
>
> What I do is create a 2 byte variable and map a 2 byte array on top
>
> var byte*2 myTimer
> var byte myTimerLH[2] at myTimer
>
> myTimerLH[0] = CCPR1L  ; tranfer low byte
> myTimerLH[1] = CCPR1H  ; transfer high byte
>
> myTimer can be used for whatever you want as a 2 byte result.
>
> Regards,
>
> Gordon Williams

I'm not sure what solution bert has for this, but you could also just send
multiple hex values via the serial port:

-- send dword via serial port
procedure send_dword(dword in dval1) is
   var byte dval2[4] at dval1
   serial_hw_write (dval2[3])
   serial_hw_write (dval2[2])
   serial_hw_write (dval2[1])
   serial_hw_write (dval2[0])
end procedure

send_dword(65025)


on your screen you should see: 00 00 FE 01

I believe jallib has more libraries, bert may have different libraries then we
have. You can browse through the jallib pack to see what we have. Bert's libs &
jallib libs do not mix well although it is possible if you know what your doing.

Matt.

--- In jallist@yahoogroups.com, "Rappl" <rappl@...> wrote:
>
> thanks for your fast answer!
>
> i have all the jallib libraries, but i'm working with bert van dams libraries
(i started to learn jal by reading his books), and i have the feeling that this
libraries don't like each other! ;)
> perhaps I should switch compleately to jallib libraries (these are much more
extensive!?), but then I have to sart at nearly zero again!?
>
> Rappl
>
> --- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@> wrote:
> >
> > If you are using jallib, you can use the library format.jal
> >
> > var word value = 65025
> > format_word_dec(serial_hw_data,value,6,0)
> >
> > It will send an ascii string "65025" via serial port.
> >
> > Matt
> >
> > --- In jallist@yahoogroups.com, "Rappl" <rappl@> wrote:
> > >
> > >
> > > good evening together,
> > >
> > > does anyone know a program which can display values, i send by sr232 to
> > > my pc? with MICterm i can only display values <= 255! (or did i make a
> > > mistake?) i need to see values<=65025 (word variable)! can anyone help?
> > >
> > > thank you and best regards,
> > >
> > > Rappl
> > >
> >
>

I understand what you want to do! And I know what a string should do! But I
can't find anything about strings in JAL, so I don't know how I can get this
single characters of the decimal value of my variable!? A string isn't the same
as an array!? Or is it?



>RS232 connections use bytes, so you cannot send values larger than >255. If you
need to send word values you can convert them to a >string first, and then send
them character by character.

>Have fun,
>Bert

>www.vandam.tk

On 12 Nov 2009, at 06:28 , Patrick Froucht wrote:

> With the old one and it's RS232 interface, perhaps it's a problem
> of the
> voltage value for the RS232 signals. With the standard, output voltage
> should be +/- 15V.
> Some computers give +/- 7V and other barely reach the negative range.
> And if its at the limit of the voltage sense for the interface circuit
> you can get random successes.

This could very well be true. But One would imagine no comms at all,
not a weird 70% failure rate. For one sucessfull programming of a
PIC, the RS232 signal changes polarity about 50.000 times, with no
error. How come this works some of the time but not all? I suspect
the OS. If this takes control momentarily away from the port, comms
fails. I know for a fact that serial ports under Windoze are
neglected and treated like dirt.

> For newer computers with USB interface, Wouter says for Wisp648
> "serial
> interface, also works with off-the-shelf usb-to-serial converters"
> There is also some question: Wouter did not tested it with all the
> converters and feed the computer USB interface enough power to
> drive the
> converter? Sometime the USB power can be adjusted to save battery.

Yes, but the same serial converter gave wildly different results on
three computers. On one it works 99.95% of the time, on another only
10% on the time and yet another 95% of the time.

USB power is negotiated immediately after inserting the plug. Surely
this is the same for all PC's. Also, Wisp648 was fed externally.

I'll try more configurations: I need to bring in an external laptop
to a company for programming PICs. I bought a PICkit as well. This
has a HID USB interface, so most USB bugs should be smoothed out.

<rant>
Can you believe an R&D department where the PIC programming guy is
NOT ALLOWED to install programs on his PC? This is the same company
where the electronics guy is NOT ALLOWED to order parts @ Farnell.
This has to be done by the purchasing department, down to a single
0804 reisistor. So he sends me the order by mail, I order @ Farnell
and send it by post the next day. This is three times as fast as the
usual method.
</rant>




>
> Patrick
>
> Eur van Andel a écrit :
>>
>> Hi
>>
>> I've programmed PIC for years, mostly with the Wisp628 and Windoze
>> 98, but also under FreeBSD. This worked 99.9% of the time. When it
>> didn't work, the cause was things like:
>>
>> impatiently switching on the LCD backlight or other large current
>> drawing peripherals (while programming)
>> a 230V AC cable acros the board which is switching an inductive load
>>
>> and other nasty EMF-generating events.
>>
>> Recently, I switched to a Wisp648 and ran that with a FTDI-based USB-
>> to-serial converter from Mac OS X 10.4, a.k.a. Tiger. Experience same
>> as above, with no EMF the success rate is above 99.8%.
>>
>> Recently, I had to program some PICs in the field, so I snatched my
>> wifes MacBookPro (Leopard, 10.5) and installed the same drivers for
>> the USB-serial-cable. Succes rate: 10%! There was no difference
>> between Wisp648 and Wisp628.
>>
>> I then tried an old XP laptop and used the serial port. Success rate:
>> 30%. Still not good enough.
>>
>> I then tried the serial-to-usb cable on the XP laptop. This worked
>> reasonably: 95% of the time.
>>
>> This is the *same* cable with the *same* xwisp.py Python script and
>> the *same* wisp648 programmer. I switched back and forth between
>> laptop and MBP and the results were the same every time (10% vs
>> 95%). My G5 (Tiger, 10.4) had no problem.
>>
>> So it can't be the cable, it can't be the xwisp script, it can't be
>> the programmer?
>>
>> I can't believe the OS matters that much for serial or USB
>> communication?
>>
>> ---
>> ir EE van Andel eur@... <mailto:eur%40fiwihex.nl>
>> http://www.fiwihex.nl <http://www.fiwihex.nl>
>> Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
>> tel+31-546-491106 fax+31-546-491107
>>
>> [Non-text portions of this message have been removed]
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

---
ir EE van Andel eur@...  http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107




[Non-text portions of this message have been removed]

Hi Rappl,

JAL does not have strings like C++ has, but does has byte arrays, which can
contain a sequence of chars. print.jal has procedure print_string() to print
such a string to any device. Bert has (amongst others) serial_hw_printf().

And on compatibility between Bert's starterpack and jallib. Berts starterpack is
based on the JAL device files of a few years ago.
Jallib has much more device files and these device files have stricter naming
conventions, in general the same like the datasheet. Jallib libraries of course
use this naming and as a result, can't be compatible with the starterpack...

Joep


--- In jallist@yahoogroups.com, "Rappl" <rappl@...> wrote:
>
> I understand what you want to do! And I know what a string should do! But I
can't find anything about strings in JAL, so I don't know how I can get this
single characters of the decimal value of my variable!? A string isn't the same
as an array!? Or is it?
>
>
>
> >RS232 connections use bytes, so you cannot send values larger than >255. If
you need to send word values you can convert them to a >string first, and then
send them character by character.
>
> >Have fun,
> >Bert
>
> >www.vandam.tk
>

*If* your method works, it will likely be longer and slower.  You should
check the asm created for the lengths of each method.

Regards,

Gordon Williams

----- Original Message -----
From: "Rappl" <rappl@...>
To: <jallist@yahoogroups.com>
Sent: Wednesday, November 25, 2009 1:17 PM
Subject: [jallist] Re: transfer tmr1L byte and tmr1H byte in only one word
variable


> this is quite logic...
> ...if you know what you have to do! ;)
> but finally i understood this principle!
>
> alternatively i also found an other way! I added both variables manual:
>
> var word timer
>
> timer = ( tmr1H * 256 ) + tmr1L
>
> regards,
> Rappl
>
> --- In jallist@yahoogroups.com, "Gordon Williams" <gwilliams@...> wrote:
> >
> > Hi,
> >
> > What I do is create a 2 byte variable and map a 2 byte array on top
> >
> > var byte*2 myTimer
> > var byte myTimerLH[2] at myTimer
> >
> > myTimerLH[0] = CCPR1L  ; tranfer low byte
> > myTimerLH[1] = CCPR1H  ; transfer high byte
> >
> > myTimer can be used for whatever you want as a 2 byte result.
> >
> > Regards,
> >
> > Gordon Williams
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

My SD Card tutorial is finnished, you can find it on the jallib website:

http://justanotherlanguage.org/content/tutorial_sd_card

Please send me your feedback.

Matt.

--- In jallist@yahoogroups.com, Eur van Andel <eur@...> wrote:
>

> <rant>
> Can you believe an R&D department where the PIC programming guy is
> NOT ALLOWED to install programs on his PC? This is the same company
> where the electronics guy is NOT ALLOWED to order parts @ Farnell.
> This has to be done by the purchasing department, down to a single
> 0804 reisistor. So he sends me the order by mail, I order @ Farnell
> and send it by post the next day. This is three times as fast as the
> usual method.
> </rant>


Easily, I work for a major telephone company that recently merged with another
major telephone company, prior to the merger (and possibly now since I haven't
tried it), I could not only not install software to my computer, I could not
even save a file I created to the hard drive, it had to be saved on a network
drive so it could be scanned for viruses and worms to "protect the PC" and I
suppose the network(but I'm saving it on a network drive ??), yet I have access
to switches and SONET rings and can take out tens of thousands of customers with
just a few keystrokes. Corporate paranoria over IP and money. Must protect or
astronomical management bonuses from the people who really make the company
profitable.

Mike

Hi Matt,
Nice work! I first have to change from BB to LIB then I'll try
Thanks
Hans

--- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@...> wrote:
>
> My SD Card tutorial is finnished, you can find it on the jallib website:
>
> http://justanotherlanguage.org/content/tutorial_sd_card
>
> Please send me your feedback.
>
> Matt.
>

Hi,
 
I seem to have come across a problem where indexing a "long table" array of word
const's using an index variable either resets or gives wrong data.
 
In my example, I have an array of 252 word's:
const word mylongarray[] = { ... }
I can reference fine like so:
var word w1 = mylongarray[0]    -- works
var word w2 = mylongarray[251] -- works
 
However, this gives wrong value for w3
var byte id3 = 0
var word w3 = mylongarray[id3] -- wrong value
and indexing with any other id3 value seems to reset the pic
id3 = 1
w3 = mylongarray[id3] -- resets
id3 = 251
w3 = mylongarray[id3] -- resets
 
Looking at the assembly, I can see it makes 2 calls, to retrieve each of the 8
bytes
when an index variable is used, otherwise it's inlined.
l__lookup_mylongarray
                               movwf    v__pclath
                               movf     v__pic_loop,w
                               addlw    9
                               btfsc    v__status, v__c
                               incf     v__pclath,f
                               movwf    v__pcl
                               retlw    148
                               retlw    3
                               retlw    152
                               retlw    3
                               ....
;          var byte id3 = 0
                               datalo_clr v_id3
                               clrf     v_id3
;          var word w3 = mylongarray[id3] -- bad value
                               bcf      v__status, v__c
                               rlf      v_id3,w
                               movwf    v____temp_24
                               movf     v____temp_24,w
                               movwf    v__pic_loop
                               movlw    0
                               call     l__lookup_mylongarray
                               datalo_clr v_w3
                               movwf    v_w3
                               movlw    1
                               addwf    v__pic_loop,w
                               call     l__lookup_mylongarray
                               datalo_clr v_w3
                               movwf    v_w3+1
 
Using JALv2, PIC16F88
 
Thanks,
Carlos




[Non-text portions of this message have been removed]

Matt,

please check the circuit image (
http://justanotherlanguage.org/sites/default/files/sd_card_schematic.jpg). I
think the 10uF cap near the SD is inverted !!!

Hugs,
Fabiano

2009/11/25 matthewschinkel <matthewschinkel@...>

>
>
> My SD Card tutorial is finnished, you can find it on the jallib website:
>
> http://justanotherlanguage.org/content/tutorial_sd_card
>
> Please send me your feedback.
>
> Matt.
>
>
>



--
Fabiano Pires
Profissional Linux LPIC-2
http://pragasdigitais.blogspot.com/
Livrando você da escória da Internet!


[Non-text portions of this message have been removed]

[Default] On Sun, 22 Nov 2009 20:48:16 -0000, "Rappl"
<rappl@...> wrote:

>in the moment where the measurement must stop, the value of "counter" is
>transfered to "istwert"!
>
>counter = istwert

Careful with this. While it looks like a single operation, JAL must
compile it as two separate reads, one from TMR1H and one from TMR1L.
If the counter is running while you read it, you risk getting an
incorrect result because the timer has advanced between the two reads.

There are several ways to solve the problem:

- Stop the timer before you read it.
- Use the Capture/Compare module.
- Read twice and evaluate both results to see if something has rolled
over.
--
Helge

Hi Matt,
I have tested the sample file 16877_sd_card on a 16F877 (changed the include)
and the program stops after the write 0x66,0x22 to sector 20. so there is no
reading. Any idea?
I use a 2GB Emtec card fresh formatted on fat32.
A little remark ; on page 2 the setting of 3800 baudtrate must be 38400
Hans

--- In jallist@yahoogroups.com, Fabiano Pires <fabiano.pires@...> wrote:
>
> Matt,
>
> please check the circuit image (
> http://justanotherlanguage.org/sites/default/files/sd_card_schematic.jpg). I
> think the 10uF cap near the SD is inverted !!!
>
> Hugs,
> Fabiano
>
> 2009/11/25 matthewschinkel <matthewschinkel@...>
>
> >
> >
> > My SD Card tutorial is finnished, you can find it on the jallib website:
> >
> > http://justanotherlanguage.org/content/tutorial_sd_card
> >
> > Please send me your feedback.
> >
> > Matt.
> >
> >
> >
>
>
>
> --
> Fabiano Pires
> Profissional Linux LPIC-2
> http://pragasdigitais.blogspot.com/
> Livrando você da escória da Internet!
>
>
> [Non-text portions of this message have been removed]
>

Hi Matt,
I have changed the write to sector 10 (20 is to big for 2GB?)and then it goes
but I only see 00 and FF
Hans

--- In jallist@yahoogroups.com, "Hansv" <hanzeman@...> wrote:
>
> Hi Matt,
> I have tested the sample file 16877_sd_card on a 16F877 (changed the include)
and the program stops after the write 0x66,0x22 to sector 20. so there is no
reading. Any idea?
> I use a 2GB Emtec card fresh formatted on fat32.
> A little remark ; on page 2 the setting of 3800 baudtrate must be 38400
> Hans
>
> --- In jallist@yahoogroups.com, Fabiano Pires <fabiano.pires@> wrote:
> >
> > Matt,
> >
> > please check the circuit image (
> > http://justanotherlanguage.org/sites/default/files/sd_card_schematic.jpg). I
> > think the 10uF cap near the SD is inverted !!!
> >
> > Hugs,
> > Fabiano
> >
> > 2009/11/25 matthewschinkel <matthewschinkel@>
> >
> > >
> > >
> > > My SD Card tutorial is finnished, you can find it on the jallib website:
> > >
> > > http://justanotherlanguage.org/content/tutorial_sd_card
> > >
> > > Please send me your feedback.
> > >
> > > Matt.
> > >
> > >
> > >
> >
> >
> >
> > --
> > Fabiano Pires
> > Profissional Linux LPIC-2
> > http://pragasdigitais.blogspot.com/
> > Livrando você da escória da Internet!
> >
> >
> > [Non-text portions of this message have been removed]
> >
>

This was right in time for me! I used the info to change from BB to lib. Just a
little remark: I spent a lot of time getting the wisp into the system, a picture
is there but I missed the installation example. Anyway it's a great help, thanks
Hans

--- In jallist@yahoogroups.com, Wouter van Ooijen <wouter@...> wrote:
>
> >> To make feedback easier, could you provide a printable version that has
> >> line numbers in the (left) margin?
> >>
> >
> > I'm afraid it may not be possible...
>
> A next-best option is to have some kind of ruler at the side,
> referencing for instance millimeters? This can be a static image.
>
> --
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: www.voti.nl/hvu
>

Hi Matt,

Your program/library  works for me with a 16f877. However, the pins are not
defined which may not be clear to other users (unless they  are declared
somewhere else) . My settings are:

-- setup spi
include spi_master_hw         -- includes the spi library
-- define spi inputs/outputs



  var bit pin_sck is pin_c3
  var bit pin_sdi is pin_c4
  var bit pin_sdo is pin_c5
  var bit pin_ss is pin_c2
  var bit pin_sck_direction is pin_c3_direction
  var bit pin_sdi_direction is pin_c4_direction
  var bit pin_sdo_direction is pin_c5_direction
  var bit pin_ss_direction is pin_c2_direction -- use any available pin


pin_sdi_direction = input    -- spi input
pin_sdo_direction = output   -- spi output
pin_sck_direction = output   -- spi clock
-- spi chip select pin

Looking forward to the next chapter!

cheers

Colin


--- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@...> wrote:
>
> My SD Card tutorial is finnished, you can find it on the jallib website:
>
> http://justanotherlanguage.org/content/tutorial_sd_card
>
> Please send me your feedback.
>
> Matt.
>

Hi Matt,

I should have added that I use a 1GB Kingston card- this is the largest that I
have.

Colin

--- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@...> wrote:
>
> My SD Card tutorial is finnished, you can find it on the jallib website:
>
> http://justanotherlanguage.org/content/tutorial_sd_card
>
> Please send me your feedback.
>
> Matt.
>

Hi Colin,
These are all defined in my 16F877 and 16F877a lib. I have all libs replaced by
the recent jallib-bee package. Could that be a reason of my malfunction?
Hans

--- In jallist@yahoogroups.com, "colin.tallis" <colin.tallis@...> wrote:
>
>
> Hi Matt,
>
> Your program/library  works for me with a 16f877. However, the pins are not
defined which may not be clear to other users (unless they  are declared
somewhere else) . My settings are:
>
> -- setup spi
> include spi_master_hw         -- includes the spi library
> -- define spi inputs/outputs
>
>
>
>  var bit pin_sck is pin_c3
>  var bit pin_sdi is pin_c4
>  var bit pin_sdo is pin_c5
>  var bit pin_ss is pin_c2
>  var bit pin_sck_direction is pin_c3_direction
>  var bit pin_sdi_direction is pin_c4_direction
>  var bit pin_sdo_direction is pin_c5_direction
>  var bit pin_ss_direction is pin_c2_direction -- use any available pin
>
>
> pin_sdi_direction = input    -- spi input
> pin_sdo_direction = output   -- spi output
> pin_sck_direction = output   -- spi clock
> -- spi chip select pin
>
> Looking forward to the next chapter!
>
> cheers
>
> Colin
>
>
> --- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@> wrote:
> >
> > My SD Card tutorial is finnished, you can find it on the jallib website:
> >
> > http://justanotherlanguage.org/content/tutorial_sd_card
> >
> > Please send me your feedback.
> >
> > Matt.
> >
>

Hans, I'll check those errors on the tutorial, let me know if you find any
others.

I'll test a few more types of sd cards, I have no idea why some cards require
the 10ms delay or why yours does not work at all after writing, what if you add
a larger delay? You have worked with SD cards before, did you every try writing
before with your old code?

Colin, you don't need to define those pins since the library uses the SPI
hardware pins and they are defined in the device file 16f877.jal . Are you
getting an error if you do not define the pins? I will add a note to the
tutorial on this.

Matt.

--- In jallist@yahoogroups.com, "Hansv" <hanzeman@...> wrote:
>
> Hi Colin,
> These are all defined in my 16F877 and 16F877a lib. I have all libs replaced
by the recent jallib-bee package. Could that be a reason of my malfunction?
> Hans
>
> --- In jallist@yahoogroups.com, "colin.tallis" <colin.tallis@> wrote:
> >
> >
> > Hi Matt,
> >
> > Your program/library  works for me with a 16f877. However, the pins are not
defined which may not be clear to other users (unless they  are declared
somewhere else) . My settings are:
> >
> > -- setup spi
> > include spi_master_hw         -- includes the spi library
> > -- define spi inputs/outputs
> >
> >
> >
> >  var bit pin_sck is pin_c3
> >  var bit pin_sdi is pin_c4
> >  var bit pin_sdo is pin_c5
> >  var bit pin_ss is pin_c2
> >  var bit pin_sck_direction is pin_c3_direction
> >  var bit pin_sdi_direction is pin_c4_direction
> >  var bit pin_sdo_direction is pin_c5_direction
> >  var bit pin_ss_direction is pin_c2_direction -- use any available pin
> >
> >
> > pin_sdi_direction = input    -- spi input
> > pin_sdo_direction = output   -- spi output
> > pin_sck_direction = output   -- spi clock
> > -- spi chip select pin
> >
> > Looking forward to the next chapter!
> >
> > cheers
> >
> > Colin
> >
> >
> > --- In jallist@yahoogroups.com, "matthewschinkel" <matthewschinkel@> wrote:
> > >
> > > My SD Card tutorial is finnished, you can find it on the jallib website:
> > >
> > > http://justanotherlanguage.org/content/tutorial_sd_card
> > >
> > > Please send me your feedback.
> > >
> > > Matt.
> > >
> >
>

matthewschinkel wrote:
> Hans, I'll check those errors on the tutorial, let me know if you find any
others.
>
> I'll test a few more types of sd cards, I have no idea why some cards require
the 10ms delay or why yours does not work at all after writing, what if you add
a larger delay? You have worked with SD cards before, did you every try writing
before with your old code?
>
> Colin, you don't need to define those pins since the library uses the SPI
hardware pins and they are defined in the device file 16f877.jal . Are you
getting an error if you do not define the pins? I will add a note to the
tutorial on this.
>
> Matt.
>

Matt

    Found a typo in your Maxim RS232 article.  To check the wires on the
DB9 connector you say to use a millimeter instate of a multimeter.

Wayne

Thanks, it will be fixed my spell checker must have changed it lol.

Matt.

--- In jallist@yahoogroups.com, Wayne <linuxone@...> wrote:
>
> matthewschinkel wrote:
> > Hans, I'll check those errors on the tutorial, let me know if you find any
others.
> >
> > I'll test a few more types of sd cards, I have no idea why some cards
require the 10ms delay or why yours does not work at all after writing, what if
you add a larger delay? You have worked with SD cards before, did you every try
writing before with your old code?
> >
> > Colin, you don't need to define those pins since the library uses the SPI
hardware pins and they are defined in the device file 16f877.jal . Are you
getting an error if you do not define the pins? I will add a note to the
tutorial on this.
> >
> > Matt.
> >
>
> Matt
>
>    Found a typo in your Maxim RS232 article.  To check the wires on the
> DB9 connector you say to use a millimeter instate of a multimeter.
>
> Wayne
>