Testing Raspberry_Release6

[decodeais]

I started the test. First problem I saw was that the LED's for Tacx and Shutdown show a dim light. I changed them to GPIO16 and DPIO20. On this ports every thing is OK. The reason are the default internal pullups. Another solution would be to make them activ low and connect them to a power pin, Second Problem switching on does not work on RPi4 by GPIO5. I made a bridge to GPIO3, then it works, but there may be trouble when I2C should be used.

[jujroy]

Hello gang,

I am a Windows 10 user but being curious, I decided to test Release 6 on my Fortius. I noticed that the power is now displayed on the Dash Board during the calibration process. Love it. After warm up and stabilisation, the resistance was around 1300 and power displayed 58 Watts. During my workout, I noticed a a few warnings on the DOS page : Dongle.read : x characters skipped (X being between 4 and 10 chararcters). With version 5.2, my Pedal Stroke Analysis is always fairly circular. With Version 6, often the bottom half of the circle was choppy, not as smooth as V5.2. The overall feeling was the same as V5.2. Thanks again for the great work.

[WouterJD]

The dongle read errors are a nasty issue; the ANTdongle has to warm-up. It seems old data from previous sessions. Suggestions welcome.

Pedal Stroke Analysis has been improved. There were some issues in the code, should be better now; meaning "according the data received". At the time of writing it was argued whether this was possible at all, since the USB-device must be read at a high frequency (20ms) to have enough samples. It is the main reason that multi-processing is implemented (also to get experience with it in python). It's about the max the device can do. Perhaps it's also dependant on the (quality of the) trainer (and cabling); one trainer may be better than the other.

Try to pedal smoothly and see whether it works. Try to ride irregular and check effect; bouncy ride or power left/no power right. On my Tacx Fortius the curve follows my way of cycling, curious how your experiences are.

[MeanHat]

@WouterJD I ran a further test on RPi0 with the latest release (fixing T1902) using scripts: 1, 2, 3, 5, 6, 7 and 9. I found the following:

1. 3_InstallNodeJs.sh (and 4) left the terminal window in ~/Downloads rather than Home. Probably not a problem.
2. There was no requirementsNoGUI.txt file in ~/FortiusANT/pythoncode. I created one without wx in it
3. When I ran from reboot there was error reported from /raspberry/FortiusAntMain.sh in line 6 relating to logfile removal: unexpected token `('. Should it read '('? I commented out the lines relating to log file and wastebasket deletion
4. On next reboot error reported in FortiusAntCommand.py line 63 with import wx error. I tried commenting out lines 63 and 64 but this resulted in error importing wx in FortiusAntBody.py line 212. I also tried changing Constants.py with GUI set from True to False but this produced different errors.

It seems that FA is trying to install/use wx. Does this help? Please let me know if you would like me to test further.

[WouterJD]

1. Agree; I could save pwd and restore at end. Manuals says to execute from file-manager and then it's not relevant.
2. Should be there now https://github.com/WouterJD/FortiusANT/blob/master/pythoncode/requirementsNoGUI.txt
3. I removed () because they are not within ''
4. Cannot reproduce; Check constants.py

   UseGui              = True      # Can be modified to force no-GUI
   try:
   from wx import EVT_CLOSE    # Just checking presence
   except:
   UseGui          = False     # no wx, no GUI

I can run with UseGui = False; which should go automatic when no wx is there. If wx is there, but faulty - then you will have to disable with UseGui = False