phlegx

phlegx

Phlegx Systems operates in different sections like new web technologies, embedded systems, electronics, design and much more. Find us at https://phlegx.com

Member Since 12 years ago

Phlegx, Austria

Experience Points
16
follower
Lessons Completed
16
follow
Lessons Completed
1.2k
stars
Best Reply Awards
131
repos

77 contributions in the last year

Pinned
⚡ This plugin allows you to update your local Git repositories in Redmine when changes have been pushed to GitLab.
⚡ Redlics - Redis analytics with tracks (using bitmaps) and counts (using buckets) encoding numbers in Redis keys and values.
⚡ A gem that calculates the exchange rate using published rates from currencylayer.com.
⚡ Rocket.Chat notification plugin for Redmine
⚡ WebsocketRailsClient++ is a C++ library that uses the implementation of RFC6455 (The WebSocket Protocol) implemented in the WebSocket++ library, the Json++ light-weight JSON parser and the Boost library. It allows connections to the Ruby Websocket-Rails server and supports the Websocket-Rails protocol.
⚡ Real MAC addresses generator and vendor lookup with MAC address handling.
Activity
Jan
21
1 day ago
started
started time in 1 day ago
Jan
20
2 days ago
Activity icon
issue

phlegx issue comment ARMmbed/mbed-os-example-pelion

phlegx
phlegx

C030-R412M timeouts when connecting to Pelion over cellular [BUG]

Describe the bug The U-blox C030-R412M board doesn't connect to Pelion. I have a SIM card and a freshly formatted SD card. I'm using a Vodafone SIM card in the UK, APN is set to wap.vodafone.co.uk in mbed_app.json as indicated by Vodafone. I have attached an antenna.

Expected behavior The board should connect to Pelion.

Logs The serial output I'm getting is

Application ready
[INFO][FSST]: KV Dir: kvstore, exists(verified) - now closing it
Connect to network
[INFO][CELL]: New CellularContext  (0x2000e160)
[INFO][CELL]: CellularContext connect
[INFO][CELL]: Start connecting (timeout 1000 ms)
[INFO][CELL]: Modem ready
[INFO][CELL]: Setup SIM (timeout 1000 ms)
[INFO][CELL]: SIM is ready
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 1 seconds
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 2 seconds
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 4 seconds
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 8 seconds
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 16 seconds
[INFO][CELL]: RSSI unknown
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 32 seconds
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 64 seconds
[INFO][CELL]: RSSI -89 dBm
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 128 seconds
[INFO][CELL]: RSSI -51 dBm
[INFO][CELL]: Network registration (timeout 180000 ms)
[INFO][CELL]: Continue after 600 seconds

Host system (please complete the following information):

  • OS: Ubuntu
  • Compiler: GCC_ARM
  • Mbed CLI version (if used): 1.10.0

Device information: Have the latest mbed-os-example-pelion code(latest commit on 22nd of April). Using mbed-OS and client pointed in there.

How can I get the board connected to Pelion? Thank you. George

phlegx
phlegx

Hi @gggekov! Please check the MNO profile of the Ublox cellular chip with AT+UMNOPROF?. If the result is 0 try to set it to 19 or 100.

Set MNO profile with Ublox m-center:

AT+CFUN=4
AT+UMNOPROF=100
AT+CFUN=15

Also check the radio access technology (RAT) used and set the right RAT (e.g. AT+URAT=9,8).

AT+CFUN=4
AT+URAT=9,8
AT+CFUN=15
Jan
14
1 week ago
Activity icon
issue

phlegx issue minio/operator

phlegx
phlegx

Error when Tenant is created

Using the default values for values.yml from the git repository. When I go to the console I get the following error:

