You are here

VESC TRAMPA NRF BLE firmware question and feature request

2 posts / 0 new
Last post
Spaceman
Offline
Last seen: 2 months 2 weeks ago
Joined: 2022-03-03 05:06
Posts: 7
VESC TRAMPA NRF BLE firmware question and feature request

 Question regarding firmware revisions and to do list.   

List simple FW rev and product description in VESC tools SWD programmer for BLE's

Tx power Low/Mid/high instead of dbm, preconfigured for sensible RF duty keeping in mind both BLE units need to match levels.

Remove Integrity as it should be pretested or implement as auto ack. My understanding in integrity is mainly the radio speed option > small bandwidth for a robust carrier and modulation type.

 Ideal for Trampa Website to include product support - binfile. AKA noting a human safety issue coding preamble that should be addressed in older rev RF products and updated.

Most folks are not developers, understanding resources compiling source code, searching via the correct channels via a github.com/vedderb link for a master file. 

Bringing up another question regarding various VESC hardware products and FW coding reversions compatibility being the main reason creating this thread / topic after FW upgrading a Trampa wand (non mageto) from V1.1 bringing it to V1.4 - flashed from an original HW product roll release before chip the shortage from a VESC6 Mk5 loaded and updated with tool V6.02.  Anything I am missing. V1.4 is all the wand upgrades to. Basically in short words, list in instruction manual documentation known stable FW to run with. Good to note releases listed in Vesc tool developer dropdown box somewhere in FW editor not to roll with. 

 Noting a attached VESC/Trampa V2.0 BLE 52840 - RF module being a BLE 654 queried via VESC tool 6.02 SWD programmer displays non supported products flash files becoming guess work, brick or let the smoke out. Safe to say for experimental perposes tested uploads from four listed devices available for update did not damage the unit being nrf52840_stormcore_ble_rx31_tx30_led5 semi worked,  tethered to the remote, bringing up another question what firmware reversion from the factory do the BLE require as both Trampa wand aka BMD-340 RF transceiver differs and would think that maybe a problem handling RF protocals or what ever algorithms ?

 

 

 

.

 

 

 

 

 

 

Spaceman
Offline
Last seen: 2 months 2 weeks ago
Joined: 2022-03-03 05:06
Posts: 7

I am a little dubiuos and behind the times with coding and since past couple of days of little free time away from work, looking at and into mass amounts of effort people have contributed to the VESC project. Hats off to everyone and thanks Ben for having this open source. 

 Unfortunately I don't own any Vesc units, debuggers and will be looking into the future to play around as I always wanted a lego mindstrom set in the younger days and if had the know how would love to contribute as I know nothing about everything.

So looking at the Vesc radio section again. The frequency / channel selection availability looks a little wack compaired to 802.15.4 channel standards, including dbm increment intervals manufacture recommendation.  Looking at another build for a friend with 0x0: 0x1010101 <- does not match preamble (0xB105000D). What is that, a clock frequency or something?

About to down load ChibiOS, and manual to check shell commands to query and ping the BLE's from the vesc hardware termianal. Putty came to mind and manufacture test tools. Although the only debugger on hand and borrowed is a Vesc unit for the past couple of days. Ideally a RF front end comms test set would be the go or a SDR to inspect the RF ramping.