Migrating to V6
Flowcode v6 will automatically attempt to migrate Flowcode v5 projects and components into the required v6 format. While the program attempts to re-create your panel as much as possible and maintain your components configuration settings there may be a requirement for the user to make minor adjustments to the imported program. Please bear in mind the following points:
Positioning of components on the panel
In version 5 the panel is a two-dimensional pane. Each component was written using visual basic, exported and registered as a OCX component which would be called by earlier versions of Flowcode (3 through 5). Graphical representation of these components are basically bitmaps placed onto a windows panel. In version 6 the panel is now a three-dimensional space where the components will be placed, and each component has been re-designed purely using the v6 component creator. Therefore based on v5 positions an estimate is made with regards to placement in v6. This may not necessarily be exactly as you would see it in version 5 so you may need to make adjustments to the layout of any components that appear on the panel.
Software & Hardware channel selection
In version 5, components that had the ability to choose between software and hardware channels, however this was a manual choice and the user would have to determine which hardware channels were available based on the chip-type. The components were hard-coded to offer 4 hardware channels regardless of channels available on the chip. In version 6 the number of hardware channels that are presented to the user are now pre-defined based on the contents of the chip-definition files(i.e the number and type of channels the chip supports), so if a chip supports two hardware channels then in Flowcode v6 the user will be presented with the option to choose software, hardware channel one and hardware channel two. If a user had chosen hardware channel 4 in the v5 program, this value will not get migrated if the chip-type in flowcode v6 does not have channel 4 as an option. If this field is blank when you have migrated your project you will need to set the channel appropriately.
Component migration table
| Component | Status | Consideration |
|---|---|---|
| GLCD | Mapped | No problems reported.
Note1: In version 5 the type of GLCD was selected from a seletion of radio buttons. When migrating to version 6, the appropraite GCLD component is chosen based on this setting (there are multiple GLCD components in v6 to choose from). |
| LED | Mapped | No problems reported. |
| LED RGB | Mapped | No problems reported. |
| LED 7Seg Single | Mapped | No problems reported. |
| LED 7Seg Quad | Mapped | No problems reported. |
| Quad Encoder | Mapped | No problems reported. |
| PWM | Mapped | No problems reported. |
| Servo | Mapped | No problems reported. |
| Accelerometer | Mapped | No problems reported. |
| One-Wire | Mapped | No problems reported. |
| Keypad | Mapped | No problems reported. |
| Stepper Motor | Mapped | No problems reported. |
| Formula Flowcode | Mapped | No problems reported. |
| RC5 | Mapped | No problems reported. |
| LCD Display | Mapped | No problems reported. |
| USB HID | Mapped | No problems reported. |
| USB Serial | Mapped | No problems reported. |
| USB_Slave | Mapped | No problems reported. |
| FAT16 | Mapped | No problems reported. |
| MIDI | Mapped | No problems reported. |
| CAN | Mapped | No problems reported. |
| CAN2 | Mapped | No problems reported. |
| ADC | Mapped | No problems reported.
Note1: Styles, labels & custom images are not carried over from version 5. Scales and markings will need complementing with a v6 marking control. |
| Bluetooth | Mapped | No problems reported. |
| Custom | DROPPED | This component will not be migrated from V5 due to the new component creation features. |
| Custom2 | DROPPED | This component will not be migrated from V5 due to the new component creation features. |
| EEprom | Mapped | No problems reported.
Note1: v6 component size is fixed 256 bytes, v5 was configurable. |
| I2C | Mapped | No problems reported. |
| IrDA | Mapped | No problems reported.
Note1: For this component you will have to set CTS/RTS pins manually. This is because CTS/RTS port/pin values were not saved for this component in v5(bug). |
| Lin Master | Mapped | Awaiting fucntional test.
Note1: the WakeUp() macro is missing in v6. Needs sorting. |
| Lin Slave | Mapped | No problems reported.
NOTE1: In v5 the messages are stored as a string. V6 needs to extrapolate the string and populate the various message settings. Macros missing in v6 compared to v5. |
| RFiD | Mapped | No problems reported. |
| RS232 | Mapped | No problems reported.
NOTE1: v5 change baud rate macro not present in v6. Needs addressing. As does RX Timeouts parameters. |
| SPI | Mapped | No problems reported. |
| SwitchBank | Mapped | No problems reported.
Note1: Labels not carried forward or direction (lsb left or right positioned) Also, the switch array in v6 allows you to tag a switch style to it. This would be used to determine the type of switches in the switchbank. This may have to be done manually. |
| TCP-IP | Mapped | No problems reported.
Note1: In v6 the TCP/IP component has two versions, one for EB023-001 and EB023-002. The appropriate component will be selected based on the hardware choice set in v5. |
| Webserver | Mapped | No problems reported. |
| Zigbee | Mapped | No problems reported |
| GPS | Mapped | No problems reported |
| Speech | Mapped | No problems reported.
Note1: pitch is not migrated yet. Also port selection needs addressing. Also ReadPhonemeLength macro missing from v6. |
| Switch | Mapped | No problems reported.
Note1: Custom and rotary switches are not yet present in v6 so they will default to basic switch. All others will show a representative switch model. |
| RF | Mapped | No problems reported. |
| GSM | Mapped | No problems reported |
| WLAN | Mapped | No problems reported. |
| DSP Level | Mapped | No problems reported.
Note1: The v5 macro ReadSingleBank_FFT() is no longer applicable in v6 for this component. You will have to adjust your flowchart accordingly. |
| DSP Add | Mapped | No problems reported. |
| DSP Control | Mapped | No problems reported. |
| DSP Delay | Mapped | No problems reported. |
| DSP FFT | Mapped | No problems reported.
Note 1: The v6 component has an additional parameter that needs setting manually. You will need to connect the 'output_i' parameter to a free buffer from your DSP System component. Note 2: You need to set your FFT options and appropriate bit depth parameter here. You need to manually get the value from your v5 DSP System component if you want to use the same settings that you had in your v5 program. |
| DSP Filter | Mapped | No problems reported. |
| DSP Freq Generator | Mapped | No problems reported. |
| DSP Input | Mapped | No problems reported. |
| DSP Inverse FFT | Mapped | No problems reported. |
| DSP Kalman Filter | Mapped | No problems reported. |
| DSP Output | Mapped | No problems reported. |
| DSP Scale | Mapped | No problems reported. |
| DSP System | Mapped | No problems reported.
Note1: In version 5 this component allowed for 10 buffers however you could only have one DSP System component in use. In version 6, the DSP System component is limited to 8 buffers however you can now have multiple DSP System components in your design. If your v5 DSP System component has more than 8 buffers then for the remaining ones you have to manually add a second DSP System in v6 and configure the remaining buffers accordingly. Note 2: FFT settings set in the DSP System component in v5 no longer exist in the v6 version as these have moved to the v6 FFT component. See FFT component above. |
| MIAC | Mapped | No problems reported. |
