tft lcd hy28b read lcd brands
You can use an IDC connector which crimps onto a ribbon cable to connect wires/ribbon cable to the LCD (see http://www.mantech.co.za/ProductInfo.aspx?Item=83M0013 for example). If you only need to connect to the LCD data and control pins you don"t need that many connections and you could use SIL sockets (www.mantech.co.za/Stock.aspx?Query=SOCK+SIL+STR+HOUSED+2.54and) but then you"ll need to solder wires to the socket pins. You can also use SIL housing (http://www.mantech.co.za/Stock.aspx?Query=housing+SIL+2.54and) but this requires that you crimp wires on terminals, not all that easy without a proper crimping tool. Perhaps the easiest would be to get hold of an old IDE hard drive ribbon connector (http://www.computerhope.com/jargon/i/ide.htm), I think it should fit.
I suggest you try and find a tutorial/code/description for your specific LCD board, because the LCD controller chip is only rated to work with input voltages up to 3.3V. Some boards put in voltage shift IC"s which makes them compatible with the Arduino 5V output. There are also different data transfer settings (8 bit, 16 bit, SPI). If you only push 8 bit data but the controller is configured for 16 bit data you will have an obvious problem. If it is configured for 8 bit transfer, you need to know whether you must connect to DB0-DB7 or DB8-DB15. I have an LCD board which is configured for 8 bit transfer, but have to use pins DB8-DB15.
While googling for any info about lcd controller I came across this page: http://heikki.virekunnas.fi/2015/raspberry-pi-tft/, author managed to get from manufacturer patch file for kernel sources and tested it with 4.1.y - on which lcd worked. But still LCD replace HDMI, but I want to use this screen as additional for user interaction, while the bigger on HDMI as presentation monitor.
Since, fbtft has been merged with rpi kernel, so the fb drivers (including ili9341.c) was moved to fbtft_device driver (so the author of page can"t compile latest kernel with driver+patch).
So something about hardware, which I reverse engineered by the "hard way" - "grab multimeter and run through all LCD FPC pins and shift register pins"
Now I noticed there is "9486L" which can suggest that LCD screen is controlled by ILI9486L, I found this LCD on taobao too but I can"t contact seller.
I"m pretty sure about D/C (Pin 37 on LCD) and Reset (Pin 19 on LCD) pins by looking into driver code, but I can"t identify other signals (WR/RD/CS/etc...)
- Controller is not ILI9341/ILI9325 - those are for smaller displays (320x240, etc...), I guess this might be ILI9486/9488 because they are for 480x320 displays. But when I compared init with DS it does not fit right so LCD can have a clone of ILI9486/9488 ...
- Module use only SPI interface and two CE signals (CE0 for touch controller, CE1 for LCD shift registers - compared to others lcd modules, in KeDei module this is swapped),
I just finished two solid days of work trying to get an HDMI LCD panel working with one of the inexpensive older model TFT LCD displays in a "Dual mode" configuration. There was a tremendous amount of help from this post, which got me most of the way there, but the infamous "last mile" still took me a while. I"m leaving some breadcrumbs here, as well as asking the group if anyone knows of a better way.
I am working on a device that uses a Raspberry Pi 4 as an embedded controller. For output, I need an 2K DSI LCD w/ its own HDMI adapter (Sharp LS055R1SX04, about $65 USD), as well as an inexpensive TFT LCD used for a basic touch user interface. The TFT LCD, which uses an ILI9341 LCD controller and an ads7846 touchscreen controller, can be had for about $10 USD. The Pi was flashed with the latest Raspberry Pi OS 32 bit then updated, so everything is current as of this writing (March 2021).
Initial configuration of the display worked with little issue. The HDMI adapter for the Sharp LCD works at 50 Hz only, so it requires custom timings. The TFT LCD uses the same controller chips as the original 3.5" Raspberry Pi LCD, so I was able to activate it with the rpi-display dtoverlay.
Booting with the above correctly revealed two framebuffer devices listed with ls -l /dev/fb*. The display initially showed as all white, then went all black, indicating correct initialization. However, when starting the desktop GUI, only the Sharp LCD showed any contents, and only it was listed as a device by xrandr.
Based on claims of the above not being "ideal", I experimented with various settings. If the above file is deleted entirely, xrandr reports the Sharp LCD as the sole display. If you put the above file in place, and remove all references to the Sharp LCD (including the Device, Monitor, Screen, and ServerLayouts), xrandr correctly reports the TFT LCD, but not the Sharp LCD. I left JUST the Device sections in, but xrandr failed to correctly report one of the other.
Since xrandr was INOP in this configuration, I could not use xinput --map-to-output to limit touchscreen coordinates to the TFT LCD. Instead, I settled on using a combination of touch screen rotation, and input coordinate translation:
Note that the TransformationMatrix is very specific to a 1440x2560 in portrait mode with 320x240 in landscape mode to the right of the Sharp LCD. The numbers are basically:
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
My question to the group, if anyone knows, is simple: is it possible to configure a Pi4 so an SPI connected LCD can co-exist without disabling the RandR extension in X11?
which is of course a different driver. I already had a customized overlay source, so I changed it to use the mentioned "mi0283qt" driver. It did not work (my screen remains blank white). I also tried the straight ili9341 driver (with no "fb_" prefix). Both showed results from modetest, but the screen remained white.
Switching to the "multi-inno,mi0283qt" compatible and I get nothing. Reading the DT bindings, the backlight has been moved from being a GPIO property of the display to being a link to the backlight device driver, so it"s understandable that the backlight stays off.
At this point, I"m going to just fall back to the configuration I posted at the beginning of this first thread. It seems to work fine. And while it may in theory not be ideal, it works for my purposes (I"m creating a very basic touch UI on the touchscreen. I"m not trying to stream video to it or anything crazy).
I"ll keep the "the legacy driver is being deprecated" in the back of my head for future purposes. Maybe by the time that happens, if this configuration is still needed, someone will have taken the information in this thread and figured out the problem.
However it is as I suspected - we have no mouse pointer on the TFT screen, presumably as X can"t cope with one display having a cursor plane and the other not. I don"t know the best way to overcome that.
Which sounds like yours (i.e the "Unknown19-1). I got the "lock up" again, but it turns out that lock-up was actually VNC (I"ve been using that to develop, as the text on a Sharp LCD is VERY tiny to look at in desktop mode). My console was still alive, so I hooked up an actual keyboard and mouse to the Pi, and the desktop on my Sharp LCD came alive. With the above two commands you"ve discovered, I now have two desktops. Sort of...
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
It appears as if the upper left hand corner of my Sharp LCD desktop is mirrored on the small LCD. It"s not two independent desktops. Instead, it"s the same desktop duplicated. I suspect that is probably more X configuration than driver stuff, however.
Asia has long dominated the display module TFT LCD manufacturers’ scene. After all, most major display module manufacturers can be found in countries like China, South Korea, Japan, and India.
In this post, we’ll list down 7 best display module TFT LCD manufacturers in the USA. We’ll see why these companies deserve recognition as top players in the American display module industry.
STONE Technologies is a leading display module TFT LCD manufacturer in the world. The company is based in Beijing, China, and has been in operations since 2010. STONE quickly grew to become one of the most trusted display module manufacturers in 14 years.
Now, let’s move on to the list of the best display module manufacturers in the USA. These companies are your best picks if you need to find a display module TFT LCD manufacturer based in the United States:
Planar Systems is a digital display company headquartered in Hillsboro, Oregon. It specializes in providing digital display solutions such as LCD video walls and large format LCD displays.
Microtips Technology is a global electronics manufacturer based in Orlando, Florida. The company was established in 1990 and has grown into a strong fixture in the LCD industry.
What makes Microtips a great display module TFT LCD manufacturer in the USA lies in its close ties with all its customers. It does so by establishing a good rapport with its clients starting from the initial product discussions. Microtips manages to keep this exceptional rapport throughout the entire client relationship by:
Displaytech is an American display module TFT LCD manufacturer headquartered in Carlsbad, California. It was founded in 1989 and is part of several companies under the Seacomp group. The company specializes in manufacturing small to medium-sized LCD modules for various devices across all possible industries.
The company also manufactures embedded TFT devices, interface boards, and LCD development boards. Also, Displaytech offers design services for embedded products, display-based PCB assemblies, and turnkey products.
Displaytech makes it easy for clients to create their own customized LCD modules. There is a feature called Design Your Custom LCD Panel found on their site. Clients simply need to input their specifications such as their desired dimensions, LCD configuration, attributes, connector type, operating and storage temperature, and other pertinent information. Clients can then submit this form to Displaytech to get feedback, suggestions, and quotes.
A vast product range, good customization options, and responsive customer service – all these factors make Displaytech among the leading LCD manufacturers in the USA.
Products that Phoenix Display offers include standard, semi-custom, and fully-customized LCD modules. Specifically, these products comprise Phoenix Display’s offerings:
Clients flock to Phoenix Display because of their decades-long experience in the display manufacturing field. The company also combines its technical expertise with its competitive manufacturing capabilities to produce the best possible LCD products for its clients.
True Vision Displays is an American display module TFT LCD manufacturing company located at Cerritos, California. It specializes in LCD display solutions for special applications in modern industries. Most of their clients come from highly-demanding fields such as aerospace, defense, medical, and financial industries.
The company produces several types of TFT LCD products. Most of them are industrial-grade and comes in various resolution types such as VGA, QVGA, XGA, and SXGA. Clients may also select product enclosures for these modules.
All products feature high-bright LCD systems that come from the company’s proprietary low-power LED backlight technology. The modules and screens also come in ruggedized forms perfect for highly-demanding outdoor industrial use.
LXD Incorporated is among the earliest LCD manufacturers in the world. The company was founded in 1968 by James Fergason under the name International Liquid Xtal Company (ILIXCO). Its first headquarters was in Kent, Ohio. At present, LXD is based in Raleigh, North Carolina.
We’ve listed the top 7 display module TFT LCD manufacturers in the USA. All these companies may not be as well-known as other Asian manufacturers are, but they are equally competent and can deliver high-quality display products according to the client’s specifications. Contact any of them if you need a US-based manufacturer to service your display solutions needs.
We also briefly touched on STONE Technologies, another excellent LCD module manufacturer based in China. Consider partnering with STONE if you want top-of-the-line smart LCD products and you’re not necessarily looking for a US-based manufacturer. STONE will surely provide the right display solution for your needs anywhere you are on the globe.
Acts as a bidirectional databus buffer with 3state option. Not really used yet, the TFT is only written to but it is possible to also read from the TFT registers.
This block first configures the TFT it is connected to (right after power on reset is finished). For instance it sets the TFT into RGB565 mode. After that it goes into write mode and all it does is constantly update the TFT view (showing either camera images or tresholded images. When this block is done configuring it signals to the next block that it can start it"s configuration:
This block took a lot of work. The Omnivision camera (OV7670) needs to be configured after power-up. For example we need to set it"s output to RGB565 mode (meaning the R-factor of a pixel is 5 bits, G is 6 and B is 5 again). I chose this to make it match with my ILI9325 TFT which has the same feature. Sccb is very similar to I2C (I-square-C, protocol invented by Philips a long time ago). But it has its differences which took me many many hours to get right!
Last but not least. This is where the actual magic happens. The block gets images from the OV7670 camera (driven by the camera"s HREF and VSYNC lines which together indicate a start + end of frame (image)). Inside the block the comparison for each pixel is done (realtime!) with the characteristics of the pixel range we look for (in this case bright pixels). SW1 is there to choose what to see on the TFT: normal camera images or the tresholded images. The image_treshold block also sends the VSYNC and HREF lines of the camera to the ili9325 block which is required to drive and synchronise the TFT to show the images.
Hello Patrik. Just to let you know that we do have now Lcd’s in stock but if you still need mcHF kit without display please email me at djchrismarc@genieprojects.co.uk so we can make custom invoice for your purchase.
I bought version 0.4 in 2016 and bought all the components including the LCD display. thus, having not yet assembled the rtx, is it possible to order only the two blank PCB version 0.6.3?
I have the tranceriver version 0.5. A HY28B model screen has broken down, I bought an identical model screen 2 years ago, and now that the test is broken, blank LCD. I have done several hours of testing with the other screen and all the work in bathroom. How would we do to get a new LCD that works well? Let’s see if there is any solution. Shipping is to Spain. Thank you
I wanted to say that I have the broken LCD, and one that I bought in another kit, when I put it on my MCHF it has a blank screen. All my work in vain. What solution can we give? can you send me another one?
Any word on when it will be ready? I was about to drop the money on a 0.7 kit when stock ran out. If it is going to be months more I may scream and drop the kilobuck+ on an IC-7200, which seems to have similar features + a 100W output.
I was wondering if the mcHF 0.6 components kit has the SMD components soldered on already. I assume (and hope) the answer is no, so that I will get to do some SMD soldering!
Hi, I just received my v0.6 boards and components last week, and have begun assembly of the UI board. I am wondering about the recommended LCD, where do I source one? What are the options
Hi Chris, I obtained an unstarted v0.5 kit from Israel. I then managed to install the LCD upside-down. Desoldering and removal has caused quite a bit of damage to LCD lands and tracks on the UI board. What options are open to me? Are there any v0.5 UI kit boards available on their own? Or even a v0.6 if it will still work?
Can I order just the U1 board from the surface mounted kit with the LCD? I got both boards together and U1 programmed but the LCD was bad and of course I had soldered it in. Got it out with only two traces ripped up and it is probably salvageable but.
I see that you are no longer offering the LCD as a part. Is it still included in the full kit? Also is there a simple way to determine what if any mods apply to the current kit?
Yes, two boards (UI and RF) with all SMD parts installed in the factory – by pick and place machine, then wave soldering. Also in the kit a LCD plus two plastic bags with extra parts – mostly through hole that you need to solder.
I have the boards from a former order from you and the display from ebay. I have read that you are out of boards and display. Does this mean you could send a full kit minus boards and displays? If yes, I would be interested to get one full-kit-minus-boards-and-display at a somewhat reduced price.
If you have any kits available please send it (since I have already paid for the international shipping, but if not, please refund the shipping and I will try to get one when you have more available (can you please place me on the “list” to get one in the future ?
I just ordered your complete mcHF kit with international shipping but it seems that you have already sold out of the radio’s, but I did successfully pay for the shipping.
You are not supposed to solder a header socket for the LCD, it is not part of the BOM and has never been. In theory you can solder one, keep in mind those are very expensive due to the non standard pitch, also your UI board will no longer fit in the 3D case. But if you make your own case, then you can use it. Soon i will list some RF packs only for sale. Check my page from time to time (also i post on Twitter).
I have ordered UI Board Kit and RF PCB several minutes ago. I’m surprised about the wonderful project and hope to read something about new features in future.
Hi, you can probably use different LCD, but will not match the UI board and the front panel. In theory you can add any LCD with QVGA resolution and similar size, and just update the LCD driver to support it. If you want it just as it is, please wait maybe another week, i will have the LCDs back in stock. 73
Dear sir, I’m new in the ham biz. Your project seems to beawesome and Exactly what I’m looking for as an underbudget beginner. I’d like to know if these 3 parts (2 pcb’s and a lcd) are all I need to build the transceiver? Is there a full kit available with the exact instructions?
You can order directly from China, np. Make sure you move the jumper before soldering the LCD to the UI board(need 16 bit mode). I do embedded development and Reverse Engineering for a living.
Just orderred for RF PCB + UI PCB + HY28B LCD. My PayPal transaction # 6KP04308DP576410H dated Dec 15, 2014. I can source for UI, but can you suggest where I can get RF PCB components from a single source or do you supply? Thank you
For soldering iron i use ERSA i-con nano, as for hot air, look on ebay for cheap Chinese ones – any that allow temperature and flow regulation with LCD will do.
I am a ham radio operator from India. I would like to get two sets of PCBS and LCD displays. Is it possible for you to send to me by courier ( FedEx or similar so that speedy delivery is possible)
I have read that by carefully selecting the mixer switching chips it is possible to achieve 50 and 70 Mhz. This will also require the more expensive SI570 versions that can go higher than 160 Mhz. From software point of view this is 10 mins coding, but for VHF you need much better front end, pre-amps, filtering, etc. Also i see in KX3 they push the same final for 50 Mhz as well, but not sure how efficient is the whole thing in 1-50 Mhz range, requires real knowledge in analogue design to make this.
As per today both boards and the LCD are available I just ordered the three items using PayPal for payment. If PayPal does not dieplay my adress please respond to my email adress!
arailabiltxy of boards: what a pity, now th UI board and LCD are available but the RF board is sold out! As the shipping costs to the outside of the UK is so high I waited for teh order of the RF board which was avaliable — last week? Now I can order the other baord and esseantila LCD but without the RF board the Transceiver is not complete. Is there a Chance when all three baords are avaliable at the same time???
Yes, i have some UI boards now, probably will update the site tomorrow as i am waiting for DHL to bring some LCDs as well. Those are the HY28B – dual interface version. The latest mcHF firmware supports all the three versions manufactured by hotmcu.com.
If HY28A is detected on boot up, the SPI is used, if HY28B – the parallel is in use. There is no change of the location of the 16 bit parallel port pins on the three different LCD modules.
I really like the idea of a kit (may be only the “hard to get” components) and suggest to introduce a list for people who want to buy a complete set of pcb´s / LCD and/or kits.
Soon will be available on the Order page, but limited quantity, based on what i have prepared already for sending, to prevent long wait, like the last two weeks.
A year after it was first announced, the Raspberry Pi touch display finally launched on Tuesday. The new component means Raspberry Pi hackers can now experiment with an officially sanctioned 7-inch, 800-by-480, 10-point multi-touch LCD display for their Pi projects.
The connection between the Pi and the driver board relies on the DSI interface leaving the Pi’s HDMI port free to power a second display. You can read all about the display adapter decisions on the Raspberry Pi Foundation’s blog.
When you first get it, the display will also require a bit of assembly since the driver board and a few cables need to be connected to the display first. Future versions of the touchscreen will come already assembled.
We"ve been committed to offering easy,time-saving and money-saving one-stop purchasing service of consumer for Tft Lcd Panel, Tft Information Display, Round Lcd Display, Led Tft Display,Lcd Counter Module. Honesty is our principle, skilled procedure is our perform, service is our target, and customers" satisfaction is our long term! The product will supply to all over the world, such as Europe, America, Australia,Wellington, Tunisia,New York, Mauritius.It using the world"s leading system for reliable operation, a low failure rate, it suitable for Argentina customers choice. Our company is situated within the national civilized cities, the traffic is very convenient, unique geographical and economic conditions. We pursue a people-oriented, meticulous manufacturing, brainstorm, build brilliant" business philosophy. Strict quality management, perfect service, reasonable price in Argentina is our stand on the premise of competition. If necessary, welcome to contact us by our website or phone consultation, we will be happy to serve you.
This project started out with the simple idea of improving the temperature stability, and grew into a more elaborate controller with an LCD screen, water level sensing and pump control. This is an attempt to document the project (partly for my own notes), which I hope to update as I continue to tweak the design.
In this setup, the machine currently boots up automatically when powered on, regulates coffee temperature, displays current temperature, pressure and water level on an LCD and logs time, temperature, pressure and flow data to CSV files, which are accessible over the wireless network via Samba.
Caution: I’ve since read that some of these Fotek branded SSRs are fake, and may not meet the rated current. Take care in selecting a suitable SSR for your mains voltage and load current.
In this project, I originally used the Dallas DS18B20 Digital Thermometer, which has a number of advantages. First, it is already calibrated and accurate to +/-0.5°C. It also uses a serial digital interface that can be easily interfaced. Finally, it uses a 1-wire bus interface that means we can potentially add several temperature sensors to a single bus. This reduces the amount of wiring needed and, more importantly, the number of GPIO pins needed.
Originally, I spread the DS18B20 with thermal paste and cable tied it flush to the aluminium body of the boiler, in the vicinity of the existing thermostat. This performed well, and I ran the machine like this for several months.
Reading the sensor from user mode worked but was a little unreliable due to unpredictable OS interruptions. To improve reliability, I wrote a kernel driver to talk to the sensor, which I used for about 8 months. Later still, I re-implemented it again using the PIGPIO library, which is the current version used. The new sensor is now installed and running on the machine, and seems to perform very well.
The obvious way to do this is to add a flow sensor. Since an espresso shot is a relatively small volume (30ml to 60ml), we need a sensor with fairly high resolution. We can’t put it on the output side of the pump because of the high pressure (~15 bar) and the vibratory pump could give erratic readings, and perhaps damage the sensor. We also don’t want it in contact with the boiler. Ideally, we also want something non-toxic and “food safe” since it will be plumbed into the machine!
Eventually, I gave up on user mode and implemented a kernel driver which can achieve more accurate timing. This worked much more reliably (I would estimate about 2-3mm resolution), and gives a nice steady level indication on the LCD. More recently, I re-implemented the range finder with the PIGPIO library which makes the software much simpler to install and use.
The display is the HY28A which is a 2.8″ Colour Touch Screen TFT LCD with an SPI interface for both the LCD and the touch sensor. It has since been replaced by a newer model HY28B.
When I bought this, I fully expected to have to write the code to drive it, but was surprised to find that Linux Framebuffer drivers are already available for this display, and many others.
I have this configured so that it displays a console on the LCD as soon the Pi boots, so that any boot messages can be seen. Rather than running under X Windows, I decided that the controller would run under the console to reduce overhead and use SDL to draw on the LCD.
Note that the factory protective film is still stuck to the LCD screen in these photographs, which is a bit dirty/scratched. I’m planning to buy some new screen protection material to replace it when I’ve finished tinkering with the hardware.
Although the display has a touch-screen, I decided that wasn’t ideal for daily use in the kitchen, so I’ve added two stainless steel buttons. In the first version, these used 4K7 pull up resistors to 3.3V and were active low, pulling the GPIO pin to ground when pushed. As I added more equipment to the machine, I began to run out of GPIO lines. The latest version uses a single analogue input with a resistor ladder to read all the buttons as described here.
Here’s an (OUT OF DATE) circuit diagram for the old version. There were three 0.1″ (2.54mm) pin header connectors, P1 and P2 connected the Pi to the LCD touch-screen, and P3 connected the Pi to the machine (sensors and boiler/pump control).
The temperature regulator runs on a separate thread, as does the display controller. Most of the sensors (such as the flow sensor and ranger) also use threads. In places, the code makes use of edge triggered interrupts (for the flow sensor pulse counting, range finding etc), to avoid busy waiting.
Has anyone had any success with getting JiveLite to work with the ADAFruit Capacitive PiTFT? it doesn"t seem to matter what I do, I just cannot get it to work. I can fairly easily get the interface to show up on the PiTFT screen and have made good use of the LCDScreen theme applet posted further back in this thread, however the touch aspect just doesn"t work. The mouse pointer can only be moved around the top left hand corner of the screen, no matter where you touch. I"m pretty sure this is an SDL issue, perhaps something to do with video resolutions, but my knowledge of SDL is rather limited to say the least. My guess is that a starting point would be to reset the SDL video mode upon load of a theme, maybe this is already done, but I"m at a loose end at the moment.
Has anyone had any success with getting JiveLite to work with the ADAFruit Capacitive PiTFT? it doesn"t seem to matter what I do, I just cannot get it to work. I can fairly easily get the interface to show up on the PiTFT screen and have made good use of the LCDScreen theme applet posted further back in this thread, however the touch aspect just doesn"t work. The mouse pointer can only be moved around the top left hand corner of the screen, no matter where you touch. I"m pretty sure this is an SDL issue, perhaps something to do with video resolutions, but my knowledge of SDL is rather limited to say the least. My guess is that a starting point would be to reset the SDL video mode upon load of a theme, maybe this is already done, but I"m at a loose end at the moment.
Reason for the question is that I am currently using a modified Squeezelite that imports Squeezeslave code so that LCDproc can be used (and infrared) and it is working well.
Reason for the question is that I am currently using a modified Squeezelite that imports Squeezeslave code so that LCDproc can be used (and infrared) and it is working well.
Tried to add a zip with the skin, but I think the zip is to big, so I only added the .lua files to the zip. Unzip the LCDSkin to jivelite/share/jive/applets, copy the image-folder from WQVGAsmallSkin inside the LCDSkin-folder.
I just bought a adafruit piTFT and configured it following the adafruit tutorial (https://learn.adafruit.com/adafruit-pitft-28-inch-resistive-touchscreen-display-raspberry-pi)
If i plug hdmi cable and reboot and launch jivelite using SDL_FBDEV=/dev/fb1 or SDL_FBDEV=/dev/fb0 always display jivelite on hdmi screen. Only difference is when i launch SDL_FBDEV=/dev/fb1 the piTFT turns black with left top cursor (and return to console when i stop jivelite) while running jivelite with SDL_FBDEV=/dev/fb0 doesn"t change piTFT output.
Then clone jivelite sources using one of repository that already implements piTFT customized skin (https://code.google.com/p/jivelite/source/clones): "git clone
The capacitive PiTFT displays jivelite fine. BUT the touch function doesn"t work. The mouse cursor can only be moved around the top left hand corner of the screen, no matter where you touch.
There is a solution hint at #268 http://forums.slimdevices.com/showthread.php?98156-Announce-JiveLite-cut-down-squeezebox-control-application&p=804070&viewfull=1#post804070 but as Newbie I do not understand what to do.
The capacitive PiTFT displays jivelite fine. BUT the touch function doesn"t work. The mouse cursor can only be moved around the top left hand corner of the screen, no matter where you touch.
4) sudo nano /boot/config.txt -> add: dtoverlay=lirc-rpi,gpio_in_pin=4 (in my case I use GPIO pin 4 for the infrared receiver - because other GPIOs are used by the PiTFT display)
I am trying to get jivelite working on my raspberry pi2 with an adafruit 2.8 PiTFT touch display. The display is installed properly. Squeezelite is also working. Before I started the installation I have flashed the official Rasbian image. I followed the installation instruction in post #3 and installed the mentioned dependencies including lib6-dev.
cc platform_linux.o jive.o jive_event.o jive_font.o jive_group.o jive_icon.o jive_label.o jive_menu.o jive_slider.o jive_style.o jive_surface.o jive_textarea.o jive_textinput.o jive_utils.o jive_widget.o jive_window.o jive_framework.o log.o system.o jive_dns.o jive_debug.o resize.o visualizer/visualizer.o visualizer/spectrum.o visualizer/vumeter.o visualizer/kiss_fft.o -lrt -lSDL -lSDL_ttf -lSDL_image -lSDL_gfx -lluajit-5.1 -lm -lpthread -o ../bin/jivelite
I am trying to get jivelite working on my raspberry pi2 with an adafruit 2.8 PiTFT touch display. The display is installed properly. Squeezelite is also working. Before I started the installation I have flashed the official Rasbian image. I followed the installation instruction in post #3 and installed the mentioned dependencies including lib6-dev.
cc platform_linux.o jive.o jive_event.o jive_font.o jive_group.o jive_icon.o jive_label.o jive_menu.o jive_slider.o jive_style.o jive_surface.o jive_textarea.o jive_textinput.o jive_utils.o jive_widget.o jive_window.o jive_framework.o log.o system.o jive_dns.o jive_debug.o resize.o visualizer/visualizer.o visualizer/spectrum.o visualizer/vumeter.o visualizer/kiss_fft.o -lrt -lSDL -lSDL_ttf -lSDL_image -lSDL_gfx -lluajit-5.1 -lm -lpthread -o ../bin/jivelite
I believe that some people on the forum have touchscreens running http://forums.slimdevices.com/showthread.php?97803-piCorePlayer-Squeezelite-on-Microcore-linux-An-embedded-OS-in-RAM-with-Squeezelit
First you should disconnect the small touchscreen and connect your pi via hdmi to a large screen. Then choose the correct resolution for you 2.8 TFT Display and shutdown the pi. Connect the 2.8 Display again with your pi. After rebooting it should be working well.
Hi, I"m planning to use a touchscreen (maybe the new 7" raspberry pi display, maybe one of the smaller PiTFTs) as a frontend with jivelite on my raspberry. I wondered, if jivelite will open an on-screen keyboard whenever text can be entered, as in a search (which I would regularly do in the spotify plugin for example). Best case scenario for me would be to operate without a physical keyboard
Hi, I"m planning to use a touchscreen (maybe the new 7" raspberry pi display, maybe one of the smaller PiTFTs) as a frontend with jivelite on my raspberry. I wondered, if jivelite will open an on-screen keyboard whenever text can be entered, as in a search (which I would regularly do in the spotify plugin for example). Best case scenario for me would be to operate without a physical keyboard
I hope I"m in the right thread. I desperately tried (with my still limited linux experience) to remotely control my jivelite. My setup is a raspberry pi with the new 7in touchscreen and jivelite as the frontend for my LMS setup. I got LIRC running, configured my remote, but nothing happens in jivelite.
Jesse is a clean and updated install. Installed the PiTFT drivers and kernel from adafruit. If I startx and boot into Raspbian the touchscreen behaves perfectly.
I spoke too soon. It worked a few minutes then started going crazy again. I"m certain there is a resolution problem as I"ve hooked several other monitors up and I can start and run jivelite on all of them except the 480x320 PiTFT.
I have this 99% figured out. I had so much trouble I went back to Jesse. Jesse uses SDL 2.0 which is has major problems with PiTFT according to Adafruit. They have a script you can run to remove 2.0 and force install SDL 1.2. However it seemed to break some other things so I just abandoned it. Now everything is working fine under Wheezy.
So the moral to this story is don"t install the brand new shiny Adafruit PiTFT touchscreen with Raspbian Jesse. After I went back to Wheezy and SDL 1.2 passing the environment variables worked as advertised in this thread.
Is there a setting where scrolling speed and step width are determined? It really stutters across the screen if the fonts are large enough to be read from a certain distance. Or can"t the framebuffer handle a higher update speed? Thanks for any hints on this!
Ok, so I found the file in /opt/jivelite/share/jive/applets/ImageViewer, opened it in vi, changed the two instances of 1000 to 5000, but it"s read only.
Ok, so I found the file in /opt/jivelite/share/jive/applets/ImageViewer, opened it in vi, changed the two instances of 1000 to 5000, but it"s read only.
hi. As you might know piCorePlayer is almost impossible to break, this is because after every reboot the original read-only packages are installed again. It is one of its strengths, but it also means that it is more difficult to make changes in the packages.
hi. As you might know piCorePlayer is almost impossible to break, this is because after every reboot the original read-only packages are installed again. It is one of its strengths, but it also means that it is more difficult to make changes in the packages.
Ok, so I found the file in /opt/jivelite/share/jive/applets/ImageViewer, opened it in vi, changed the two instances of 1000 to 5000, but it"s read only.
hi. As you might know piCorePlayer is almost impossible to break, this is because after every reboot the original read-only packages are installed again. It is one of its strengths, but it also means that it is more difficult to make changes in the packages.
Thanks for the tip, however, when I went to save the edited copy of ImageSourceLocalStorage.lua in vi, it said that the file was read only (even though its noted as lrwxrwxrwx with ls -l).
Thanks for the tip, however, when I went to save the edited copy of ImageSourceLocalStorage.lua in vi, it said that the file was read only (even though its noted as lrwxrwxrwx with ls -l).
After enabling the "Alarm Settings" menue you have to edit the PFTFTSkinApplet.lua file and change the lines starting at "local _timeFirstColumnX12h":
Please excuse my noobness but I have looked all over and read this announcement but is there a posting or instructions on how to run Jivelite from the command prompt, use the frame buffer with the official pi screen and the touch input work correctly?
Please excuse my noobness but I have looked all over and read this announcement but is there a posting or instructions on how to run Jivelite from the command prompt, use the frame buffer with the official pi screen and the touch input work correctly?
Tried to add a zip with the skin, but I think the zip is to big, so I only added the .lua files to the zip. Unzip the LCDSkin to jivelite/share/jive/applets, copy the image-folder from WQVGAsmallSkin inside the LCDSkin-folder.
If I run Jivelite like a window in xde (read here (http://forums.slimdevices.com/showthread.php?98156-Announce-JiveLite-cut-down-squeezebox-control-application&p=830898&viewfull=1#post830898)), touch work with any problem!
Is it possible to put the command "send magic packet" from settings -> picoreplayer -> Wake-on-lan to the main menu of Jivelite? It would be great if i could start my ReadyNAS from the main menu
I have set up several raspberries with squeezelite. Currently I am controlling all with my iPad or iPhone. But somehow I always have to search for a iPad or iPhone, because they are never on the place it should be. So I thought about a inexpensive solution, setting up dedicated raspberry with a small LCD screen and Jivelite for controlling all the other sqeezeplayers.
I already set one raspberry up, but I was not able to change the raspberry / squeeze-player. I see the different players in my network (Einstellungen -> Erweitert -> Informationen zur Squeezebox -> Player-Informationen), but I am not able to select one (a different one) and to control it.
I successfully managed to install jivelite on the latest version of raspbian usings a 3.2" Waveshare TFT. Everything is working fine except the "when off" screensaver (when playing works fine!). I want it to display the Clock but no matter what I select (not even Blank Screen), nothing happens when i press the off button (music stops). If it matters I am using jivelite to remote control squeezelite on another machine (Behavior is the same if iI select one of my Squeezebox Radios)
I successfully managed to install jivelite on the latest version of raspbian usings a 3.2" Waveshare TFT. Everything is working fine except the "when off" screensaver (when playing works fine!). I want it to display the Clock but no matter what I select (not even Blank Screen), nothing happens when i press the off button (music stops). If it matters I am using jivelite to remote control squeezelite on another machine (Behavior is the same if iI select one of my Squeezebox Radios)
Yesterday I"ve also connected a nice LCD screen grabbed from an old laptop (using a V56 card) to use it like a monitor for the Orange Pi One. My screen is 1920x1200 but after few settings it is not so bad (err... it"s a wonderful LG LCD after all).
- I installed JiveLite "the hard way": following the instructions on the first page, I knew that google code closed and I knew JiveLite was on github, so I changed the git clone address. But why do you not change the instructions directly on the first page of this thread?
In my side I wrote a very little python script to manage LCD 16x2 or 20x4 on the I2C especially for the Orange Pi Zero (it is also working for the Raspberry) because it was harder (so more fun) when you have more or less no documentation, for the Orange Pi Zero, and you have to discover by yourself. Looking at JiveLite running gives me some ideas for my script!
Yes, there"s an environment variable for this. See my post in this thread (http://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer&p=839818&viewfull=1#post839818).
Yes, there"s an environment variable for this. See my post in this thread (http://forums.slimdevices.com/showthread.php?103330-Jivelite-for-piCorePlayer&p=839818&viewfull=1#post839818).
Huh - just started a thread because I"m having the same issue... Was anyone here able to resolve it (and why on earth does it just work in PiCorePlayer ???)