An error occurred, please try again
V2.TenantList.Items: []v2.Tenant: v2.Tenant.Spec: v2.TenantSpec.PrometheusOperator: readObjectStart: expect { or n, but found f, error found in #10 byte of ...|perator":false,"requ|..., bigger context ...|d"}},"volumesPerServer":1}],"prometheusOperator":false,"requestAutoCert":true,"s3":{"bucketDNS":fals|...

Any ideas what might causing this? Is there a way to make this more verbose? I assume this is some misconfiguration in my Yaml file or a Bug.

It used to work with an older version though.

Your Environment

  • Version used (minio-operator): 4.4.3
  • Environment name and version (e.g. kubernetes v1.17.2): v1.20.8
Jan
13
1 week ago
Activity icon
issue

phlegx issue comment minio/operator

phlegx
phlegx

Undocumented breaking change in CRD for Operator 4.3.9

Expected Behavior

I have just updated Minio Operator from version 4.3.5 to 4.3.9 in our development cluster using the Helm chart. Being a minor version change, with nothing of concern in the release notes, I expected the pods to restart and just work.

Current Behavior

4.3.9 appears to include a breaking change in the CRD within the Helm chart, relating to spec.prometheusOperator

CRD in 4.3.8:

prometheusOperator: properties: annotations: additionalProperties: type: string type: object labels: additionalProperties: type: string type: object type: object

CRD in 4.3.9:

prometheusOperator: type: boolean

Possible Solution

Steps to Reproduce (for bugs)

Context

This has resulted in our Tenants (Deployed in a Gitops workflow using Flux) failing to deploy with the following error:

error validating data: ValidationError(Tenant.spec.prometheusOperator): invalid type for io.min.minio.v2.Tenant.spec.prometheusOperator: got "map", expected "boolean"; if you choose to ignore these errors, turn validation off with --validate=false

I can find no reference to this change in the release notes and no documentation regarding how to use the new Prometheus Operator functionality. Previously we specified a label under spec.prometheusOperator.labels which ensured the ServiceMonitor would be picked up by the correct Prometheus server. I have no idea how to replicate this same functionality with the new CRD.

Regression

Yes. PrometheusOperator functionality no longer works as expected.

Your Environment

  • Version used (minio-operator):
  • Environment name and version (e.g. kubernetes v1.17.2):
  • Server type and version:
  • Operating System and version (uname -a):
  • Link to your deployment file:

Minio operator 4.3.9 deployed with Flux using the Helm chart. Multiple Tenants deployed by Flux. These do not using the Helm chart.

phlegx
phlegx

I'm also facing these issues. How can this be solved? Thanks!

Jan
10
1 week ago
started
started time in 1 week ago
Dec
20
1 month ago
Activity icon
issue

phlegx issue te-online/timemanager

phlegx
phlegx

[Feature Request] Compatibility with Deck / Tasks

Hi!

Please add possibility to associate tasks to a project from Deck app. Nextcloud Deck is a kanban style organization tool aimed at personal planning and project organization for teams integrated with Nextcloud. Deck is developed by Nextcloud itself. I think it could be an important feature if users can choose and associate Deck app tasks, Tasks app tasks or TimeManager app tasks to a project for time tracking.

See this issue on Deck app: nextcloud/deck/issues/2299

Dec
18
1 month ago
started
started time in 1 month ago
Dec
14
1 month ago
started
started time in 1 month ago
Dec
6
1 month ago
started
started time in 1 month ago
started
started time in 1 month ago
Nov
22
2 months ago
started
started time in 1 month ago
Nov
9
2 months ago
Activity icon
issue

phlegx issue ARMmbed/mbed-os

phlegx
phlegx

C030-R412m: Target don’t start (power supply / battery)

Description of defect

Under certain conditions the target C030-R412m does not start anymore. Following an explained routine that describes the problem:

  1. Power supply (over USB serial connector or through pins) and Battery are both attached.
  2. Program starts and runs as expected.
  3. Detach power supply, target runs as expected only with battery.
  4. After X time, battery is draining and target powers off.
  5. After some hours, I re-attach the power supply (over USB serial connector or through pins). And here is the problem!

Problem

The target don’t starts and the charger chip never starts to charge the battery. If I attach the power supply through USB with serial data, I don’t get a serial connection. Only the blue led (near serial USB connector if USB power supply used) and the green led near battery charger chip is on. Push reset button does not help and does nothing (no reaction).

To get the target back to work, I need to:

  1. Remove power supply and battery.
  2. Re-attach battery and then the power supply.
  3. Target returns to normal status and all works as expected.

Target(s) affected by this defect ?

C030-R412M

Toolchain(s) (name and version) displaying this defect ?

Mbed Studio 1.4.3

What version of Mbed-os are you using (tag or sha) ?

mbed-os-5.15.7

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

Mbed Studio 1.4.3

How is this defect reproduced ?

To reproduce this problem, follow steps described in description.

Nov
8
2 months ago
Activity icon
issue

phlegx issue comment ARMmbed/mbed-mqtt

phlegx
phlegx

MQTT wildcard subscriptions don't work with root topic

Wildcard subscriptions do not seem to be working per the MQTT standard.

Subscribing to '/test/topic/#' does not seem to work for messages coming into '/test/topic'.

It only seems to work for subtopics, for example:

'/test/topic/one' and '/test/topic/two'

phlegx
phlegx

Any news for this problem?

Nov
3
2 months ago
started
started time in 2 months ago
Oct
29
2 months ago
Activity icon
issue

phlegx issue datadrivers/terraform-provider-nexus

phlegx
phlegx

Import user functionality

Would be nice to have an import functionality for the nexus_security_user

Oct
26
2 months ago
Activity icon
delete

phlegx in phlegx/mbed-os delete branch mbed-os-5.15

deleted time in 2 months ago
Oct
25
2 months ago
started
started time in 2 months ago
started
started time in 2 months ago
Oct
22
3 months ago
Activity icon
issue

phlegx issue comment ARMmbed/mbed-os

phlegx
phlegx

Fix Ublox C030 SARA-R412M onboard cellular device serial (target default instance).

Summary of changes

Whit the following mbed_app.json config example, the ONBOARD_UBLOX target is used and the serial connection to the Ublox module can work properly.

"target_overrides": {
    "*": {
        "platform.stdio-convert-newlines": true,
        "platform.stdio-baud-rate": 115200,
        "platform.default-serial-baud-rate": 115200,
        "mbed-trace.enable": true,
        "cellular.debug-at": true,
        "cellular.use-apn-lookup": true,
        "nsapi.default-cellular-apn": "\"some.provider.com\"",
        "nsapi.default-cellular-plmn": null,
        "nsapi.default-cellular-sim-pin": null,
        "nsapi.default-cellular-username": null,
        "nsapi.default-cellular-password": null,
        "lwip.ipv4-enabled": true,
        "lwip.ipv6-enabled": true,
        "lwip.tcp-enabled": true,
        "lwip.ethernet-enabled": false,
        "lwip.ppp-enabled": false,
        "ppp.ipv4-enabled": false,
        "ppp.ipv6-enabled": false
    },
    "UBLOX_C030_R412M": {
        "target.features_add": ["STORAGE"],
        "target.components_add": ["SD"],
        "target.network-default-interface-type": "CELLULAR",
        "storage.storage_type": "FILESYSTEM",
        "sd.SPI_MOSI": "SPI_MOSI",
        "sd.SPI_MISO": "SPI_MISO",
        "sd.SPI_CLK": "SPI_CLK",
        "sd.SPI_CS": "SPI_NSS"
    }
}

Bugfix on ONBOARD_UBLOX.cpp#L30 adding line serial.set_flow_control(SerialBase::RTSCTS, MDMRTS, MDMCTS);.

With the correct serial flow control, the serial connection is stable and don't get lost.

CellularDevice *CellularDevice::get_target_default_instance()
{
#if defined(TARGET_UBLOX_C030_R41XM)
    static UARTSerial serial(MDMTXD, MDMRXD, MBED_CONF_PLATFORM_DEFAULT_SERIAL_BAUD_RATE);
    serial.set_flow_control(SerialBase::RTSCTS, MDMRTS, MDMCTS); // <---------- Bugfix
    static ONBOARD_UBLOX_AT device(&serial);
#elif defined(TARGET_UBLOX_C030_N211)
...

The discussion about this bug can be found on issue #15143.

Impact of changes

Migration actions required

Documentation

None


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[X] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

@RobMeades @0xc0170


phlegx
phlegx

I don't know what kind of test this is and if it is related to this bugfix.

Activity icon
issue

phlegx issue comment ARMmbed/mbed-os

phlegx
phlegx

Fix Ublox C030 SARA-R412M onboard cellular device serial (target default instance).

Summary of changes

Whit the following mbed_app.json config example, the ONBOARD_UBLOX target is used and the serial connection to the Ublox module can work properly.

"target_overrides": {
    "*": {
        "platform.stdio-convert-newlines": true,
        "platform.stdio-baud-rate": 115200,
        "platform.default-serial-baud-rate": 115200,
        "mbed-trace.enable": true,
        "cellular.debug-at": true,
        "cellular.use-apn-lookup": true,
        "nsapi.default-cellular-apn": "\"some.provider.com\"",
        "nsapi.default-cellular-plmn": null,
        "nsapi.default-cellular-sim-pin": null,
        "nsapi.default-cellular-username": null,
        "nsapi.default-cellular-password": null,
        "lwip.ipv4-enabled": true,
        "lwip.ipv6-enabled": true,
        "lwip.tcp-enabled": true,
        "lwip.ethernet-enabled": false,
        "lwip.ppp-enabled": false,
        "ppp.ipv4-enabled": false,
        "ppp.ipv6-enabled": false
    },
    "UBLOX_C030_R412M": {
        "target.features_add": ["STORAGE"],
        "target.components_add": ["SD"],
        "target.network-default-interface-type": "CELLULAR",
        "storage.storage_type": "FILESYSTEM",
        "sd.SPI_MOSI": "SPI_MOSI",
        "sd.SPI_MISO": "SPI_MISO",
        "sd.SPI_CLK": "SPI_CLK",
        "sd.SPI_CS": "SPI_NSS"
    }
}

Bugfix on ONBOARD_UBLOX.cpp#L30 adding line serial.set_flow_control(SerialBase::RTSCTS, MDMRTS, MDMCTS);.

With the correct serial flow control, the serial connection is stable and don't get lost.

CellularDevice *CellularDevice::get_target_default_instance()
{
#if defined(TARGET_UBLOX_C030_R41XM)
    static UARTSerial serial(MDMTXD, MDMRXD, MBED_CONF_PLATFORM_DEFAULT_SERIAL_BAUD_RATE);
    serial.set_flow_control(SerialBase::RTSCTS, MDMRTS, MDMCTS); // <---------- Bugfix
    static ONBOARD_UBLOX_AT device(&serial);
#elif defined(TARGET_UBLOX_C030_N211)
...

The discussion about this bug can be found on issue #15143.

Impact of changes

Migration actions required

Documentation

None


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[X] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers

@RobMeades @0xc0170


phlegx
phlegx

Thank you all for the reviews. I'm not authorized to merge this pull request. Are any of you authorized?