Matrix user forums

Hi benj, The ECIO devices have their own programming tool which is located in the "Flowcode v4/Tools/ECIO" directory. When you select the ECIO as a target device this will automatically select its own programming tool and also predefine the correct configuration settings. Yep, that is how my system ...

Will PPP work with an ECIO module? When I installed FlowCode I didn't select the option of installing PPP, can it be done after the fact? Thanks for the code benp, but it certainly is much more complicated then what benj was suggesting. I'm thinking that benj's example must be utilizing some hidden ...

Hi benp --- thanks for uploading your code (I'll be looking it over after this post). I am using an ECIO-40P which has a PIC18F4455 on board. Well I am now testing benj's flash read/write examples in hardware and I am seeing something rather unusual. So here is what is happening: My program at first...

We all have those days

Probably a good thing I wasn't using ICD, otherwise the problem and the solution would have been farther down the road. So now you have one less thing to worry about.

For those that are following this, Ben just sent me some alternative C Code for Reading and Writing to the Flash Memory area on the PIC. Apparently there is a problem with getting the original examples to compile in FlowCode. Here are the new versions: /* Read from Flash Memory */ volatile char* reg...

Hey Ben -- I PM'ed you a link to my FlowCode Source, hopefully this will both help to clarify what I have done, and also lead to a solution.

Thanks

Hi Ben -- the 2 examples I showed were actually 2 independent C Code Blocks in FlowCode. I naturally assumed that the address should be an integer (16-Bits) and that the value to be read or written was limited to 1 byte. So far all I've done is create a macro for each instance (read and write) and p...

Thanks Steve -- I'll hold off on contacting you until my product has made it past the prototype stage, and is ready to go into production.

Real nice of you guys to offer this service.

Ben, I'm trying to implement the C-Code you gave into one of my flowcode programs and when I compile I get a failure due to the C-Code (doesn't give specifics). Here is my Write to Flash: /* temp = value to be written addr = flash memory address */ write_register(FCV_ADDR, FCV_TEMP); And here is my ...

I noticed when selecting either ECIO28P or ECIO40P as the target, the resulting Chip Diagram's pin-out although accurate for the particular USB programmable device, is not the same as the actual chip being used (PIC18F2455 or PIC18F4455). The main problem really lies in how the Chip Diagram is label...

Hello medelec35,
As you probably guessed by my other postings in the V4 section, my ECIO40P is working well. So basically the changes I made during the driver installation did the trick.

:lol: I really should have known that. Time to wake up and get some caffeine in my system. And yes deleting that entry did take care of the problem. BTW for those that are interested, here is a link to the Elektor article (and software) by Bert van Dam: http://www.elektor.com/magazines/2009/november...

Thanks medelec35 for the feedback. However I do have a question relating to deleting the 'SampleADC' Macro, and it simply comes down to how do I do that? Remember I can not see any macros other then the Main one, and the option to delete macros is grayed out. Would I have to first open this program ...

When I downloaded Bert van Dam's article and example FlowCode for the "Driver-free USB Interface", I get the following warnings when compiling to my ECIO40P: Warning unreferenced functions removed: FCI_FLOAT_TO_STRING in: C:\Program Files (x86)\Matrix Multimedia\Flowcode V4\FCD\internals.h FCI_NUMBE...

I guess its a Windows 7 compatibility problem (at least my version and service pack). Here's what I did to fix it: Right-clicked on the "Matrix_ECIO_Driver_install (amd64).exe" and selected "Properties", then selected the "Compatibility" tab and ticked the "Run this program in compatibility mode for...

When trying to install the ECIO driver software on my Dual Core AMD Laptop I get the following pop-up message: http://mytekcontrols.com/FlowCode/ECIOProblem.gif My Computer/OS Specifications: Acer Aspire 5534 AMD Athlon X2 Dual Core Processor L310 1.2 Ghz Memory = 4 GB Windows 7 Home Premium 64-Bit ...

I asked this same question back in my V3 days, and was hoping that the LCD command functions would be supported in V4 (reference: http://www.matrixmultimedia.com/mmforums/viewtopic.php?f=5&t=1318&p=5878&hilit=lcd+command+simulation#p5878 ) It would be very handy to say the least. Any way that this c...

Thanks guys, I was looking for a solution like this.

Although a Flash Memory component similar to the included EEPROM one would be nice, I can live with the C code version for what I need to do (thanks Ben).

Thanks Ben, Since we are talking about waiting on this until the next major revision, I just thought of one more possibility that would be really cool and useful. Suggestion #7: allow grouped objects to have the option to be retained as a permanent group (with un-grouping as yet another option). Bot...

First of all; I absolutely love the addition of this Panel Creation feature. This is something that LabView has had for years, and it is truly a pleasure to see its implementation in FlowCode V4. However after using it for a few days, I do have some suggestions, which I believe should be doable with...

Well I downloaded the V4 Demo and tried running the Graphical LCD 2 Channel Analog Scope simulation. Boy was it slow on my system (Pentium 4 -- 2.66Ghz, 1Gb RAM, XP Home Service Pack 3). CPU usage went up to 100% and stayed there the entire time that the simulation mode was active (did this even wit...

If you are designing your system to always be on and reliably running then you can either play around with the code until the warning goes away or you can start using the watchdog timer peripheral. Although I would agree with using the watchdog timer to catch run away events, and it is a good idea ...

I didn't realize you could do that

Thanks Ben and Steve for the quick and informative responses to my questions.

Unusual System Clock Speeds --- Using a crystal or oscillator input such as 14.318 Mhz which is 4 times the color burst frequency for NTSC video, or some other multiple at an even higher frequency, in order to directly produce color NTSC video output from a PIC (not something that could be done with...

Interesting, I'll give this a try. Too bad there wasn't a device config aspect in FlowCode that would let you set this parameter by clicking a box. Then if FlowCode saw that this box was checked, it would know to either pull up an alternate FCD file for the particular target chip selected, or I don'...