Matrix user forums

Thanks - these are good ideas that are already on our lists. Some of these files are required during ICD, so they can't be totally removed in all situations. An alternative suggestion has been to put all intermediate files into a separate working folder (either directly off the project file itself, ...

Hi all,

We upgraded the site's certificate a few weeks ago, but there seems to be a problem with it when it changed over today. We're looking into it and should rectify it in the next hour or so.

And I hope to have a new installer for Flowcode v8 out later today.

Regards,
Steve.

I have created a new version of mLoader which will be distributed as part of a Flowcode v8 patch that I hope to release in the next week or two. If anyone wants to try it (especially @PHolz, @RILamb, or anyone else experiencing the problem in this thread), you can download and unzip the attached and...

Thanks, Frank.

We should have a patch for V8 out later this week.

Regards,
Steve.

Hi Martin, No need to upload the registry as I know what's preventing Flowcode from running. The reason for the initial crash, however, remains a mystery. I did release (via PM) a special build of Flowcode v8 at the end of Jan to people who were experiencing the problem. This tackles some of the pot...

Hi Robert,

Excellent - I'm glad you're back up and running. And thanks for your patience and help in sorting this out.

Regards,
Steve.

I see the problem. The "tools" folder in Flowcode should contain many subfolders such as "Buggyprog", PICkit2" and "mLoader". An image of mine is below. It looks like your mLoader files have all been placed directly in the "tools" folder, rather than unde...

Thanks, Robert. According to that message, there is no "mLoader" folder under "c:\Program Files (x86)\Flowcode v8\tools". Can you please check that folder to see if it's missing. Perhaps the "mLoader" folder has been renamed or been moved somewhere else? And where is th...

Hi Robert, Thanks for the mLoader debug messages. Please disregard my previous post about saving your flowcode program in a different location. The problem is that Flowcode is not finding the correct location of mLoader. I have prepared a batch file which should shed some light on why this is. Pleas...

Hi Robert, Did you get a similar debug message to @PHolz? Specifically, the "vid_8087&pid_0ac2" part? Regarding the problem with Flowcode, it looks like Flowcode can see the mLoader.exe file, but mLoader cannot see your HEX file. To easily fix this, you could make a new folder for your...

Thanks @PHolz. I'm glad the new mLoader is working for you.

And that debug message is very interesting. I'll investigate further tomorrow...

Hi Robert, Here is a link which will hopefully solve the 8.3 filename issue: https://www.matrixtsl.com/mmforums/viewtopic.php?f=76&t=20336&p=89900&hilit=getshortpathname#p89900 Before you try this, you can check to see if this is the problem by downloading and running the attached zip fi...

Hi Robert, I think the problem regarding the path is something to do with there being no 8.3 filename support on your PC. I will try to find the instructions to fix this shortly. In the meantime, could you please download and run this file with no Matrix board plugged in and let me know what message...

Hi Robert, Thanks for getting back to me. You should be able to rename the existing mLoader.exe file (e.g. to mLoader_original.exe) and then rename the mLoaderA.exe to mLoader.exe, and then it should work fine through Flowcode as well. Even if this all works fine for you, I would like to investigate...

Hi all,

Here's another file to try, if you have the time...



Regards,
Steve.

I'll have another look at this problem this morning and will get back to you both later today.

Hi Robert,

I think I have a fix for you. Please try the attached file and let me know how you get on.



Regards,
Steve.

Hi Robert.

Please try the attached file and let me know what message you get. Plug your E-blocks board in first before running mLoader. Also, can you please upload a screenshot of mLoader once it has run and you have dismissed the debug message.



Thanks,
Steve.

Thanks for the screenshots, Robert. I'll let you know when I think of the next step...

Hi Robert, Thanks for your patience in helping us solve this problem. Can you please download and unzip the following file into the "Flowcode 8/tools/mLoader" folder and run the mLoader_dbg.exe file: mLoader_dbg.zip This exe should display a debug message when running when it is looking fo...

Hi all,

If anyone wants to help and is experiencing this problem relatively frequently, can you please contact me via PM. I am creating a special build of Flowcode that will hopefully help and I want to test it a bit more before releasing it as a patch.

Thanks,
Steve.

Thanks, Martin.

I've not been able to replicate this myself, but I am about to send you a PM with something I'd like you to try.

Regards,
Steve.

For info, I checked v8 and it seems to work fine. I assume this bug was fixed a while ago in v7 or v8.

Flowcode supports only 26 connection points per macro. If you require more, then I guess your macro is very long and complicated, and you should perhaps rewrite it and/or split it into smaller macros. There are many debates about good programming practice, and some programmers recommend functions sh...

Thanks, Abhi - that information is really useful. I have a few other quick questions if you don't mind... Are you still getting the shutdown problem? Does it happen all the time or only occasionally? Is there something specific you can do in Flowcode to make the shutdown problem happen? Regards, Ste...