Hi Sunish,

Thanks for the info. So it is also in the original version? I am currently 
working on my 'Jaluino One' project that I want to finish first but I had a 
quick look at the library 'usb_keyboard.jal' and saw the following that I 
do not understand but might explain the issue.

You see this:

   USB_KEYBOARD_KEY_SPACE,                                  ; 0x20 space
   USB_KEYBOARD_KEY_1   | ASCII_USB_SHIFT,                  ; 0x21 char ! 
   0x34                 | ASCII_USB_SHIFT,                  ; 0x22 char "
   USB_KEYBOARD_KEY_3   | ASCII_USB_SHIFT,                  ; 0x23 char #
   USB_KEYBOARD_KEY_4   | ASCII_USB_SHIFT,                  ; 0x24 char $
   USB_KEYBOARD_KEY_5   | ASCII_USB_SHIFT,                  ; 0x25 char %
   USB_KEYBOARD_KEY_6   | ASCII_USB_SHIFT,                  ; 0x26 char &
   0x34,                                                    ; 0x27 char '
   USB_KEYBOARD_KEY_9   | ASCII_USB_SHIFT,                  ; 0x28 char (
   USB_KEYBOARD_KEY_0   | ASCII_USB_SHIFT,                  ; 0x29 char )
   USB_KEYBOARD_KEY_8   | ASCII_USB_SHIFT,                  ; 0x2A char *
   0x2E                 | ASCII_USB_SHIFT,                  ; 0x2B char +
   0x36,                                                    ; 0x2C char ,
   0x2D,                                                    ; 0x2D char -
   0x37,                                                    ; 0x2E char .
   0x38,                                                    ; 0x2F char /

I do not understand why there is no USB_KEYBOARD_KEY_2 which should have 
the value 0x40 or "@" but it could explain the issue you have.

Kind regards,

Rob




On Monday, February 25, 2019 at 6:01:10 AM UTC+1, Sunish Issac wrote:
>
> Hello Rob,
> The problem is there in 18F13k series too!. Its easily reproducible, try 
> printing a string through keyboard from an array having @. It gets replaced 
> by #.
>
> Please find attached the JAL file
>
> Sunish
>
> On Mon, Feb 25, 2019 at 2:10 AM Sunish Issac <[email protected]> wrote:
>
>> Hello Rob,
>> I was able to compile for 18f13k50 (same as 14k50), there are no 
>> warnings, but I couldn't test the output as my test board uses type b cable 
>> which I don't have at the moment, will test tomorrow and update.
>>
>> Kind regards,
>> Sunish
>>
>>
>> On Sun, Feb 24, 2019 at 10:04 PM Rob Jansen <[email protected]> wrote:
>>
>>> Hi Sunish,
>>>
>>> This sample gives a warning that I do not yet understand. I am not sure 
>>> if the warning has a relation with the problem you mentioned.
>>>
>>> Do you now if the same problem also occurs with the 18F14K50 sample 
>>> program?
>>>
>>> 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 [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to