Difference between revisions of "Migrating to V6"
| Line 175: | Line 175: | ||
|- | |- | ||
| width="15%" | GPS | | width="15%" | GPS | ||
| − | | width="10%" bgcolor=" | + | | width="10%" bgcolor="Orange" | Mapped |
| − | | width="75%" | Awaiting | + | | width="75%" | Awaiting functional test |
|- | |- | ||
| width="15%" | Speech | | width="15%" | Speech | ||
Revision as of 08:58, 15 July 2013
Flowcode v6 will automatically attempt to migrate Flowcode v5 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 were basically bitmaps 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 avaialble 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 based on the contents of the chip-definition files, 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.
Component migration table
| Component | Status | Consideration |
|---|---|---|
| GLCD | Mapped | Awaiting functional test. 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 | Awaiting functional test. |
| LED RGB | Mapped | Awaiting functional test. |
| LED 7Seg Single | Mapped | Awaiting functional test. |
| LED 7Seg Quad | Mapped | Awaiting functional test. |
| Quad Encoder | Mapped | Awaiting functional test. |
| PWM | Mapped | Awaiting functional test. |
| Servo | Mapped | Awaiting functional test. |
| Accelerometer | Mapped | Awaiting functional test. |
| One-Wire | Mapped | Awaiting functional test. |
| Keypad | Mapped | Awaiting functional test. |
| Stepper Motor | Mapped | Awaiting functional test. |
| Formula Flowcode | Mapped | Awaiting functional test. |
| RC5 | Mapped | Awaiting functional test. |
| LCD Display | Mapped | Awaiting functional test. |
| USB HID | Mapped | Awaiting functional test. |
| USB Serial | Mapped | Awaiting functional test. |
| USB_Slave | Mapped | Awaiting functional test. |
| FAT16 | Mapped | Awaiting functional test. |
| MIDI | Mapped | Awaiting functional test. |
| CAN | Mapped | Awaiting functional test. |
| CAN2 | Todo | Awaiting mapping |
| ADC | Todo | Awaiting mapping |
| Bluetooth | Todo | Awaiting mapping |
| Custom | DROPPED | This component will not be migrated from V5. |
| Custom2 | DROPPED | This component will not be migrated from V5. |
| EEprom | Todo | Awaiting mapping |
| I2C | Todo | Awaiting mapping |
| IrDA | Mapped | Awaiting functional test. 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). |
| LEDS | Todo | Awaiting mapping |
| Lin Master | Todo | Awaiting mapping |
| Lin Slave | Todo | Awaiting mapping |
| RFiD | Todo | Awaiting mapping |
| RS232 | Todo | Awaiting mapping |
| SPI | Todo | Awaiting mapping |
| SwitchBank | Todo | Awaiting mapping |
| TCP-IP | Todo | Awaiting mapping |
| Webserver | Todo | Awaiting mapping |
| WebServer2 | Todo | Awaiting mapping |
| Zigbee | Todo | Awaiting mapping |
| GPS | Mapped | Awaiting functional test |
| Speech | Todo | Awaiting mapping |
| Switch | Todo | Awaiting mapping |
| RF | Todo | Awaiting mapping |
| GSM | Mapped | Awaiting functional test |
| WLAN | Todo | Awaiting mapping |
| DSP Level | Todo | Awaiting mapping |
| DSP Add | Todo | Awaiting mapping |
| DSP Control | Todo | Awaiting mapping |
| DSP Delay | Todo | Awaiting mapping |
| DSP FFT | Todo | Awaiting mapping |
| DSP Filter | Todo | Awaiting mapping |
| DSP Freq Generator | Todo | Awaiting mapping |
| DSP Input | Todo | Awaiting mapping |
| DSP Inverse FFT | Todo | Awaiting mapping |
| DSP Kalman Filter | Todo | Awaiting mapping |
| DSP Output | Todo | Awaiting mapping |
| DSP Scale | Todo | Awaiting mapping |
| DSP System | Todo | Awaiting mapping |
| MIAC | Todo | Awaiting mapping |
