SpinalWatch - Socoder

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|676\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Off Topic -> SpinalWatch
Page : 1 2 3 4 5 6 7 8 Prev 9 10 Next
Mon, 14 Aug 2023, 15:30
spinal	Got a work around, I'll have to check it every half hour though and copy+paste into a doc. Â¯\_(ãƒ„)_/Â¯ -=-=- Check out my excellent homepage!
Mon, 14 Aug 2023, 15:33
Jayenkai	Well, if that's workable. Might be tricky overnight, though. -=-=- ''Load, Next List!''
Mon, 14 Aug 2023, 20:14
Kuron	You can do it, we have faith in you!
Tue, 15 Aug 2023, 00:46
spinal	Well, if that's workable. Might be tricky overnight, though. If I remove all the power saving code, then it only gets a couple of hours battery, especially if I stick a couple of LED's on there also. -=-=- Check out my excellent homepage!
Tue, 15 Aug 2023, 09:32
spinal	inline void drawPixel(int x, int y, uint8_t color){ if(x<0 \|\| y<0 \|\| x>=WIDTH \|\| y>=HEIGHT) return; uint16_t x8 = x>>3; if(color > 1){ color = GreyPattern[(x&1)+2(y&1)]; } if (color){ sBuff[x8 + y WIDTH_8] \|= (128>>(x&7)); }else{ sBuff[x8 + y * WIDTH_8] &= ~(128>>(x&7)); } } --v Something is up with my pixel function, not 100% sure what it is, but it's not rendering 'black' pixels. I think the screen is inverted compared to most monocheomr screens, so White = 0 and Black = 1 (I think). So perhaps this... if (color){ sBuff[x8 + y * WIDTH_8] \|= (128>>(x&7)); --v Isn't doing what I think it is? \|edit\| Forget that, I'll leave it there to show how stupid I was. The problem was in my sprite drawing function, I forgot I attempted to add transparency a couple of days ago. -=-=- Check out my excellent homepage!
Tue, 15 Aug 2023, 09:54
Jayenkai	I'm sure there's a reason for it, but what's with the or and anding when setting the stuff value? Should you not just be setting it directly to the value? \|edit\| LOL, ok! \|edit\| -=-=- ''Load, Next List!''
Tue, 15 Aug 2023, 12:19
spinal	bah, it's crashing more than ever now. Time to start over. -=-=- Check out my excellent homepage!
Tue, 15 Aug 2023, 12:20
Kuron	Damn. Yeah, sometimes a fresh start is best. You can do this, I know it!
Wed, 16 Aug 2023, 10:22
spinal	Reverting back to version 1, just before switching to gadgetbridge for the notifications. First I'll get it to connect, then accept the time etc. and go from there again. -=-=- Check out my excellent homepage!
Wed, 16 Aug 2023, 10:34
Jayenkai	Poor Spinal Good luck
Wed, 16 Aug 2023, 10:40
spinal	However, I did just notice that I wasn't freeing some pointers after use, perhaps that's what was causing the random crashes.... -=-=- Check out my excellent homepage!
Wed, 16 Aug 2023, 11:17
Kuron	Oy vey! That might be enough to do it.
Wed, 16 Aug 2023, 11:26
Kuron	Spinal don't feel bad. Even the big boys are having "time issues".
Fri, 18 Aug 2023, 01:36
spinal	OK, Started from scratch, First I got the BLE code working and connecting, no problems yet. Then I added all of the power saving code, one item at a time and still working (power at 1.9mA). Left it running for a while, no crashing, sent multiple notifications, still no crashing. Switched to Putty instead of the Arduino Serial monitor because it supports unicode formatting commands (such as colours and clearing the screen) 10:06:28 Friday 2023-08-18 [Notifications [ -------------------- Gadgetbridge Test notification This is a test notification from Gadgetbridge -------------------- Gadgetbridge Test notification This is a test notification from Gadgetbridge -------------------- Hello. Your Login authentication code is 123456. -------------------- Messages Login Authentication Hello. Your Login authentication code is 123456. --v I noticed that txt messages come through twice, once without any sender info, then again with full info. I guess I need to put a check for that once everything is working correctly. Todays task - get the screen working again, perhaps redo all of the pixeling code from scratch as there was some weirdness going on with that last time. But first I'll leave it running for a few hours and keep an eye on the time and crashing and stuff. -=-=- Check out my excellent homepage!
Fri, 18 Aug 2023, 01:51
Jayenkai	Fingers crossed!
Fri, 18 Aug 2023, 10:23
Kuron	You can do it!
Fri, 18 Aug 2023, 10:32
spinal	So far so good. I've started adding the screen functions back and it's not crashed yet. Ble is still working, slightly slower for some reason, although the power saving 'deep sleep' seems to be working fine and not killing the Ble like it did last time. -=-=- Check out my excellent homepage!
Fri, 18 Aug 2023, 10:48
Kuron	Keep us posted, please.
Fri, 18 Aug 2023, 14:22
spinal	Added the screen functions back, reverted to the original 'send full screen' rather than only the dirty lines, for some weird reason it isnt dirtying the lines properly and I can't be bothered to find out why. -=-=- Check out my excellent homepage!
Fri, 18 Aug 2023, 14:59
Jayenkai	Nothing dirty? That's 'cos your code is so perfectly clean! -=-=- ''Load, Next List!''
Sat, 19 Aug 2023, 02:49
spinal	It's weird, I would manually force the buffer and the copy to be different, but then it would only decide that where I'd put the text was different and the background wouldn't be. I was calling clearSceeenBuffer() in my setup, so I'd expect the first frame to render fully, but nope void clearScreenBuffer(){ // clear the gfx buffer. memset(sBuff, 0x00, 3024); // WIDTHHEIGHT/8 memset(bBuff, 0xAF, 3024); // Make sure the back buffer is different from the front buffer. } void writeScreen(){ // Before updating screen, compare to previous frame and only update differences. for(int y=0; y<168; y++){ dirtyLine[y]=0; // mark the line clean int offset = 18 y; for(int x=0; x<18; x++){ if(bBuff[offset+x] != sBuff[offset+x]){ dirtyLine[y] = 1; // if ANY byte on the line is different, mark it fro re-drawing } bBuff[offset+x] = sBuff[offset+x]; // copy front buffer to back buffer } } uint8_t fullLine[320]; // 16 lines of screen data uint16_t index = 0; // index of buffer to read from digitalWrite(CS_PIN, HIGH); SPI.beginTransaction( SPISettings(8000000, LSBFIRST, SPI_MODE0) ); // 8mhz as fast as the nrf52840 will go, but that's 100fps, so that's OK. // add vCom to the 'send data' command SPI.transfer(_SHARPMEM_BIT_WRITECMD \| (vCom ? _SHARPMEM_BIT_VCOM : 0)); // The important bit, check if a line is dirty and add it to the 'fillline' buffer to be sent. Once the buffer has 16 lines in it, send it. for(uint16_t line=1; line<=168; line+=16){ uint16_t bufferIndex = 0; for(uint16_t subLine=0; subLine<16; subLine++){ uint16_t realLine = line + subLine; if(realLine > 168) break; // Don't go over the total number of lines if(dirtyLine[realLine-1]){ index = (realLine - 1) * 18; fullLine[bufferIndex] = reverse_byte(realLine); for(int x=1; x<19; x++){ fullLine[bufferIndex + x] = sBuff[index + x - 1]; } fullLine[bufferIndex + 20] = 0x00; bufferIndex += 20; } } if(bufferIndex > 0){ SPI.transfer(fullLine, bufferIndex); } } SPI.transfer(0x00); digitalWrite(CS_PIN, LOW); vCom ^= 1; } --v \|edit\| Something I should have thought of, sleeping for a second at a time, makes the buttons unresponsive. However, I get one free question per day on gpt-4, so I let AI add interrupts to be sleep and button handeling. Now, instant buttons presses even when sleeping! -=-=- Check out my excellent homepage!
Sat, 26 Aug 2023, 04:30
spinal	Got wordwrap sort of working, but for some reason its updating the global textY position wrongly. \|edit\| Why is this 144x186 image not displayed at full size, even when clicked on? -=-=- Check out my excellent homepage!
Sat, 26 Aug 2023, 04:54
Jayenkai	I'm getting a 144x168 image. If it's meant to be 144x186, email me the original image and I'll have a poke around to try to figure it out. -=-=- ''Load, Next List!''
Sat, 26 Aug 2023, 05:02
spinal	It saves as 144x168, it copy+pastes as 144x168, it only doesnt display in the post as 144x168, it displays as 130x151. -=-=- Check out my excellent homepage!
Sat, 26 Aug 2023, 05:12
Jayenkai	shrugs Not seeing it. Are you sure you haven't zoomed out SoCoder a bit in your browser or something? Hit Ctrl+0. -=-=- ''Load, Next List!''
Sat, 26 Aug 2023, 05:14
spinal	Bloody hell, that was it.
Page : 1 2 3 4 5 6 7 8 Prev 9 10 Next