g0wfv
commented
8 years ago Can the host not access a remote LCDproc server when run from a Windows machine?
As for native support, you could always have a go at writing it yourself ....
Closed iball closed 8 years ago
g0wfv
commented
8 years ago Can the host not access a remote LCDproc server when run from a Windows machine?
As for native support, you could always have a go at writing it yourself ....
g0wfv
commented
8 years ago OK, so looking at these LCDs, they aren't connected via serial to USB adapters. In fact thinking about it, there is no way they can be anyway, as the HD44780 is a parallel device, not a serial device!
The first board you linked to is built around an ATMega328 chip (Arduino!) and the second a PIC16F88 chip.
Without looking deeper, they probably have some kind of command implementation all of their own and will not easily fit into the existing HD44780 code as I managed to do for the PCF8574 I2C support.
iball
commented
8 years ago MMDVMHost when run from a Windows 10 64-bit PC can not access the same LCDd Pi-housed server I was successfully running already with a DVMega Pi.
Odd. This is the same exact serial TFT I'm currently using with LCDd running on a Pi to get LCDproc client data from MMDVMHost running on another Pi across the room.
phl0
commented
8 years ago Jupp. But the logic for controlling the display is implemented in LCDd then. MMDVMHost speaks a rather basic / abstract protocol with LCDproc which has nothing to do with controlling the display.
iball
commented
8 years ago OK. Closing request then.
phl0
commented
8 years ago Why not go ahead and try an implementation? ;-)
g0wfv
commented
8 years ago I'm sorry, perhaps my night shift addled brain is misunderstanding your attempted setup!
Are you running MMDVMHost on Windows, but trying to access a TFT connected to a Pi being controlled by LCDproc?
Or trying to run with the TFT connected to the Windows machine?
On Tue, 8 Nov 2016, 20:00 Florian (DF2ET), notifications@github.com wrote:
Why not go ahead and try an implementation? ;-)
— You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/g4klx/MMDVMHost/issues/204#issuecomment-259211045, or mute the thread https://github.com/notifications/unsubscribe-auth/AQf_4t2w50B2TK79DwGgSE3sgCHmri8Kks5q8LjTgaJpZM4Kr7R2 .
A J Corbett
G0WFV
iball
commented
8 years ago Tony, no problem man, I've been there.
I'm running the latest version of MMDVMHost on a Windows 64-bit PC with MMDVM.ini setup to point to LCDd running on another Raspberry Pi in a 7" display case that has a serial 2x16 LCD hooked up to it via USB-to-serial adapter.
This works just FINE for a DVMega installed on another Pi's GPIO pins and it's sending just fine from the DVmega Pi to the LCDd Pi and displaying on the LCD well - a little corruption on the "Listening" side but other than that it's fine.
So yes, from a Windows MMDVMHost process to a Pi running LCDd with a 2x16 LCD connected to a USB port on it via serial adapter.
OK, so we have support for the HD44780 LCD in I2C mode, and support for a TFT Serial - can we get support for HD44780 LCDs that have a serial backpack on them and are connected on a serial port via USB-to-serial adapter?
Something like these:
https://www.sparkfun.com/products/10097
https://www.sparkfun.com/products/9568
Normally I'd use LCDproc, but LCDproc doesn't work when MMDVMHost is run on a Windows box.