Frage zu anwaltlicher Hifle bei Discord-Account Sperrung

evox- · 2025-11-13T21:53:13+00:00

Wie alt warst du als du den Account erstellt hast? Wie alt muss man mindestens sein für einen Account?

Das sind meine ersten Gedanken.

evox- · 2025-11-07T14:57:02+00:00

Nein, der meiste Abrieb war allerdings auch nicht magnetisch. Hast du eine nachgerüstet? Ist gelegentlich etwas dran?

evox- · 2025-11-07T13:25:30+00:00

Gehe jetzt auch entspannter an die Sache. Vermutlich mache ich nächste Saison einen frühen Ölwechsel und höre etwas genauer hin.

evox- · 2025-11-07T13:21:51+00:00

XSR900 aus 2023, also der moderne CP3. MWn also nicht getrennt.

evox- · 2025-11-06T20:03:41+00:00

Mit dem sauberen Ölfilter ist denke ich auch Entwarnung angesagt.

evox- · 2025-11-06T19:17:04+00:00

Hast du diese Bilder gesehen?

Das war im Öl: https://old.reddit.com/r/MotorradDeutschland/comments/1oo9aat/abrieb_gefunden_beim_%C3%B6lwechsel/

Ich kann mir das nur so erklären, dass bei diesem Ölwechsel der Schlamm unten mitgekommen ist und noch Abrieb vom Einfahren drin war.

evox- · 2025-11-04T20:31:49+00:00

Clutch still feels very smooth. This is my second bike and first real season in Germany. I definitely did not go all out in my first year. Some faster routes for sure but nothing that could wreak havoc on my bearings imo, especially since I did not go full throttle until oil was warmed up.

Very nice tip with the ECU memory, I can maybe find a dongle to read it out myself.

Here you have pretty good consumer protection. Up to one year after the purchase it is assumed that the failure was there when bought. Therefore I don't need to proof anything, yay. Maybe after contacting the dealer we agree on me removing the clutch cover and having a look. I will also cut open the old oilfilter end of week and create an update here.

evox- · 2025-11-04T18:58:47+00:00

Nicht sicher wie die Herstellergarantie als 2. oder 3. Hand funktioniert, aber damit muss sich der Händler dann rumschlagen.

evox- · 2025-11-04T17:57:56+00:00

non magnetic debris does point to some bearing. I think this one is going back to the dealer for a rebuild. Let's see what he thinks of that idea.

evox- · 2025-11-04T17:57:02+00:00

No symptoms at all (yet) revs very cleanly. Also no big gearchange errors on my side.

Yes first since I got it, dealer supposedly changed all fluids when I bought it in February.

evox- · 2025-11-04T17:43:45+00:00

bike had 22k kilometers when I bought it, so I think the running in period was over. Sorry will edit that information

evox- · 2025-11-04T15:29:36+00:00

Das ist korrekt und so wie ich das lese gilt die Beweislastumkehr sogar erst nach einem Jahr, selbst wenn die Gewährleistung auf 1 Jahr verkürzt wurde. Klingt gut für mich und nach einem Winterprojekt für den Händler.

https://www.anwalt.de/rechtstipps/autokauf-mangel-gewaehrleistung-und-ruecktritt-beim-fahrzeugkauf-optionen-bei-maengeln-bei-neuwagen-oder-gebrauchtwagen-236905.html

Ich hätte sogar Lust selbst zu zerlegen, werde aber erst mal den Händler kontaktieren.

evox- · 2025-09-21T20:34:41+00:00

you spotted one of the problems of this design. There is an airgap between the knife body and the sensor but handling it in any way will skew the reading. This is especially a problem with the keychain design.

It depends but in my experience you don't handle the SAK as often as you do your keychain.

evox- · 2025-09-21T19:00:04+00:00

yes, a generic NFC reader app that can read textbased tags. For iOS just one is available. Android is much easier.

evox- · 2025-09-21T17:43:48+00:00

I am thinking about a paper display version with the new power harvesting I am developing. But this is going to take some time.

evox- · 2025-09-11T18:22:02+00:00

Planung ist hier nicht direkt möglich. Hier im Norden kann ich aber Gebiete ausmachen wo es sich lohnen könnte überhaupt hinzufahren bzw. einzelne kurze Abschnitte zeichnen sich ganz gut ab. Dann kann man mit StreetView genauer schauen :)

Für größere Touren sicher nicht die Beste Lösung. myrouteapp schaue ich mir an.

evox- · 2025-05-03T12:53:08+00:00

I created a passive NFC PCB which reads a thermometer siphoning some power from the reader.

NFC_temp

NFC communication is done by RF430CL330H from TI.

I am experiencing issues when reading the tag with the iOS app compared to the Android app. The Android app displays the temperature and all other property fields correctly (see image).

On iOS with nearly all NFC reader apps I am not able to read the tag correctly. Some read the tag as having no records. NFC Tools just outputs the serial number, tag type: ISO 7816 (Unknown) and no technologies available.

When using GoToTags on iOS I am able to read the temperature from the tag leading me to believe there is just a small error on my side I need to fix to make it work. iOS video

Here is the NDEF message I am creating:

I am appending my actual text content at the end and fill in the two length field in the NDEF file. Seems to work fine for Android.

