4D Displays - Basics
Posted: Fri Jun 17, 2022 3:58 pm
Hi,
I'm hoping to tackle the display requirments for a customer project and I've been meaning to do more with the 4D displays.
In Early FC examples by Jon Crow..the graphic widgets were setup in 4D software and loaded to the screen. Commands were then sent/recieved from the PIC. Visually complex widgets in $DC designer are easily dragged and dropped into the display.
Q; In Jon's example FC commands like 'VisiRecieve' and 'VisiReadByteFromMessage' ... is there an equivalent command in the New 4D components?
I've just looked at the later 4D components in current FC. These seem to be more of a drawing package, building the graphics from PIC commands.
Q: Does the 4D display need to be in a specific Mode (Serial?) or a config file loading on its SD card to work with these FC component macros? or just spit them out of the UART into the Displal RX,TX.
Q: are there big differences between the V1 and V2 4D component versions ?
Thanks, J.
I'm hoping to tackle the display requirments for a customer project and I've been meaning to do more with the 4D displays.
In Early FC examples by Jon Crow..the graphic widgets were setup in 4D software and loaded to the screen. Commands were then sent/recieved from the PIC. Visually complex widgets in $DC designer are easily dragged and dropped into the display.
Q; In Jon's example FC commands like 'VisiRecieve' and 'VisiReadByteFromMessage' ... is there an equivalent command in the New 4D components?
I've just looked at the later 4D components in current FC. These seem to be more of a drawing package, building the graphics from PIC commands.
Q: Does the 4D display need to be in a specific Mode (Serial?) or a config file loading on its SD card to work with these FC component macros? or just spit them out of the UART into the Displal RX,TX.
Q: are there big differences between the V1 and V2 4D component versions ?
Thanks, J.