It only happens on reloaded data, not while logging live.
The reload path is parsing the column name - splitting on underscores to recover type, source and sample count - and then rejoining for display without putting them back. So the reconstruction partly works: it recovers enough to identify the channel, it just doesn't carry the unit and it mangles the label on the way out.
I am surprised it mangles the names.
And I do not remember if TC tries to recover units from math, I hope it does, but I will check.
I have made a Notepad++ User Defined Language config to help coding TestController definition files.
After importing, open Language > User Defined Language > Define your language, go to the Comment & Number tab, and under Comment line position tick "Force at the beginning of line". Without it every semicolon starts a comment, including the ones separating commands.
(Attachment Link)
Lots done, reworked the two PS drivers I'm posting today.
I have made a Notepad++ User Defined Language config to help coding TestController definition files.
After importing, open Language > User Defined Language > Define your language, go to the Comment & Number tab, and under Comment line position tick "Force at the beginning of line". Without it every semicolon starts a comment, including the ones separating commands.
I am relaxing this evening and playing with my computer and I derided to play a bit with AI and used the following question...
I think I might have got you addicted to another TE related hobby.
@Cyclotron
Do I understand that the definitions of Cyclotron are Copyrighted and provided under license ? (that is what I read on your github)
Could you clarify this why that is needed and also how this impacts TC as a whole once part of a release.
I encourage everyone to define their license because they own it regardless of their noting it. It would be reasonable for HJK to ask that each driver have a reasonable license from the author before including it. Its unfortunate that this is the way of things but its better to understand it and align your work to your will by stating it.
I encourage everyone to define their license because they own it regardless of their noting it. It would be reasonable for HJK to ask that each driver have a reasonable license from the author before including it. Its unfortunate that this is the way of things but its better to understand it and align your work to your will by stating it.
I take posting is this thread as implied consent to include it in TC.
With images I want a statement saying I am free to use it (I sometimes add images to the list of supported equipment, but only for a few devices).
I Flash2b takes photos of some of his modules, I may include a few, there are nearly no photos of modules in the list.
Thank you for posting that. This gives everyone a clear understanding of the path to being included with TC.
All of my content for TC shoudl be considered free to use. The repos that contain it all out on github should be clear I hope. If you need any specific statements from me let me know. I picked MIT license as a way to find something the most permissive but IANAL so maybe there's a better one.
Could @Cyclotron please change #name LBE-1420 GPS to #name Leo Bodnar LBE-1420 GPS in the definition?
(more consistency)
Don't forget to reload the definition or edit settingsLoad.txt adding the same there as well !
I've updated this driver with the manufacturer name in the #name and dropped the "GPS".
Would make sense to rewrite it abandoning Java and using 100% Python instead?
Python has an enormous ecosystem of community-supported libraries (like pyVisa, RPi.GPIO, pySerial, smbus, and CircuitPython/MicroPython libraries) designed specifically to interface with HW.
I am a beginner here, so please go soft and sorry in advance. Please do not shoot at me.
PyVISA: The industry standard for communicating with test equipment via GPIB, USB, RS232, or Ethernet (SCPI commands).
PySerial: Perfect for simpler devices that talk over virtual serial/COM ports.
Plotting & Dashboards: Instead of built-in Java GUI windows, Python lets you stream live data directly into Plotly/Dash, Streamlit, or Grafana for gorgeous, web-accessible telemetry dashboards.
Data Analysis: Instantly pipe your logged data into Pandas, NumPy, or SciPy for immediate post-processing and curve fitting.