@Makinolo - Great work the beta 0.3.0.0 is working fine with android app (ErgoK). The fit file just has the , vs . issue with default danish language on the pc. I'll just switch those around for my next test ride. Sure gotta be fun riding some more with it. I'm not a gamer so i probably have to get my kids to help me out :-) And i'll try to get them to try the sweaty version of GTA as well :-)
Great idea and i would really like to try it out. Unfortunately my trainer is not found
The software that i am using: "An ANT+ FE-C connection is possible e.g. with zwift, bkool, virtualtraining etc., golden cheetah is supported too.
Both ANT+ FE-C operation modes (simulation and workout) are supported, your ergometer/trainer acts like a smart-trainer."
http://ergo.ub-online.de/index.php/en/
I am a software developer but a noob when it comes to GTA5 - I've even borrowed my sons account.
With F11 the debug shows that ANT comm is ok, but i don't get power from the trainer. The debug of the android app does not contain anything so i don't think the FEC*.dll recognices and even tries to connect.
The ant+ id 1306 as fec controlable and 1302 as power meter.
5mods on Discord
@Makinolo - Great work the beta 0.3.0.0 is working fine with android app (ErgoK). The fit file just has the , vs . issue with default danish language on the pc. I'll just switch those around for my next test ride. Sure gotta be fun riding some more with it. I'm not a gamer so i probably have to get my kids to help me out :-) And i'll try to get them to try the sweaty version of GTA as well :-)
@Makinolo Thank You for the suggestion - unfortunately your are right. It does not make much difference setting the device id.
I've editor the ini
FECDEVICEID = 1306
log file below. It looks like an issue with the channel 1 connection - id 12345 has to be a default
Device
16 Controls
17 Fitness Equipment Devices ( FEC )
Constructor: Creating ANT_plus_transponder.
Init:USB device initialisation was successful!
InitANT: Resetting module...
InitANT: Setting network key...
Start: ANT initialisation was successful!
CAPABILITIES:
Max ANT Channels: 8
Max ANT Networks: 8
Standard Options:
Advanced Options:
CAPABILITIES_NETWORK_ENABLED
CAPABILITIES_SERIAL_NUMBER_ENABLED
CAPABILITIES_PER_CHANNEL_TX_POWER_ENABLED
CAPABILITIES_LOW_PRIORITY_SEARCH_ENABLED
CAPABILITIES_SEARCH_LIST_ENABLED
Advanced 2 Options 1:
CAPABILITIES_EXT_MESSAGE_ENABLED
CAPABILITIES_SCAN_MODE_ENABLED
CAPABILITIES_PROX_SEARCH_ENABLED
CAPABILITIES_EXT_ASSIGN_ENABLED
RESET Complete, reason:
RESET_CMD
MessageProcess: Framer Timeout No more messages. Processed 2
Network key set.
Assigning channel #0...
Assigning channel #1...
Channel #0 assigned
Setting Channel ID Device = 1306 Dev Type = 17 Trans Type = 5 ...
Channel #1 assigned
Setting Channel ID Device = 12345 Dev Type = 16 Trans Type = 5 ...
MessageProcess: Framer Timeout No more messages. Processed 2
Channel #0 ID set
Setting Radio Frequency to 57 ...
Channel #1 ID set
Setting Radio Frequency to 57 ...
Radio Frequency set for channel #0
Setting Message Period to 8192 ...
Radio Frequency set for channel #1
Setting Message Period to 8192 ...
Message period assigned #0
Setting LP search timeout 16 in channel #0...
Message period assigned #1
Setting LP search timeout 0 in channel #1...
MessageProcess: Framer Timeout No more messages. Processed 6
Setting HP search timeout 2 in channel #0...
Setting HP search timeout 0 in channel #1...
Message search timeout assigned #0
Opening channel #0...
MessageProcess: Framer Timeout No more messages. Processed 3
Message search timeout assigned #1
Opening channel #1...
Chanel #0 opened
Enabling extended messages...
Chanel #1 opened
Enabling extended messages...
Extended messages enabled
MessageProcess: Framer Timeout No more messages. Processed 4
Extended messages enabled
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Not ready to transfer on sendMessage 0x32
Not ready to transfer on sendMessage 0x33
Close: Closing all channels.
Close: Release serial object.
Great idea and i would really like to try it out. Unfortunately my trainer is not found
The software that i am using: "An ANT+ FE-C connection is possible e.g. with zwift, bkool, virtualtraining etc., golden cheetah is supported too.
Both ANT+ FE-C operation modes (simulation and workout) are supported, your ergometer/trainer acts like a smart-trainer."
http://ergo.ub-online.de/index.php/en/
I am a software developer but a noob when it comes to GTA5 - I've even borrowed my sons account.
With F11 the debug shows that ANT comm is ok, but i don't get power from the trainer. The debug of the android app does not contain anything so i don't think the FEC*.dll recognices and even tries to connect.
The ant+ id 1306 as fec controlable and 1302 as power meter.