Matrix user forums

Hello

After updates RTC is working ok, thanks.

I also noticed that DS3231 component from FC6 is working ok in FC7. (at least on arduino?)
viewtopic.php?f=58&t=14566


How usually FC6 components are compatible with FC7? Does it depend on compiler?

Hello, I get following compiler error on FC7 after trying DS3231 RTC module (Otherwise system works OK with i2c OLED display) FC7 version: 7.2.1.4 C:\Users\Arska\Dropbox\FLOWCO~1>"C:\PROGRA~2\FLOWCO~2\COMPIL~1\avr\BATCHF~1\..\bin\avr-gcc.exe" -mmcu=atmega2560 -Os -funsigned-char -o "C...

Hello, The component should have a property named I2C Delay or something similar. please can you check this is set to No. If this does not solve the issue for you then please can you post your program. Actually the component was SSD1306 i2c not 1305... But anyway i didin't find any i2c delay settin...

I Tried to use SSD1306 I2C display with FC7, but the screen update is very slow, In FC6 same program works OK (with same settings)

Processor speed is ok (based on 1 hz led blinker) PIC18f46k22

Is it possible to have speed settings for I2C communication for this component?

Benj wrote:I have now fixed the problem. Simply copy the attached file into your "Flowcode 7/CAL/PIC" folder and the compilation should then work correctly.

PIC_CAL_IO.h

Thanks Benj, i will give it a try.

It would be nice to have error tolerant communication protocol for RF transfer:


something like this:

https://www.pjrc.com/teensy/td_libs_VirtualWire.html

FC7 software uart wont compile (12f683) it would be nice to have custom C code like in FC5. Well you can add custom C code in FC 6 and FC 7 or I am misunderstand you some how I mean c code editable components like in fc5. They disappeared with fc6 which was big loss on terms of functionality of the...

FC7 software uart wont compile (12f683)

When I open same file on FC6 it compiles ok. (File was orginally made in FC7 free version)


PS. Could you make interface more like in FC5 ( it has most clear layout so far...) + it would be nice to have custom C code like in FC5.

Hello Here is the current version of my MODBUS slave FLOWCODE components. Everything starts with MODBUS_master_requesting component.... So after you receive data to UART you will call that macro. This version is working fine with industrial Touch panels. Master writing multiple INTs command is not c...

I am still on FC5 because of this kind of problems I dont have time to troubleshoot FC6 related errors.

Is there any solution for this problem? Or should i stay on FC5?

For example this is what my touchscreen sends to PIC(18f4523) as a MODBUS master:

01 03 00 01 00 07 55 c8

And this is what my PIC "sees" :

01 03 01 07 55 c8, there is zeros missing, so the MODBUS slave wont work.


Above is workin correctly with FC 5...

Hello Again troubleshooting FC6 ( I am trying to port my FC5 program to FC 6, but there is continuosly some errors :( ) Now I am stuck with rs232 receive component. The problem is I cant receive "0" byte in FC6 This is possible in FC 5 by selecting "extended" datatype. What does ...

Hello


Yes, that was the issue... Thanks

OK

The problem was unconnected RTS/CTS pins in rs232 component... But I dont need those pins, could you fix this problem ?

Hello I have FC 6 version 6.0.4.0 installed I get following error message while trying to compile my program to HEX ( I have only "RS232 receivestring component" in my test program) C:\Program Files (x86)\Flowcode 6\CAL\PIC\PIC_CAL_UART.c(402:5): error: unknown identifier 'tris' C:\Program...

Hello Steve I tried to keed to MODBUS code quite simple... First the RSR232 component resceives the MASTER command starting with slave adress (1), which after comes the command 1,3,5,6 or 16. After that the program checks if the crc is ok and if it is OK program executes command + calculates reply C...

After Downloading version 6.03 i am able to open FC5 files without errors, so things are improving :) But the Dashboard panel is quite bad, I am not able to zoom in or out in the panel. I think you should dedicate mouse wheel to do the zooming. If you want to make good 3d / 2d interface, you should ...

Hello I will report same kind of a problem: After opening a FC5.fcf file in FC6 and trying to compile i get following errors: Errors when generating C source code: 18f45k22_v6.c : 848 : error : Syntax error 18f45k22_v6.c : 858 : error : Syntax error I have stepper motor, RS232 and ADC components fro...

I have also same problem, I tried to move on FC6, but the interface is more messy than in FC5. The pure 2D like in FC5 would be excellent. Also I tried to open my previous version of program on FC6, but I think it messed up things somehow :( because the program wont work in my PIC... I dont have tim...

Hello Here is code for working MODBUS slave. This program works well with industrial touchpanel and MODBUS RTU protocol. Touchpanel is sending commands as Master and PIC answer as a slave. The Command 16(write multiple int) is not so finished yet (because i haveny needed that so far.) The MODBUS par...

Hello Here is Flowcode 5 version with modified LCD component. There is modified code which allows LCD to interact with i2c. Basically display type is similar like this: http://www.ebay.com/itm/New-Blue-IIC-I2C-TWI-2004-20x4-Serial-LCD-Module-Display-for-Arduino-/281141014288?pt=LH_DefaultDomain_0&am...

Hi For example how do I add 20x4 LCD display, there is no way to edit v6 LCD display... You can just change the lines and columns near the bottom of the proberties panel. This only works for the basic LCD, (i.e the first in the list. The one that looks like a picture of a commerical panel is purely...

Hello I just bought this new version of flowcode, and i am little bit lost :( For example how do I add 20x4 LCD display, there is no way to edit v6 LCD display... How do I add my owc C code to the LCD display? I need to add i2c LCD custom code to the display. If I open my working version of v5 in v6...

Thanks Benj

It compiles now OK.

I would like to understand how the modified code works... I noticed that LCD RawSend macro is not calling transmit byte nor enable pulse i2c macros....

I didint understand when i2c transmission occurs inside the LCD macro.