Matrix user forums

Hello,

Here is a program you can try.

Connect a combo board to Ports A and B or an BL0169 LCD to Port B and connect the RFID board to Port C only.

Hi Jan,

Thanks for letting us know and glad it's working for you.

It looks perfect your solution, but I could not find it.

The generic Keypad component is no longer shown in a component category and is only available now via the Search.

Hi Brian, I find you can be doing the most complicated thing in the world and something stupid and silly will always find a way to creep in and trip you up :wink: Its just the way of things. The number of times I have rewritten code because I assumed it was flawed when really it was down to a basic ...

Thanks for the photo Jan, I've created a new component for you and uploaded to the update system. Just change "Files in use" to "Full database" on the update window to get the new component. The numeric values inside the component I've assigned like this. 1, 2, 3, 10 4, 5, 6, 11 ...

Hi Monie,

The document you want is probably the RPI getting started guide which is available towards the bottom of this page.

https://www.matrixtsl.com/flowcode/support/

Hello Sadik,

The PIC32MX says it supports up to 4GB.

I believe FAT16 supports up to 4GB and FAT32 will support up to 64GB. I'll investigate internal and USB storage support.

Hi Jan,

Can you send us a link or photo of your keypad layout. We can probably fairly easily create a new component with the right layout for you.

You also need to remember to terminate the string. e.g. add a null byte to mark the end of the data.

For example

s[0] = 65
s[1] = 'x'
s[2] = 0

Would give you "Ax"

Hi Jorgen,

I happened to buy one last week so it should hopefully arrive today and I'll be able to investigate why it isn't working for you.

Hi Sadik,

Just to be clear are you wanting to write to the internal flash on the PIC32 device or to a USB memory stick?

We don't currently support these via components but as a bit of an investigation I can certainly try to help with implementing either.

Hi Jorgen, Hmm, There are no blocking functions in the component code but it may be the I2C CAL that is blocking. Do you have pull up resistors on the SDA and SCL traces? Internal pull up resistors may also be an option if your target device supports this. Are you using software or hardware I2C? I b...

Hello, Thanks for letting us know. I've been in and added the Char$ function now, it was the only string function that was missing but strange it was missing. It's on this page, https://www.matrixtsl.com/wiki/index.php?title=String_Manipulation_Functions Or via the main help index page listed under ...

Hi Jorgen,

Try this instead.

Hello,

Brilliant, glad it's working correctly for you now.

The easiest way is to use an DSP output component and read the value into a float variable. Once there you can do any floating point calculations required.

Hi Roy, I've noticed a couple of things. Your input read is converting the whole of PortB into an input which may be causing temporary issues on your motor drivers. The value of delay in the loop is going to set the speed for both motors. To solve the problem I used the switch components to allow me...

Hi Jorgen, I'm out the office today but I've made the component for you, hopefully it should work well but let me know. I'll push it to the update system tomorrow when I'm back in but here is the component file if you want to try it today. Just copy the file into your "C:\ProgramData\MatrixTSL\...

Hi Jorgen,

I'll have a look for you tomorrow.

Your suggestion was to pick up a PicKit 3, which I have now done :) The issue is that I am having trouble getting a connection to the PicKit 3. Receiving a rather vague error message. I've posted on the forum detailing the exact issue and error, and did receive 1 response, but that unfortunately wa...

Hello,

It looks like the scale maths is going a bit strange for signed buffers in the simulator. I've changed the buffers to be unsigned and changed the parameters of the sine wave generator and now it is hopefully working as expected.



Let me know how you get on.

Hello Sandro,

Welcome to the forums. Can you attach what you have done so far and we will have a look for you and hopefully point you back in the right direction.

Hi Sadik,

Many thanks for letting me know. I had added the brightness function to the component but not exposed it. I've pushed an updated version of the component to the update system now which should allow you to control the brightness of the display.

Hello,

Leigh has some experience of this but he on holiday this week. I'll ask him to have a look on his return next week.

I'll also have a bit of a dig and see if I can find any examples for you.

Hello, Have you tried compiling a very simple program such as a 1 second flasher to double check if the device is being programmed correctly as it is reporting. Can you post your program so we can double check there is nothing wrong there. Other then this it looks to be something to do with the Wind...

Hello, Brilliant thanks for letting us know. I wonder if there is a silicone errata document for the 256 device i.e. a known problem. The same code should run fine on both and generally a family will share a silicone design so strange the 128 version is ok but the 256 is not? I'll make a note in cas...

Hi John,

We currently do not support this device, even in Flowcode 8. I could look at adding it into v8 if that would be useful.

I'm afraid that the compiler shipped with Flowcode 6 will not support this chip.