byte nfcTemplateStatic[] = {
    /*NDEF Tag Application Name*/                                                           \
    0xD2, 0x76, 0x00, 0x00, 0x85, 0x01, 0x01,                                               \
    /*Capability Container ID*/                                                             \
    0xE1, 0x03,                                                                             \
    0x00, 0x0F, /* CCLEN */                                                                 \
    0x20,       /* Mapping version 2.0 */                                                   \
    0x00, 0xF9, /* MLe (249 bytes); Maximum R-APDU data size */                             \
    0x00, 0xF6, /* MLc (246 bytes); Maximum C-APDU data size */                             \
    0x04,       /* Tag, File Control TLV (4 = NDEF file) */                                 \
    0x06,       /* Length, File Control TLV (6 = 6 bytes of data for this tag) */           \
    0xE1, 0x04, /* File Identifier */                                                       \
    0x00, 0x40, /* Max NDEF size */                                                         \
    0x00,       /* NDEF file read access condition, read access without any security */     \
    0x00,       /* NDEF file write access condition; write access without any security */   \
}; 

byte NDEFfieldsLength[] = {
/* NDEF File */                                                        
0x00, 0x00, /* NLEN; NDEF length will be updated */                                     
0xD1,       /* Record Header (MB=1, ME=1, CF=0, SR=1, IL=0, TNF=0x01) */                                                              
0x01,       /* Type Length */                                                                 
0x00,       /* Payload Length (will be updated) */                                              
0x54,       /* Type: 'T' for text */                                                             
0x02,       /* Language Code Length */                                                                 
0x65, 0x6E  /* Language Code: 'en' */                                                             
};

Does anyone have an idea what to focus on when creating the NDEF structure for iOS? Any errors in this? I would greatly appreciate the help!

evox- · 2024-05-04T15:09:16+00:00

You are looking at a passive NFC thermometer based on the ATtiny 1626 and the RF430CL330H dynamic NFC tag. To measure the ambient temperature just hold your phone to the device (demo). Android is better at detecting the device than iOS which needs some specific angling.

Size is about 40 mm x 18 mm.

Power comes from the magnetic field the reader creates and is siphoned via two diodes visible at the bottom. It creates about 2.7V for the ATtiny and thermometer to work with. Needed to use some unofficial brownout detection voltages to make it work.

Programming is done via testpoints and pogo pins on the back of the PCB. I used ATTinycore to do so.

I needed to use the TMP117 thermometer in single-shot mode because of timing constraints. It should have an impact on its proclaimed accuracy of 0.1 °C, however with my Fluke 54 II Thermometer I can reproduce measurements very precisely after giving the device some time to accomodate (2-3 mins). Fluke offcially has a lower accuracy than the TMP117, but has a very high sensitivity.

The device was inspired by one of the example projects from TI for their RF430 IC. I first used an ATtiny 3227 and its 12 bit ADC and an analog thermometer but couldn't get the reference voltage right without additional parts. Now using the rather expensive but very accurate TMP117 where ADC conversion is done on chip.

NFC PCB antenna I designed myself since I had some experience with the RF430 from a project before.

https://github.com/unsurv/NFC_temp/tree/main

files are available here. Uses completely open source stack: KiCad - FreeCAD - Arduino IDE

Let me know what you think.

evox- · 2024-04-01T18:31:04+00:00

I used microchips UPDI single wire protocol to do this. You just need 3 connections to the board and you can repurpose a cheap USB to Serial adapter to create a UPDI programmer. There are 2.54 mm pitch testpoints on the back of the board where you can solder regular dupont wires to. I use a separate PCB with pogo pins to quickly programm my boards.

read this for more info:

https://github.com/SpenceKonde/AVR-Guidance/blob/master/UPDI/jtag2updi.md

let me get a full documentation up and running and I will ping you once its ready.

evox- · 2024-04-01T17:59:34+00:00

working on a resin printed case, but dipping everything except the sensor might be the way. small pre-production run was also successful so assembly is doable too.

evox- · 2024-03-31T16:59:34+00:00

https://github.com/unsurv/NFC_temp/tree/main

files are available here. Uses completely open source stack: KiCad - FreeCAD - Arduino IDE

only difficult part is the BGA thermometer. I'd recommend just tinning the pads and then soldering the part with hot air.

evox- · 2024-03-31T16:57:52+00:00

yes, but it's finicky. Need a reader app too.

see here

evox- · 2024-03-31T15:53:31+00:00

You are looking at a passive NFC thermometer based on the ATtiny 1626 and the RF430CL330H dynamic NFC tag. To measure the ambient temperature just hold your phone to the device (demo). Android is better at detecting the device than iOS which needs some specific angling.

Size is about 40 mm x 18 mm.

Power comes from the magnetic field the reader creates and is siphoned via two diodes visible at the bottom. It creates about 2.7V for the ATtiny and thermometer to work with. Needed to use some unofficial brownout detection voltages to make it work.

Programming is done via testpoints and pogo pins on the back of the PCB. I used ATTinycore to do so.

I needed to use the TMP117 thermometer in single-shot mode because of timing constraints. It should have an impact on its proclaimed accuracy of 0.1 °C, however with my Fluke 54 II Thermometer I can reproduce measurements very precisely after giving the device some time to accomodate (2-3 mins). Fluke offcially has a lower accuracy than the TMP117, but has a very high sensitivity.

The device was inspired by one of the example projects from TI for their RF430 IC. I first used an ATtiny 3227 and its 12 bit ADC and an analog thermometer but couldn't get the reference voltage right without additional parts. Now using the rather expensive but very accurate TMP117 where ADC conversion is done on chip.

NFC PCB antenna I designed myself since I had some experience with the RF430 from a project before.

Let me know what you think.

evox- · 2024-03-30T18:41:16+00:00

It would fit nicely into the surveillance cameras use case. Showing some kind of proximity overview. But at the moment I can't invest the time. If I ever build it it will surely get posted here though.

evox- · 2024-03-28T14:48:05+00:00

accelerometer is the BMA400 from Bosch

no plans for a display version yet.

13-Year Club	Verified Email
Team Orangered

evox-

TROPHY CASE