These applications are just ported from the DS203 firmware and not all functions are fully working. Assertion failed message means that something went wrong or something is not implemented yet. Normally the application could continue running, but I decided to freeze the app in that point so I will be forced to fix it properly.

Since I do not know if someone uses these apps, I focus on those which I find more valuable - mostly on new LA104 applications. When I will return to the development of DS203/DS213 I will fix it (but that will be probably not sooner than in 2 weeks), if you have basic C++ programming skills you can try fixing it on your own. Tutorials on how to setup building environment is in the readme

If you will find more problems, feel free to report here new issues.

from la104.

Thanks! I'll update you if I find something else

from la104.

The error that Steppan5g described also occurs with me.

Hardware

DFU version: V3.73C
Hardware version: SCH_V2.0
System version: DS213
FPGA version: AGL1K
Display: ILI9327 (400x240)
Disk: 8MB (8188kB)

Software

BIOS version: 0104
Build rev: a826b7c
Build date: Dec 23 2020 19:08:18
Build user: gabrielvalky
Build system: darwin19

from la104.

I have seen that error on random occasions.

I started formatting the filesystem, every time I update my LA104, this seems to help.

Not sure if it's the same for the oscillator devices, but I assume it could be.

from la104.

Please report here the assertion message and steps for reproducing

from la104.

Well, latest was with RF analyser synthesizer, when trying to transmit a capture, after having modified one field (temperature) Assertion failed in ../source/modem/cc1101.h [403]: len > 0 & len < 256

from la104.

@nieldk please export captured signals with button "Save" in capture tab and paste here produced file

from la104.

@nieldk please export captured signals with button "Save" in capture tab and paste here produced file

[{_protocol:"Nexus Temperature & Hum","length":36,"data_0":0x468029f2,"data_1":0x3000000,"id":70,"battery_low":1,"channel":1,"temperature10":41,"humidity":32,"_timestamp":555777,"_uid":1000},{_protocol:"TFA-Twin-Plus-30.3049","length":36,"data_0":0x5e0c2099,"data_1":0x30000000,"temperature10":44,"humidity":-3,"id":37,"battery_low":0,"channel":3,"valid":0,"_timestamp":742432,"_uid":1001,"junk":0}]

It's the nexus one that fails after nodding temp and press transmit

from la104.

@nieldk I confirm that it crashes when trying synthesizing nexus packet. Code responsible for synthesizing is simply commented out: https://github.com/gabonator/LA104/blob/master/system/apps_featured/80_rftool/source/protocol/nexus.h#L114

Unfortunately I am currently very busy to fix it. But I can guide you how to fix it and you can do it by yourself.

from la104.

@nieldk I confirm that it crashes when trying synthesizing nexus packet. Code responsible for synthesizing is simply commented out: https://github.com/gabonator/LA104/blob/master/system/apps_featured/80_rftool/source/protocol/nexus.h#L114

Unfortunately I am currently very busy to fix it. But I can guide you how to fix it and you can do it by yourself.

Thanks, I might give it a look. But it's not major thing.

from la104.

I fixed the minigen error in my fork https://github.com/Alexxdal/LA104

from la104.

@Alexxdal feel free to open pull request with your changes

from la104.