LCD Display

[seandepagnier]

On my  PI I have installed an OpenPlotter+PI software. I have adjusted a motor.ino sketch on arduino so that I can drive the motor controller. The arduino board is linked trough USB to the Raspberry to exchange the data. At the moment the functions are limited only to drive the motor without rudderfeedback, rudder stops, voltage , temperature warnings.
Opening Openplotter the AP control seems to work , the pilot is engaged , the compass heading is displayed and moving the sensor compass the autopilot reacts properly moving the motor. However I well know that I have to work extensively on the motor.ino sketch in order to have an acceptable working base.

Why is that? motor.ino should not need significant changes

My question is:
1)-Having linked to the raspberry , trough GPIO SPI an external display ( even if different from the Nokia and jlx ones listed in the lcd and hat.py files) is it possible to have the data displayed on it as Andreas did, on my arrangement?

Which exact display are you using?

2)-Is it possible to change the display commands including an ST7735 driver?

If you can get tftfb working.. then linux framebuffer output is supported. Otherwise you could simply write another driver for your display.

3)-Fitting in the above arrangement a keypad device and a jlx display , should the openplotter pilot work without any other changes to the files?

In theory.. Lets hear what changes you end up needing to make to help improve pypilot.

4)-Opening the files in /usr/local/lib/pypilot3.7 the lcd.py seems to list the default drivers (nokia and jlx) but in any other file I have found the relative driver commands. Moreover running hat.py and lcd.py the data ( heading, standby) appear on the screen but not on the display ( of course I know  the ST7735 driver display is not compatible but if I change it with a jlx one could I have the data displayed on it?

There are 4 drivers supported:
nokia5110
jlx12864
linux framebuffer
glut (opengl window mostly for debugging)

You can pass the driver on the command line to use, or edit ~/.pypilot/hat.conf to specify which driver to use. If you changed to the jlx12864, then it will work once you specify this in the hat.conf. My hardware generally contains an i2c eeprom on i2c bus 0 which is programmed with a small configuration file which indicates the hardware attached, the screen type etc. Without this you have to manually edit the configuration file, as these spi displays (unfortunately) have no feedback or way to read data from them and so therefore no way to perform auto detection.