Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ledmap.json interfering with 2D set-up #3926

Open
1 task done
spiro-c opened this issue Apr 23, 2024 · 9 comments
Open
1 task done

Ledmap.json interfering with 2D set-up #3926

spiro-c opened this issue Apr 23, 2024 · 9 comments
Assignees
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master

Comments

@spiro-c
Copy link

spiro-c commented Apr 23, 2024

What happened?

I have setup of remapped 16x16 2D matrix to 32x8 for my custom display using ledmap.json file if the ledmap.json file is present the 2D settings are not loaded from cfg.json you need to go to 2D settings and resave the settings already present so the 2d output can be start sending effect

To Reproduce Bug

Create 2D matrix and remap the pixels using ledmap.json after reboot it will not display any 2d effect need to go in 2d settings and resave setting what are already set

Expected Behavior

Able to remap 2d matrix

Install Method

Self-Compiled

What version of WLED?

WLED 0.15.0-b3 (build 2404120)

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

---WLED 0.15.0-b3 2404120 INIT---

esp32 v3.3.6-16-gcc5440f6a2

arduino-esp32 v1.0.x


CPU:   ESP32-D0WDQ6 rev.1, 2 core(s), 240MHz.

FLASH: 4MB, Mode 2 (DIO), speed 80MHz.

heap 312356

JSON buffer allocated: 32767

PIN ALLOC: Pin 1 successfully allocated by 0x89 (137)

Registering usermods ...

heap 279520

Reading config

Reading settings from /wsec.json...

JSON buffer locked. (3)

JSON buffer released. (3)

JSON buffer locked. (1)

Reading settings from /cfg.json...

Removing all.

PIN ALLOC: Pin 2 successfully allocated by 0x82 (130)

Successfully inited strip 0 (len 256) with type 22 and pins 2,255 (itype 23). mA=55/850
PIN ALLOC: Pin 0 successfully allocated by 0x85 (133)

Starting usermod config.

JSON buffer released. (1)

heap 272144

Initializing strip

Loading custom palettes

Loading custom ledmaps

JSON buffer locked. (7)

Reading LED map from /ledmap.json

JSON buffer released. (7)

heap 271412

Usermods setup

heap 271412

Defaulf WiFi used.

initServer

heap 216956

Initial connect or forced reconnect.

Defaulf WiFi used.

initConnection() called.

Access point disabled (init).

Connecting to Network...

Loop took 714ms.
Usermods took 0ms.
Strip took 1ms.


Connected! IP address: 192.168.10.195

Init STA interfaces

mDNS started

send NTP

NTP recv, l=48

Local time: 12:59
WS FileRead: /index.htm

JSON buffer locked. (17)

JSON buffer size: 8071 for request: 6
JSON content length: 5465

JSON buffer released. (17)

JSON buffer locked. (17)

JSON buffer size: 4807 for request: 8
JSON content length: 2190

JSON buffer released. (17)

JSON buffer locked. (17)

JSON buffer size: 2501 for request: 3
JSON content length: 1365

JSON buffer released. (17)

WS FileRead: /skin.css

Not-Found HTTP call: /presets.json

WS FileRead: /presets.json

WS client connected.

JSON buffer locked. (12)

JSON buffer size: 2497 for WS request (1366).
heap 181916

Sending WS data to a single client.

JSON buffer released. (12)

JSON buffer locked. (11)

JSON buffer released. (11)

JSON buffer locked. (12)

JSON buffer size: 2497 for WS request (1366).
heap 183784

Sending WS data to a single client.

JSON buffer released. (12)

WS client disconnected.

settings resp0

settings resp10

Matrix ledmap:

   0,   1,   2,   3,   4,   5,   6,   7,   8,   9,  10,  11,  12,  13,  14,  15,  16,  17,  18,  19,  20,  21,  22,  23,  24,  25,  26,  27,  28,  29,  30,  31,

  32,  33,  34,  35,  36,  37,  38,  39,  40,  41,  42,  43,  44,  45,  46,  47,  48,  49,  50,  51,  52,  53,  54,  55,  56,  57,  58,  59,  60,  61,  62,  63,

  64,  65,  66,  67,  68,  69,  70,  71,  72,  73,  74,  75,  76,  77,  78,  79,  80,  81,  82,  83,  84,  85,  86,  87,  88,  89,  90,  91,  92,  93,  94,  95,

  96,  97,  98,  99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127,

 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159,

 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191,

 192, 193, 194, 195, 196, 197, 198, 199, 200, 201, 202, 203, 204, 205, 206, 207, 208, 209, 210, 211, 212, 213, 214, 215, 216, 217, 218, 219, 220, 221, 222, 223,

 224, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235, 236, 237, 238, 239, 240, 241, 242, 243, 244, 245, 246, 247, 248, 249, 250, 251, 252, 253, 254, 255,

JSON buffer locked. (7)

Reading LED map from /ledmap.json

JSON buffer released. (7)

Slow strip 29/23.
Writing settings to /wsec.json...

Anything else?

Work around is to upload ledmap1.json file and load from presets it will honour the remapped pixel data

Code of Conduct

  • I agree to follow this project's Code of Conduct
@spiro-c spiro-c added the bug label Apr 23, 2024
@blazoncek blazoncek self-assigned this Apr 23, 2024
@blazoncek blazoncek added the confirmed The bug is reproducable and confirmed label Apr 23, 2024
@blazoncek
Copy link
Collaborator

This will require the addition of "height" and "width" fields in ledmap.json.
Compatible with WLED MM.

blazoncek added a commit that referenced this issue Apr 23, 2024
@blazoncek blazoncek added the fixed in source This issue is unsolved in the latest release but fixed in master label Apr 23, 2024
@DarthWeber
Copy link

I added "height" and "width" fields in ledmap.json - but the issue is the same

@dosipod
Copy link

dosipod commented Apr 28, 2024

@DarthWeber Using ledmap.json ( which is the default ledmap ) is bad idea and caused us a lot of issues before version 15 . What you should do is use ledmap1.json to ledmap9.json . You can add height" and "width" fields if you like only if you are using MM else it is optional .
So using ledmap.json means if something is wrong with your custom map then that would mess with your unit setup and you have no way to go back to the default ledmap as you already set your map as default . Just do not do it

@blazoncek
Copy link
Collaborator

@dosipod height and width are required for 2D and are available in AC since the commit above (0.15.0-b3).

@dosipod
Copy link

dosipod commented Apr 28, 2024

I do not actually use ledmaps with 15 and only referring to the use of the default ledmap.json . I recall an issue in segmentation when "height" and "width" are used in ledmap and i hope that is not carried over .Ledmap name not changing should be next

@DarthWeber
Copy link

used ledmap1.json and referred it in the presets, this seems to work right.

Thanks all of you!

@spiro-c
Copy link
Author

spiro-c commented Apr 29, 2024

Did you use the latest build from 0_15 branch adding "height" and "width" to the ledmap.json is working there

@DarthWeber
Copy link

Did you use the latest build from 0_15 branch adding "height" and "width" to the ledmap.json is working there

I used 15.3 from this branch and added height and width - but same issue for me.

@blazoncek
Copy link
Collaborator

@DarthWeber please provide ledmap.json and cfg.json. I will also require boot debug dump from serial console, similar as @spiro-c provided above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug confirmed The bug is reproducable and confirmed fixed in source This issue is unsolved in the latest release but fixed in master
Projects
None yet
Development

No branches or pull requests

4 participants