Hello,
Could this be installed on 2 pi zeros and have them monitor a pi4 that
is playing.
So maybe one shows by meters and one shows spectrum analyzer
bengaldave's Profile:
I have trouble using LMS Monitor using along with 3.5 inch TFT.
everytime I start LMS Monitor. MY LCD goes white but OLED display
LMSMonitor. I want to use both LCD for jivelite screen and OLED for
LMSmonitor.
I tried using command sudo ./lmsmonitor --name "piCorePlayer" -D19 -R22
-C24 -o6
Any updates, would love to have this working
sandbagger's Profile: http://forums.slimdevices.com/member.php?userid=70654
View this thread: http://forums.slimdevices.com/showthread.php?t=111790
Hi,
Does LMS monitor support SSD1351 128x128 OLED screens?
sh1ntomi's Profile: http://forums.slimdevices.com/member.php?userid=70545
View this thread: http://forums.slimdevices.com/showthread.php?t=111790
shunte88 wrote:
> ... I'll be pullling the updated graphical engine into the trunk by the
> weekend ...
Okay, six weeks have passed since then. I think there has been no update
yet.
When will the support for the new OLED displays come?
Best regards
PiPlayer
shunte88 wrote:
> I'm back into the code after a couple of months fighting fires in the
> day job, 80hr+ 7 day weeks so not much time for anything other than
> catching up on sleep ...
I figured you were heavily involved in your work. That's why I didn't
want to stress you out. I'm glad you're
MrD wrote:
> Would love to see an update to the code if only a branch.
I'm back into the code after a couple of months fighting fires in the
day job, 80hr+ 7 day weeks so not much time for anything other than
catching up on sleep
I'll be pullling the updated graphical engine into the trunk by
Would love to see an update to the code if only a branch.
-MrD
===
3 PiCore Players
1 Transporter (dead)
2 Squeezebox v3 (1 dead, 1 resurrected)
Linux x86-64 SlimServer 8.1.1
MrD's Profile:
PM sent
Thanks
psketch wrote:
> pm me your email and I'll send it all over
sandbagger's Profile: http://forums.slimdevices.com/member.php?userid=70654
View this thread:
sandbagger wrote:
> That will be perfect for now.
> yes I have the EVO SABRE Balanced DAC
> yea, directions/files would be a lot of help, to be honest I have
> forgotten more than I ever knew about linux :P
> I have been using PicorePlayer for a while now with just a 9038 or the
> AK4493 DAC
That will be perfect for now.
yes I have the EVO SABRE Balanced DAC
yea, directions/files would be a lot of help, to be honest I have
forgotten more than I ever knew about linux :P
I have been using PicorePlayer for a while now with just a 9038 or the
AK4493 DAC hats but wanted balanced
would
sandbagger wrote:
> any updates?
>
> just got my Audiophonics dac up and running on PiCore and would love to
> get the 2ndary screen running
>
> Thanks
Depending on which audiophonics dac you're talking about, I built an
extension for pcp for the 'EVO-Sabre'
any updates?
just got my Audiophonics dac up and running on PiCore and would love to
get the 2ndary screen running
Thanks
sandbagger's Profile: http://forums.slimdevices.com/member.php?userid=70654
View this thread:
shunte88 wrote:
> ...
> implementation of addition OLED support inclusive grayscale 256x64
> SSD1322 is almost there, driver 100% functional and blindingly fast ...
>
> ...
> I'm shooting for the end of month to release the update ...
Is there already a release date planned for the new
Hi,
I'm trying to restart this project, but I switched over exclusively to
Archlinux.
I tried the binaries and they gave out. Would I be able to compile and
get it working on Archlinux or it's a fruitless effort?
Any tips to get this working? I have a arduino spi o1, ssh o7 and a i2c
o6 working.
Alas my peepers dont work as well and 2.42 inch screen would be
desirable.
For the life of me i cannot get the ssh1309 working, both i2c or spi. I
bought a second thinking i burned out the first one, using
Looking forward to the updates!
-MrD
===
3 PiCore Players
1 Transporter (dead)
2 Squeezebox v3 (1 dead, 1 resurrected)
Linux x86-64 SlimServer 8.1.1
MrD's Profile:
apologies for the radio silence my new job is taking much of my time,
baby needs new shoes and all that...
implementation of addition OLED support inclusive grayscale 256x64
SSD1322 is almost there, driver 100% functional and blindingly fast
given this introduced a lot of layout change with
Any updates on this?
-MrD
===
3 PiCore Players
1 Transporter (dead)
2 Squeezebox v3 (1 dead, 1 resurrected)
Linux x86-64 SlimServer 8.1.1
MrD's Profile:
@luc apologies really slammed with work so trying to catch up a little
the operation you described is as expected
the sluggish VU's is down to a bug that has been resolved but has as of
yet not been deployed
use the downmix switch on the command as the single VU operates
correctly.
bit
Nice work! I just tested this morning, plug and play ready :-)
I have a couple of questions.
My setup is a pi3B, wifi, picoreplayer, jivelite, official pi 7" display
and allo boss DAC 1.2
Generic 1.3" OLED I2C and I plugged them on sda/SCL/vcc/gnd GPIO hat
from the DAC.
I use this simple
Hello, I'm trying to get the AZDelivery 1.3 128x64 OLED SH1106 Chip
working on my Picoreplayer.
It works on an Arduino.
I followed the instructions from shunte88.
Installation and start run without errors, but the display does not
show.
Maybe someone can help me, thank you
shunte88 wrote:
> I picked up the case on fleaBay for cheap, shipped from China so a few
> weeks in transit these days
>
> I then used Frontpanel Express for the CNC work - front and rear panels
>
> Audiophonics and DIYAudio have similar cases, very bare bones and you
> don't need to spend a
I picked up the case on fleaBay for a cheap
I then used Frontpanel Express for the CNC work - front and rear panels
Audiophonics and DIYAudio have similar cases, very bare bones and you
don't need to spend a ton - I'm betting t'zon, Alibaba, etc have good
choices too
That was 6-7 years ago
Excellent!
Quick question, the aluminum case on the github readme file... did you
cnc that or buy, where did you get it from?
Second, I did get code working in my setup, using Pi OS to compile.
I did spend more time reading the code and reviewing the server
interfaces.
I think passing in
Absolutely, I'll add it for the next release
Update on the next version:
I've spent a good bit of time optimizing the codebase, as part of the
SSD1322 implementation I've taken the route of reworking much of the
visualization processes.
VU meters as an example now constitute a single routine
Any chance we could get a command line parameter to pass in the LMS IP?
Instead of auto-discovery? My LMS is on a different subnet from the
wifi network.
If not ... I will setup a cross compiler and see about adding myself.
-MrD
===
3 PiCore Players
1 Transporter (dead)
2
jasc wrote:
> Hello, did you ever manage to get Slimmer to work on your 16x2 Display?
>
> Best,
> jasc
Hi, Unfortunately I did not. As others did mention there are some things
missing or have wrong versions.
Not having the time nor the knowledge, or the time to gain the
knowledge, I gave up,
cortegedusage wrote:
> @shunte88 Thank you for the hint of using slimmer, I didn't find it my
> self. I will try it.
>
> Thank you,
>
> Dennis
Hello, did you ever manage to get Slimmer to work on your 16x2 Display?
Best,
jasc
audio chain: 'raspberry pi 4b 8gb'
thejeko wrote:
> Hello everybody,
> after a couple of days of full immersion in this project and after
> having read all the messages and tried practically everything I have
> read, I have to annoy you because some things just do not get there.
>
> 1. How do I increase the fluidity and
Hello everybody,
after a couple of days of full immersion in this project and after
having read all the messages and tried practically everything I have
read, I have to annoy you because some things just do not get there.
1. How do I increase the fluidity and sensitivity of the vu meter, when
I
shunte88 wrote:
> different display technologies LCD/Matrix and OLED; and a totally
> different display paradigm at that
> there's a solution called slimmer that works with LCD 16x2 screens -
> check the forum
> I have 16x2 as a TBD but its not on the horizon as yet
> The unit below the OLED
different display technologies LCD/Matrix and OLED; and a totally
different display paradigm at that
there's a solution called slimmer that works with LCD 16x2 screens -
check the forum
I have 16x2 as a TBD but its not on the horizon as yet
As of *26-Feb-2021* my digitized collection is
cortegedusage wrote:
>
> I see you've got plans to get the raspdac mini v1 16x2 display to work,
> I believe this is the same display.
> What can I do to get it to work?
>
I've got it too! Never found a way to get the display work with
piCorePlayer. It would cool to have it working!
Hi there,
I found this solution, and I was wondering what would it take to get it
to work with a 16x2 display?
I've got one of these (
https://www.audiophonics.fr/en/network-audio-players-raspdac/audiophonics-raspdac-kit-diy-network-player-raspberry-pi-20-dac-sabre-v3-p-10384.html)
lying
You have tested Allo Boss already with this display?
Anyway, happy for now. Will have a eye on this during next builds.
Aki7's Profile: http://forums.slimdevices.com/member.php?userid=67596
View this thread:
the monitor does not interact with the DAC in any way
PCM5122 is a pretty common chip
I've used a dozen or so DAC's, I would count them but I'd like to avoid
the feeling of shame :p, over the years and none have presented a
problem
Maybe you were unlucky and picked up a defective unit
As of
Finally found a stable working solution:
*ES9023* DAC is working fine with LMSmonitor and SH1106 _ SSD1306 128x64
I2C-Modul. No more several start/stops needed on soft power off/on.
*Allo Boss *seems to interfere on I2C bus in combination, maybe all
DAC's with this *PCM5122* chip or driver,
sounds like you've got everything setup correctly, fully describing the
startup sequence
you've repeated a couple of parameters, if they're switches they can
flip the functionality
simplifying you command string
make sure you don't have a monitor running, give it the kill command
twice to
Hello,
I have been following this project with interest for a long time. I
appreciate all the effort put into it.
I have had success connecting to my LMS and generating the "splash"
screen on my oled. Im not able to reproduce when it seems to be
visualizing the data. I have changed the ALSA
ok, thxs.
the last audio project took a lot out of me so going to take a break.
i'll try out the non-glass at the end of march when i start new project.
i'm already designating a space for this OLED in my build, so crossing
fingers.
i'll report back if it works (hopefully SPI 4-wire).
both of those have well supported drivers and work out of the box
As of *16-Feb-2021* my digitized collection is (25236 hours 47 minutes)
+ (49 seconds) or
2.879[/B] YEARS IN DURATION
RANDOM CONTINUOUS PLAY WOULD REALLY ANNOY THE NEIGHBORS...
DIGITIZED THUS FAR:
[B]TOTAL TRACKS: 163,904
That's a good point. There is a glass version and a non-glass version.
I don't mind getting the non-glass version if there is a higher power
requirement for the glass.
I also noticed it's SSD1309 now as before it was SSD1306:
shunte88 wrote:
> 12V would be surprising; 3V3 and 5V are the usual
> There may be hardware that boost converts to 12V under the hood but not
> something you'd supply directly
> I've 20-30 OLED of various sizes and flavors and all of them conform to
> the 3V3/5V input
Yes but you probably
12V would be surprising; 3V3 and 5V are the usual
There may be hardware that boost converts to 12V under the hood but not
something you'd supply directly
I've 20-30 OLED of various sizes and flavors and all of them conform to
the 3V3/5V input
As of *15-Feb-2021* my digitized collection is
shunte88 wrote:
> Release 0.4.72 inclusive of updates to the binary has been uploaded to
> the repo
>
> 'LMSMonitor 0.4.72' (https://github.com/shunte88/LMSMonitor)
>
> This is a maintenance release for the most part
>
> The intermittent memory reallocation abend has been resolved
>
> Lots
Thanks shunte88.
I'll skip gomonitor for now. Just need the basics.
I gave up on the project that I initially ordered OLEDs for... It was
just too bulky.
The OLED is too nice to let it sit around, so I was able to get it
working with iPeng.
So barebones A+ stream to iPeng playback.
gomonitor wraps the lmsmonitor call for ease of use
it really just ensures the environment is ready, kills any prior
versions that may be running and works out the name of your pCP setup
I deploy it as a helper or starter script for folks to use
if you're happy to roll your own, and from your
Hi.
Is gomonitor still a thing? Every attempt including latest build, it
parses a lmsmonitor string for me to use. No way to run gomonitor, just
pushes me towards lmsmonitor.
I can successfully run lmsmonitor -o7 on every attempt at the console,
but once I copy and paste into tweaks I get
Release 0.4.72 inclusive of updates to the binary has been uploaded to
the repo
'LMSMonitor 0.4.72' (https://github.com/shunte88/LMSMonitor)
This is a maintenance release for the most part
The intermittent memory reallocation abend has been resolved
Lots of minor tweaks -non-functional-
Thanks. Ended up wiring was correct.
I have up on the 1.3" and swapped with the .96". First try and it
worked.
Will experiment again on Sunday and hopefully return the defective 1.3"
Monday.
Cheers
LiFePO4's Profile:
this is indeed SPI device so -o7 is what you'd want and its fully
supported by the OLED library
you can override the SPI pins via the command line or wire with the SPI0
pi gpio mapping, see here:
https://pinout.xyz/pinout/spi
alternatively you can switch to the i2c interface
Code:
No luck on my first attempt. If anyone can spot a misstep pls point
out:
I'm using Waveshare SH1106:
https://www.waveshare.com/1.3inch-oled-b.htm
Wiring:
1 VCC Power positive (3.3~5V power input) [GPIO 3.3V]
2 GND Ground [GPIO GND]
3 NC NC
4 DIN Data
shunte88 wrote:
> what you've posted looks good - nothing out of the ordinary
>
> did it lockup?
>
> if so what did you see with the logged output?
>
>
Yes. Very easy to reproduce. When I start playing a track it freezes
now!
2021-01-31 08:18:07 :: src/lmsmonitor.c-1029 : isRefreshed
I'm also very interested in the idea of the EVO Sabre as a replacement
for my venerable Transporter. As you say, it's WIP, but in the mean
time, I wondered how you found the EVO Sabre from a SQ perspective?
psketch's
I've just tried running piCorePlayer 7.0 on the EVO-Sabre Dac. Out of
the box it worked fine after selecting the Audiophonics iSabre Q2M as
audio output. The volume control on the DAC works, as do the Volume Up
and Down buttons on the remote control - but of course there is nothing
being
what you've posted looks good - nothing out of the ordinary
did it lockup?
if so what did you see with the logged output?
was an exception thrown or did it appear to be working without issue?
I'm still trying to hit the perfect storm, conditions that throw an
abend; taking a good bit of time
shunte88 wrote:
> -V on the monitor not squeeze
>
> you need to run the monitor manually so you can observe and capture the
> logging
>
tc@piCorePlayer:~$ sudo /mnt/mmcblk0p2/tce/lmsmonitor --name
"piCorePlayer" -k -w -c -rixv --meter "rn" -x 0x3d -c -f 7 -z -w0 -db
-V
OLED Mode
-V on the monitor not squeeze
you need to run the monitor manually so you can observe and capture the
logging
I'm running diagnostics now inclusive memory checks
these things take time it needs to hit the issue when a combination of
events occurs
I've gone with a new tool so took a hit with
shunte88 wrote:
>
> have you run with -V - what does the monitor "-think-" its doing?
>
What do you mean?
Putting: -V in Squeezelite Settings -> Various Options?
seekasoul's Profile:
i have two devices running 24/7 with no ugliness, one runs with weather
and the other is pretty much default setting; there's another 3 setups
but they're in other parts of the house and not monitored - no
observable issues there though
a freeze after 10 minutes I've never seen
have you run
shunte88 wrote:
>
> i added additional safety code for the realloc and those changes are in
> the current available build
Just uploaded latest build, but after playing about 10 min with airplay
the clock display is already frozen!
No blinking ":" beetween hour and min...
It's very annoying.
sounds like its hitting a resource issue - memory allocation or
something else that's causing an abend
on exit it should be clearing the screen so maybe it is literally
getting stuck
I've seen that type of behavior with the JSON scrape of weather and LMS
status/details
hits an invalid linked
shunte88 wrote:
> how long is a piece of string? :p
>
> not sure what you mean by stuck
> is the monitor freezing?
> are you referring to the colon flash not being bang on the second?
>
> a bit more detail...
The monitor freeze with the time stuck at random hour:min displayed.
Then only a
how long is a piece of string? :p
not sure what you mean by stuck
is the monitor freezing?
are you referring to the colon flash not being bang on the second?
a bit more detail...
As of *25-Jan-2021* my digitized collection is (25092 hours 53 minutes)
+ (54 seconds) or
2.863[/B] YEARS IN
Why the time get stuck so easily on the display?
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View this thread: http://forums.slimdevices.com/showthread.php?t=111790
shunte88 wrote:
> @LiFePO4
>
> with the deskpi Pro I routed a channel then slotted the 128x32 into it,
> had I been careful that should have been all I needed but ended up using
> some damping material to hold it secure and reduce the light bleed too
>
> easiest thing I've found for screw
Lot of confusion :-)
I offered the code, when there is any interest. You are interested, so
here is the code with the lmsmonitor handling:
Code:
#!/bin/sh
#
@LiFePO4
with the deskpi Pro I routed a channel then slotted the 128x32 into it,
had I been careful that should have been all I needed but ended up using
some damping material to hold it secure and reduce the light bleed too
easiest thing I've found for screw mounts is to solder the unit to
hi @Aki7, what I meant was remove the -K or --powersave so you don't
trigger the power save on the OLED and stick with your script that does
your own power down.
I could have sworn you also asked about an API call you found in the
code, at least I think you did
I reviewed the deployed script
shunte88 wrote:
> @LifePO4
>
> I think its just a typo but go for the 128x64 - the monitor fully
> supports this screen dimension
>
> note OOTB = Out Of The Box - works without issue
I ended up only ordering the two safe OOTB choices.
There were no mounting holes on the 128x32, so
shunte88 wrote:
> @Aki7 - very odd
> this is a nice to have but I'll keep poking at it to see where it could
> be going awry - until I do remove the argument from your call
> that extra line in the script controls the mute/unmute on one of my amps
> - it shouldn't be in the deployed script so
@LifePO4
> Okay, thanks. I won't take any risks with the 1.5Inch and take a small
> risk with a 128x32 (SSD1306):
>
I think its just a typo but go for the 128x64 - the monitor fully
supports this screen dimension
you can get the 128x64 up to 2.4 inches (diagonal) - see the main
picture in the
shunte88 wrote:
>
> @LiFePO4
>
>
> The SSD1306 and SH1106 are fully supported and work OOTB
>
> The grey scale and color aren't on the radar, although 1327 should be a
> quick tack on top of the 1322 implementation
>
> I've both of those devices but no plans for the color 128x128 - I'm
>
@Aki7 - very odd
this is a nice to have but I'll keep poking at it to see where it could
be going awry - until I do remove the argument from your call
that extra line in the script controls the mute/unmute on one of my amps
- it shouldn't be in the deployed script so remove it
I'll be pushing an
0.96inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SSD1306
https://www.waveshare.com/product/displays/lcd-oled/lcd-oled-3/0.96inch-oled-b.htm
1.3inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SH1106
https://www.waveshare.com/1.3inch-OLED-B.htm
1.5inch OLED Module OLED White (16
verbose looks ok, but still the same results.
Soft power on, display stays black:
...
2021-01-14 20:43:16 :: src/lmsmonitor.c-1029 : isRefreshed
2021-01-14 20:43:16 :: src/lmsmonitor.c-1067 : activeScroller test
2021-01-14 20:43:16 :: src/lmsmonitor.c-1072 : display clock test
2021-01-14
just pushed an update
caught another edge case
some fixes in tag logic too - composer and quoted strings (JSON side
effects)
let me know how that looks
if still seeing odd behavior add the --verbose flag and post the output
cheers
As of *13-Jan-2021* my digitized collection is (25074 hours 42
Hi shunte88,
just tested the new version concerning the "powersave". Same behaviour
as in my last post '#206'
(https://forums.slimdevices.com/showthread.php?111790-ANNOUNCE-LMS-Monitor-2020=1004081=1#post1004081).
Aki
latest pushed to github inclusive binary updates
hopefully all bases are covered
have at it
I have to admit I don't think I've used the power button the entire time
I've run LMS - 13 years or so?
I actually added the clock and weather because my devices are always on
I can't actually remember
those issues are sorted but looks like the visualization mode is a tad
problematic - multi-threading bites once again :mad:
i'll keep you posted - look for updates in the AM (US EST)
As of *08-Jan-2021* my digitized collection is (25049 hours 16 minutes)
+ (43 seconds) or
2.858[/B] YEARS IN
so scenario #1 you're starting with the streamer in power off state
that's is something I don't think I tested - logically shouldn't change
anything but obviously not the case
the partial clear I thought I'd caught all edge cases during testing -
will review the "refresh" flagging and see what
Hi Shunte88,
thanks for your support.
---
Starting lmsmonitor in player "off" State:
tc@pcVV:~$ sudo killall lmsmonitor
killall: lmsmonitor: no process killed
tc@pcVV:~$ PNAME=`cat /usr/local/sbin/config.cfg | grep
shunte88 wrote:
> @Aki7 I've quite the collection of DAC's I upgrade at least one device
> once a year and I've never had an issue
>
> Not sure whats going on with your setup.
>
> The monitor does not interact with the DAC in anyway shape or form, and
> it doesn't care if a DAC is attached or
@Aki7 I've quite the collection of DAC's I upgrade at least one device
once a year and I've never had an issue
Not sure whats going on with your setup.
The monitor does not interact with the DAC in anyway shape or form, and
it doesn't care if a DAC is attached or not, nor if a hat, USB flavor,
shunte88 wrote:
> I'll be working on supporting the latest Audiophonic DAC which supports
> dual displays as well as being a stellar DAC
>
> 'AUDIOPHONICS EVO-SABRE Balanced DAC 2x ES9038Q2M USB RPI SPDIF BT / XLR
> RCA'
>
Hi shunte88,
thanks for the new version. Just tested the new powersave feature
without success. Screen stays on last state on "power off". When soft
powered on again screen stays "freezed".
This is with attached DAC. Former tests showed different behavior when
lmsmonitor is operated with or
the power save function has been added to the monitor and the repo
updated inclusive of a binary refresh
to initiate power save mode use the added command line switch
Code:
--powersave
alternatively provide the short *K* switch
if the player
apologies I've been looking for a new job and this has consumed much of
time these last months
in no particular order
@Aki7 - power-off/sleep mode of the player does not trigger any
additional functionality. I'll look at adding a configurable sleep mode
that will sleep in lockstep with the
@shunte88, please help me.
i have the raspdac mini with piCorePlayer v7.0.0b6, but i don't know how
to enable the oled screen.
please help me :(
matteo92li's Profile: http://forums.slimdevices.com/member.php?userid=71194
Hi shunte88,
... struggeling with the "soft power off". Is there any expected
behavior of lmsmonitor when the player is set to "off"?
(and set to "on" later).
Aki
Aki7's Profile:
Is there a way to shutdown the screen, stop lms monitor, without shuting
down picoreplayer?
Thanks
davidscrat's Profile: http://forums.slimdevices.com/member.php?userid=70499
View this thread:
Is everyrhing ok to install lms monitor on the pi4 raspdac mini with
9038 q2m dac
Is there any "tutoriel", cause i am a beginner.
I have lms 8.0 and pcp 6.0.
Thanks
davidscrat's Profile:
shunte88 wrote:
> I'll get a system setup and poke around some
> Are you setup on Pi3 or Pi4?
Rpi 4 and DAC is I2S.
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
View this thread:
I'll get a system setup and poke around some
Are you setup on Pi3 or Pi4?
As of *17-Nov-2020* my digitized collection is (24770 hours 5 minutes) +
(22 seconds) or
2.82576072[/B] YEARS IN DURATION.
DIGITIZED THUS FAR:
[B]TOTAL TRACKS: 157,965
TOTAL ALBUMS: 14,448
TOTAL ARTISTS: 20,544
TOTAL
shunte88 wrote:
>
> let me know if you do hit snags, I have the code open today so I'm ready
> to start any type of review
Unable to make it work with pCP 7.0.0 Beta, can you help me into doing
it?
seekasoul's Profile:
hi @seekasoul
you won't need the dev package - you only need that to look for your i2c
address
you should be able to get going by following the install instructions
and skipping that step
configure pCP data sharing
do the wget step
then use the same command line as you used before to spin up
Any chance to use it with 7.0.0 Beta version?
*i2c-tools-dev.tcz* seems no more downloadable as an extension on the
repositories...
Let me know.
seekasoul's Profile: http://forums.slimdevices.com/member.php?userid=69788
HI,
As I said previously, I have never seen a SSD1322 driver chip Oled
using I2C. The Oleds with 0ohm links to change between I1C and SPI
normally use the SSD1305 / SSD1309 series ICs. My 3.1" Oled with
SSD1322 does not have any 0ohm links and cannot be converted to I2C
so I just checked
the SSD1322 can operate in both SPI and IIC modes, moving a couple of 0R
resistors on the driver board sets the mode
I have SPI functional on a standalone device and I'm working to get the
code into the Adafruit library, actually code is in there but not tied
in 100%
GPIO configuration is
1 - 100 of 284 matches
Mail list logo
