ANNOUNCE: LMS Monitor 2020

[shunte88]

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

[Aki7]

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 20:43:16 :: src/lmsmonitor.c-1142 : clockPage
LMS:Player Powered ..: On
LMS:Playing .........: Yes
LMS:Time Played .....: 173.699988101959
2021-01-14 20:43:17 :: src/lmsmonitor.c-0397 : power test
2021-01-14 20:43:17 :: src/lmsmonitor.c-1029 : isRefreshed
2021-01-14 20:43:17 :: src/lmsmonitor.c-1040 : isPlaying
2021-01-14 20:43:17 :: src/lmsmonitor.c-0397 : power test
2021-01-14 20:43:17 :: src/lmsmonitor.c-1029 : isRefreshed
2021-01-14 20:43:17 :: src/lmsmonitor.c-1040 : isPlaying
2021-01-14 20:43:19 :: src/lmsmonitor.c-0397 : power test
2021-01-14 20:43:19 :: src/lmsmonitor.c-1029 : isRefreshed
...

[LiFePO4]

.

[LiFePO4]

.

[shunte88]

@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 updated archive shortly that removes that command
I'll keep you posted with progress

@LiFePO4

These two seem like safe choices:

0.96inch OLED (B)
1.3inch OLED (B)

0.96inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SSD1306

1.3inch OLED (B) OLED 128×64 3-wire SPI, 4-wire SPI, I2C SH1106

Any chance these will work in the near future?

1.5inch OLED Module OLED White (16 gray scale) 128×128 4-wire SPI, I2C SSD1327

1.5inch RGB OLED Module OLED 65K colorful 128×128 3-wire SPI, 4-wire SPI SSD1351

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 favoring a 240x240 version

There's a TODO section on the README and those have priority - its finding the cycles to make that happen especially when I have to redo the artwork too

I just got a couple of 128x32 that I've plumbed into a dekpiPro enclosure so I'd like to add a simple text scroller for that setup too, theres a git repo for that too - lots of fun routing and polishing acrylic on top of writing the software. Next step for this is to add a DAC or amp - I've several pi0 hats that are candidates.



art is also a hobby of mine so theres fun to be had designing the new setups
art on dribble
art on devianart
art on zazzle - t-shirts etc...

[LiFePO4]

.

[shunte88]

@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 README
The 'zon has those devices at reasonable prices 128x64

If you do want the 128x32 this is the device I have in the deskpi 2x 128x32 for under $10

the 128x32 for the deskpi is currently another project. I'm looking at popping a justBoom amp or IQAudio DAC into the mix soon, then a very much cutdown monitor will be ported over with a simple scrolling interface.
I have to open up the unit as the M.2 drive isn't being detected so I'm swapping it out for a cheap Kingston SSD
It'll make for a solid portable system
Its a nice enclosure for those interested but it does have some rough edges and its been a bit of a time-suck standing it up

note OOTB = Out Of The Box - works without issue

[Aki7]

@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 updated archive shortly that removes that command
I'll keep you posted with progress

What do you mean with "until I do remove the argument from your call" and "so remove it". Which argument?

I use the LMS "soft on/off" for powering on/off my aplifiers with relays to be as green as i can :-)

[LiFePO4]

@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 dealbreaker.

Look forward to trying out in a week...

[shunte88]

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 and couldn't find the call, and checking through the thread I'm not seeing the question so I do think I need some hot milk and a nap is likely overdue

apologies for any confusion

I'll keep picking at the power save and keep you posted should the veil lift and I discover the issue