v6.0.7 Issues
Moderator: Benj
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
v6.0.7 Issues
Since v6.0.6 flowcode now detects a new 6.0.7 version is available to download,
I thought I would start a new thread for bugs since I did not want to hijack someone else's thread.
If anyone would like to report bugs on this unofficial thread, they are more than welcome!
Servo component not importing correctly from V5
If any V5 flowchart contains a servo component then when V6 flowchart is ran, Unknown or missing component warning will appear.
IMPORTANT!
Servo component is totally unusable
If either servo is imported from FC5 or you add a servo, it does not appear with in component macros: Therefore it can't be used!
I thought I would start a new thread for bugs since I did not want to hijack someone else's thread.
If anyone would like to report bugs on this unofficial thread, they are more than welcome!
Servo component not importing correctly from V5
If any V5 flowchart contains a servo component then when V6 flowchart is ran, Unknown or missing component warning will appear.
IMPORTANT!
Servo component is totally unusable
If either servo is imported from FC5 or you add a servo, it does not appear with in component macros: Therefore it can't be used!
Martin
-
- Valued Contributor
- Posts: 2045
- Joined: Wed Aug 27, 2008 10:31 pm
- Location: Netherlands
- Has thanked: 553 times
- Been thanked: 1081 times
- Contact:
Re: v6.0.7 Update
The update process reset my Professional License to a Home License. Not a big issue, still annoying.
The input icon Port?.H bit issue for PIC16 is more serious.
The input icon Port?.H bit issue for PIC16 is more serious.
“Integrity is doing the right thing, even when no one is watching.”
― C.S. Lewis
― C.S. Lewis
-
- Posts: 170
- Joined: Sat Dec 10, 2011 7:21 pm
- Location: Canada
- Has thanked: 20 times
- Been thanked: 52 times
- Contact:
Re: v6.0.7 Issues
The ADC Dial component has gone missing for PIC 18.
The I2C LCD component still needs these fixes: (see the last posts in these threads)
http://www.matrixmultimedia.com/mmforum ... lcd#p57234
http://www.matrixmultimedia.com/mmforum ... lcd#p57186
Configuration settings are now working nicely!
The I2C LCD component still needs these fixes: (see the last posts in these threads)
http://www.matrixmultimedia.com/mmforum ... lcd#p57234
http://www.matrixmultimedia.com/mmforum ... lcd#p57186
Configuration settings are now working nicely!
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: v6.0.7 Issues
Minor bug:
When selecting a New project, the target device is not kept in focus on the Choose target of project options.
When selecting a New project, the target device is not kept in focus on the Choose target of project options.
Martin
- SteveM
- Posts: 55
- Joined: Tue Mar 25, 2014 2:09 pm
- Has thanked: 28 times
- Been thanked: 65 times
- Contact:
Re: v6.0.7 Issues
Hi there,medelec35 wrote:Servo component is totally unusable
If either servo is imported from FC5 or you add a servo, it does not appear with in component macros:
Looks like this is a problem in the upgrader, and maybe a little lack of explanation on our part!
The 'Servo' component that looks like a physical servo is purely a simulation component that is used for System Panel animations. Just like the real thing, the servo 'motor' only responds to a signal from a multi-channel controller - and it is this other component, 'Servo Controller', which is equivalent to the old v5 servo component.
There's a better explanation on the Wiki page for the component, along with a couple of demonstration Flowcode files that show the Servo/Controller combo in action - you can have as many of the Servo 'motors' as you have channels selected for the controller, so simulations of quite complex models can be built.
I'll pop the upgrader bug onto our 'to-do' list - it really should be linking to the controller component, as this is where all the downloadable code lives!
Best wishes,
Steve.
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: v6.0.7 Issues
Ah OK.SteveM wrote:The 'Servo' component that looks like a physical servo is purely a simulation component that is used for System Panel animations.
Thanks for that, my mistake.
So it's just the upgrader thats the issue.
There are people (myself included) like like to just drag and use, rather than keep visiting wiki prior to using.
Should the component be under the simulation section or name be altered so it suggests its for simulation only, to avoid confusion in the future?
I guess it could be an easy mistake for other people to make.
Martin
Martin
- mikn
- Posts: 209
- Joined: Mon Mar 03, 2014 10:11 pm
- Has thanked: 54 times
- Been thanked: 41 times
- Contact:
Re: v6.0.7 Issues
As an update request: It could be great if variable advices won't appear when I write comments.
Thanks.
Thanks.
- Attachments
-
- sc-comments.GIF (6.95 KiB) Viewed 15609 times
FC 6.1.3.2 (18.02.2016)
- mikn
- Posts: 209
- Joined: Mon Mar 03, 2014 10:11 pm
- Has thanked: 54 times
- Been thanked: 41 times
- Contact:
Re: v6.0.7 Issues
Small issue with 3d System panel.
I closed it and work with 2D only, but every time I start FC and open my project, 3D panel is back to it's place.
I closed it and work with 2D only, but every time I start FC and open my project, 3D panel is back to it's place.
- Attachments
-
- sc-3dsys.GIF (21.83 KiB) Viewed 15581 times
FC 6.1.3.2 (18.02.2016)
- SteveM
- Posts: 55
- Joined: Tue Mar 25, 2014 2:09 pm
- Has thanked: 28 times
- Been thanked: 65 times
- Contact:
Re: v6.0.7 Issues
Hi mikn,
That doesn't sound right - we'll take a look at the new routines that memorise the window positions and see if we can identify the problem.
In the mean-time, if you only ever want to use the 2D panel, you can completely disable the 3D panel in the global options....
- Open the menu item "View -> Global Options"
- Click the "Application" tab.
- You can now click the option boxes for "Use dashboard as the default panel", and "Disable the system panel".
If you do this, you will also find that you can get components onto your panel a little faster by just double clicking them in the menus without needing to drag them across the screen - normally this would make them appear on the System Panel (3D).
Best Regards,
Steve.
That doesn't sound right - we'll take a look at the new routines that memorise the window positions and see if we can identify the problem.
In the mean-time, if you only ever want to use the 2D panel, you can completely disable the 3D panel in the global options....
- Open the menu item "View -> Global Options"
- Click the "Application" tab.
- You can now click the option boxes for "Use dashboard as the default panel", and "Disable the system panel".
If you do this, you will also find that you can get components onto your panel a little faster by just double clicking them in the menus without needing to drag them across the screen - normally this would make them appear on the System Panel (3D).
Best Regards,
Steve.
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Servo pulse tolerance.
This may not be an issue?
Looking more into the servo.
A very good feature that is now added is to change maximum and minimum width.
Only minor issue is there is a -21.7% between required and actual pulse width with minimum set to 990us as measure width is 774.6us
& There is a -16.1% between required and actual pulse width with maximum set to 2100us as measure width is 1761.1us
Results obtained was using USB Testpod
I also compared testpod to Eb006 V9 and results are very close indeed.
using EB006 V9 on sampling 100K:
Minimum = 780us
Maximum = 1760us
I thought I would post my findings so it can be decided if tolerance is good enough or not?
Hardware is 16F1937 running with 19660800Hz crystal.
Looking more into the servo.
A very good feature that is now added is to change maximum and minimum width.
Only minor issue is there is a -21.7% between required and actual pulse width with minimum set to 990us as measure width is 774.6us
& There is a -16.1% between required and actual pulse width with maximum set to 2100us as measure width is 1761.1us
Results obtained was using USB Testpod
I also compared testpod to Eb006 V9 and results are very close indeed.
using EB006 V9 on sampling 100K:
Minimum = 780us
Maximum = 1760us
I thought I would post my findings so it can be decided if tolerance is good enough or not?
Hardware is 16F1937 running with 19660800Hz crystal.
Martin
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
LED Pins not retained from FC5
All single LED's imported from flowcode V5 always default to pin A0 irrespective of there original pin assignment.
Martin
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
RXint does not simulate.
Not sure if this should be a bug report or feature request?
Since I don't know if it was originally intended to simulate or not?
Since I don't know if it was originally intended to simulate or not?
Martin
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
RS232
Not testing all the baud rates.
With ECIO40
In hardware mode when baud is set to 2400, the actual baud is 13333! Martin
With ECIO40
In hardware mode when baud is set to 2400, the actual baud is 13333! Martin
- Attachments
-
- RS232test.fcfx
- (4.6 KiB) Downloaded 221 times
Martin
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: v6.0.7 Issues
Hi Martin,
RXINT doesn't currently simulate - feature request - I've put it on the list for you.
Looking into the RS232 baud problem it seems that the hardware UART cannot run that slow with the clock speed equal to 48MHz. I've checked the maths and it looks like this.
9600 = ((48000000 / 9600) - 16) / 64 = 77
4800 = ((48000000 / 4800) - 16) / 64 = 156
2400 = ((48000000 / 2400) - 16) / 64 = 312
312 or hex 0x138 is being truncated to 8-bit 0x38 which is then setting the baud to the 13KHz value your seeing.
I've added a warning to the CAL file so that you get a compiler warning if this happens.
RXINT doesn't currently simulate - feature request - I've put it on the list for you.
Looking into the RS232 baud problem it seems that the hardware UART cannot run that slow with the clock speed equal to 48MHz. I've checked the maths and it looks like this.
9600 = ((48000000 / 9600) - 16) / 64 = 77
4800 = ((48000000 / 4800) - 16) / 64 = 156
2400 = ((48000000 / 2400) - 16) / 64 = 312
312 or hex 0x138 is being truncated to 8-bit 0x38 which is then setting the baud to the 13KHz value your seeing.
I've added a warning to the CAL file so that you get a compiler warning if this happens.
This device has an optional 16-bit baud register so I can look into using this if needed. However some devices don't have this so it gets a bit complicated.C:\Program Files (x86)\Flowcode 6\CAL\PIC\PIC_CAL_UART.c(87): WARNING: The baud rate you have entered cannot be reached (too slow for crystal speed)
- Attachments
-
- PIC_CAL_UART.c
- (21.41 KiB) Downloaded 222 times
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: v6.0.7 Issues
Thanks Ben.
Happy with the fact if it's not going to work then produce a warning,
Martin
Happy with the fact if it's not going to work then produce a warning,
Martin
Martin
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: v6.0.7 Issues
Cheers Martin,
Started looking into the 16-bit baud registers but using them changes the baud calculation again so would need a third setting for the CAL file which I'm not feeling 100% about at the mo. So it's probably a fairly big change we can do when we get some time to have a good run at it.
It might be that we then default to the 16-bit baud calc to get more accurate baud rates where possible but would probably need to go through the FCDs and define if the 16-bit baud is available or not before we can do this.
For now the warning is a good enough quick fix
Started looking into the 16-bit baud registers but using them changes the baud calculation again so would need a third setting for the CAL file which I'm not feeling 100% about at the mo. So it's probably a fairly big change we can do when we get some time to have a good run at it.
It might be that we then default to the 16-bit baud calc to get more accurate baud rates where possible but would probably need to go through the FCDs and define if the 16-bit baud is available or not before we can do this.
For now the warning is a good enough quick fix
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Timer1 disables two pins with Flowcode V5 & V6
For example target device is 12F1840, using Timer1 configured for internal clock.
You will find that Timer1 Oscillator In (T1OSI, pin RA5) and Timer1 Oscillator Out (T1OSO pin RA4) pins are both disabled.
This is significant if using an 8 pin device and you require the use of these pins.
A work around is to place a C code block after Timer1 interrupt with:
Since clearing bit 3 of t1con disables the dedicated built in oscillator that requires external pins to work.
Not required if using internal clock.
This caught me out, so I thought i would post about it soother people are not caught out the same.
Martin
Edit: from Ben:
You will find that Timer1 Oscillator In (T1OSI, pin RA5) and Timer1 Oscillator Out (T1OSO pin RA4) pins are both disabled.
This is significant if using an 8 pin device and you require the use of these pins.
A work around is to place a C code block after Timer1 interrupt with:
Code: Select all
clear_bit(t1con,T1OSCEN);
Not required if using internal clock.
This caught me out, so I thought i would post about it soother people are not caught out the same.
Martin
Edit: from Ben:
Benj wrote: The Timer 1 issue has now been fully resolved across the 8-bit PIC family. It was a problem on pretty much all devices with timer 1 so weird we hadn't come across it before. Updated FCDX files will be included in the next release. If anyone wants any updated files in the mean time for testing then let me know.
Martin
-
- Posts: 1333
- Joined: Tue Oct 06, 2009 9:39 am
- Has thanked: 1135 times
- Been thanked: 299 times
- Contact:
Re: Timer1 disables two pins with Flowcode V5 & V6
Hi Martin!
Is this a bug in FC or is it norrmal, but a feature (trick) you know..
Best regard
Jorgen
Is this a bug in FC or is it norrmal, but a feature (trick) you know..
Best regard
Jorgen
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: Timer1 disables two pins with Flowcode V5 & V6
Hi Jorgen,
Its a bug, so posted a work around.
I placed the information in tips and tricks, since bug affects both FC5 and FC6 & post does not get lost with all other bugs.
So the solution is a tip
Martin
Edit: I have merged thread to here as it may be more appropriate.
Its a bug, so posted a work around.
I placed the information in tips and tricks, since bug affects both FC5 and FC6 & post does not get lost with all other bugs.
So the solution is a tip
Martin
Edit: I have merged thread to here as it may be more appropriate.
Last edited by medelec35 on Thu Jun 05, 2014 2:34 pm, edited 1 time in total.
Reason: Merged with a different thread.
Reason: Merged with a different thread.
Martin
-
- Posts: 1333
- Joined: Tue Oct 06, 2009 9:39 am
- Has thanked: 1135 times
- Been thanked: 299 times
- Contact:
Re: Timer1 disables two pins with Flowcode V5 & V6
Hi Again! and thank´for reply.
I can see that your information is a tip But if it is a bug, can we not fix it somewhere, both in FC5 and FC6. I prefer having Pic work properly right away without having to remember add C code.
I'm not good at C code.
Hope you understand what i mean
BR
Jorgen
I can see that your information is a tip But if it is a bug, can we not fix it somewhere, both in FC5 and FC6. I prefer having Pic work properly right away without having to remember add C code.
I'm not good at C code.
Hope you understand what i mean
BR
Jorgen
-
- Matrix Staff
- Posts: 9520
- Joined: Sat May 05, 2007 2:27 pm
- Location: Northamptonshire, UK
- Has thanked: 2585 times
- Been thanked: 3815 times
- Contact:
Re: Timer1 disables two pins with Flowcode V5 & V6
Hi I have just worked out the permanent solution for Flowcode V6.
Flowcode V5 is much more complex.
For V6:
You will need to load the .fcdx so make sure you have a back up of the original file.
Files can be found in:
C:\Program Files (x86)\Flowcode 6\FCD\PIC if 64 bit windows
or
C:\Program Files\Flowcode 6\FCD\PIC if 32 bit windows
Scroll down to the
and swap around the contents within rectangle boxes as shown:
The version that should work is the fcdx file with Prescaler Rate above Clock source Select.
I will move this to the issues selection as it may be more suitable there.
Besides there is not an official V6.0.7 bugs section!
Martin
Flowcode V5 is much more complex.
For V6:
You will need to load the .fcdx so make sure you have a back up of the original file.
Files can be found in:
C:\Program Files (x86)\Flowcode 6\FCD\PIC if 64 bit windows
or
C:\Program Files\Flowcode 6\FCD\PIC if 32 bit windows
Scroll down to the
Code: Select all
<interrupt ident='TMR1' ....
I will move this to the issues selection as it may be more suitable there.
Besides there is not an official V6.0.7 bugs section!
Martin
Martin
-
- Posts: 44
- Joined: Sat Dec 11, 2010 8:50 pm
- Has thanked: 8 times
- Been thanked: 3 times
- Contact:
Re: v6.0.7 Issues
Hi everybody,
running the servo example 1, in the component example page, is ok but trying to compile it I have error issues. The second example with the two servos is fine. What is going wrong?
Sakis
running the servo example 1, in the component example page, is ok but trying to compile it I have error issues. The second example with the two servos is fine. What is going wrong?
Sakis
-
- Posts: 243
- Joined: Tue Nov 27, 2012 12:53 pm
- Location: Cambridge, UK
- Has thanked: 140 times
- Been thanked: 118 times
- Contact:
Re: v6.0.7 Issues
A simple GUI Issue this...
I have one SPI and one RS232 component in the dashboard (system panel disabled).
Should I change any of the RS232 parameters in properties, the SPI Data Scope pops up, even though deselected in the View menu. I close the scope window, change any RS232 parameter, and up it pops again !
All the best,
Brendan
I have one SPI and one RS232 component in the dashboard (system panel disabled).
Should I change any of the RS232 parameters in properties, the SPI Data Scope pops up, even though deselected in the View menu. I close the scope window, change any RS232 parameter, and up it pops again !
All the best,
Brendan
LinkedIn Profile...
http://www.linkedin.com/in/brendantownsend
http://www.linkedin.com/in/brendantownsend
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: v6.0.7 Issues
Hello,
The Timer 1 issue has now been fully resolved across the 8-bit PIC family. It was a problem on pretty much all devices with timer 1 so weird we hadn't come across it before. Updated FCDX files will be included in the next release. If anyone wants any updated files in the mean time for testing then let me know.
I'll have a look into the servo motor example for you.
The scope window pop up is annoying at best and should be removed from the components in the next update release. I've added this to my list to double check it gets removed.
The Timer 1 issue has now been fully resolved across the 8-bit PIC family. It was a problem on pretty much all devices with timer 1 so weird we hadn't come across it before. Updated FCDX files will be included in the next release. If anyone wants any updated files in the mean time for testing then let me know.
I'll have a look into the servo motor example for you.
The scope window pop up is annoying at best and should be removed from the components in the next update release. I've added this to my list to double check it gets removed.
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel