Matrix user forums

LM35 have only 0.5 °C resolution. Why are you using 0.125 multiplier? Try DS18B20, it has a resolution of 0.0625 °C, what is enough for displaying 0.1 °C precision. The main problem is the "TempdegC" variable, what is FLOAT. Try to never use FLOAT, you can make some tricks. From "calculate temperatu...

Try this:

It's doesn't matter, where is the SetDutyCycle command. After the PWM enabled, the output goes to full duty until it's got another SetDutyCycle command. I've tested it on Flowcode 5, on that version, only the second problem exists, set duty to 255 is not 100 % duty on the HW.

Second problem: Set the duty to 255, simulation shows az 100 %, but in the real HW, it's not 100 %.

Hello!

I made a little PWM test and i found two problems. See attached program.

First problem: When i power up the controller, after the PWM enable, it's turns on as full duty until it's get another command.

The flowchart command sends the charaters to a buffer (SW, HW, both?) then waits 4 ms, the main process does not wait for the UART module to finish the job. This is why you see more pause at higher UART baudrate. I think.

Highly recommended, start testing the display via an USB - UART converter. Much-much faster. You can test the commands (with your program in the display), if everithing is ok, write the microcontroller program. Whit this procedure, you can thest the display first. Othervise, you won't know where is ...

I think, the best way using this displays as a normal display. Do everything by the controller, reading from the display only the touch event, nothing more. Reading by UART interrupt, sending data as normal UART communication, easy to use. Sedning "12345" text to object t0: SendRS232String("t0.txt="...

Normally, the I2C bus needs 4.7 kOhm pull up. If you use 2.2 kOhm and the SSD1306 has built-in pull up, the result can be lower than 2.2 kOhm. Smaller resistance, harder to pull down by the RTC and/or SSD1306. Or try to monitor the I2C bus by a logic analyser.

Benj wrote:Would it be possible for you to share your v5 flowchart with us.

Yes: DS18B20 & Memory (ROM) usage (Flowcode v6 topic).

PicoPuls wrote:Does that mean that the Microchip FREE mode compiles 10 times faster
than the previous compiler in Flowcode6?

Maybe only the hex generation is faster. Same flowchart tested in FC v5, v6 and v7:

Yes, i'm using XP only for two reasons: Flowcode and Proteus. The main system is Mac OS. Ok, no problem to create a new virtual machine. The problem is simple: i can install, but not run. Message from the installer is missing: "Flowcode 7 requires Windows 7 or newer" -> "Quit Installer" (no other op...

Hello!

A little mistake:

Hello!

Where is the System requirements? Flowcode 7 free version installed without any warnings, but if I want to start, i got this:
... FlowcodeV7.exe is not a Win32 application.


The Win system is very minimal in a virtual machine, separated from the world.

Did you try pure UART (RS232) communication? I think, when you call the GSM module, it's sending the information via UART.

External D/A converter.

Use the fastest controller you got, clock it as fast as possible. In the gLCD properties panel, set the "Display Enable" to 1. Zero, or higher number than 1 will slow down the gLCD. I'm using some KS0108 with PIC18F26K22 at 64 MHz, but the display isn't too fast. Better than running the controller a...

Hello!

Result of the last update:

Hello!

Better...
Suggestion

Hello!
Pin "LED" is still in use. If disconneted, got "verbose error" message: "boostc_18F.exe reported error code 1". Portait - landscape problem still exists. Slow update (PIC is running at 64 MHz) problem is still exists.

All the best!

Where did you got this problem? HW? Simulation? One interesting thing (accidental?):

7654321 - 7588785 = 65536 (0x10000)

Can you test it with other controller? Or try to multiply in two setps:

V_5 = V_5 * 5000
V_5 = V_5 *2

or

V_5 = V_5 * 100 * 100

...

What is the problem exactly? You have to send 9 bytes to control the player. Here is some example: Play: 7e,ff,06,0d,00,00,00,fe,ee,ef Pause: 7e,ff,06,0e,00,00,00,fe,ed,ef Stop: 7e,ff,06,11,00,00,00,fe,ea,ef Next: 7e,ff,06,01,00,00,00,fe,fa,ef Previous: 7e,ff,06,02,00,00,00,fe,f9,ef Play first file:...

Try to connect the Reset pin to Vcc (3.3 V) or GND. Do not leave floating because it can generate continuous resets on the display.

Other memory usage test. Simple, GPS* based clock with 4 x 7seg display (direct drive).
*ublox NEO 6M module

I think the bug in Flowcode. This program working well with Flowcode V5, but not with V6. Other informations here: OneWire bug report.