Impossible to connect to ioni hc pro

Herve45 · 6 July 2020 14:13

My hardware configuration:
small mige
ioni pro hc
simucube 1.0.22
ioni 10716

Problems arise when:
I disable ioni usb configuration on simucube 1.0.22
I run granity 1.15.1
both USB cables attached

How it behaves:
sometimes “simplemotion usb (ft230x basic uart” is present on the list
sometimes it’s missing

and it’s impossible to connect on ioni
I formatted my system a few months ago
maybe drivers are missing

I have attached following files:

Mika · 6 July 2020 14:21

When it is not visible, can you copy the debug event log from Simucube to here.

Herve45 · 6 July 2020 14:22

Simucube Boot : 1
Simucube Boot : 0
Simucube Boot : 22
Flash settings data loaded : 0
First-time drive initialization : 0
Initial config has been previously performed. Initializing Drive. : 0
State: Initializing Drive : 0
Drive init stage 1, position : 857233
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 857237
Drive init stage 4, phasing, current position : 857241
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Request profile number : 0
Command: Request profile name for profile : 0
Command: Request profile byte data for profile : 0
Command: Request profile number : 1
Command: Request profile name for profile : 1
Command: Request profile byte data for profile : 1
Command: Request profile number : 2
Command: Request profile name for profile : 2
Command: Request profile byte data for profile : 2
Command: Request profile number : 3
Command: Request profile name for profile : 3
Command: Request profile byte data for profile : 3
Command: Request profile number : 4
Command: Request profile name for profile : 4
Command: Request profile byte data for profile : 4
Command: Request profile number : 5
Command: Request profile name for profile : 5
Command: Request profile byte data for profile : 5
Command: Request profile number : 6
Command: Request profile name for profile : 6
Command: Request profile byte data for profile : 6
Command: Request profile number : 7
Command: Request profile name for profile : 7
Command: Request profile byte data for profile : 7
Command: Request profile number : 8
Command: Request profile name for profile : 8
Command: Request profile byte data for profile : 8
Command: Request profile number : 9
Command: Request profile name for profile : 9
Command: Request profile byte data for profile : 9
Command: Request profile number : 10
Command: Request profile name for profile : 10
Command: Request profile byte data for profile : 10
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 1
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 2
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 3
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 4
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 5
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 6
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 7
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 8
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 9
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 10
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 11
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 12
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 13
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 14
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 15
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 16
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 17
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 18
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 19
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 20
Command: Set calibrated analog axis mode : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Regain SMBUS : 1
State: Regaining SMBus : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
Drive init stage 1, position : 858341
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 858341
Drive init stage 4, phasing, current position : 858341
Drive init stage 4, phasing, current position : 858341
Drive init stage 4, phasing, current position : 858278
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Regain SMBUS : 1
State: Regaining SMBus : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
Drive init stage 1, position : 859213
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 859213
Drive init stage 4, phasing, current position : 859214
Drive init stage 4, phasing, current position : 859213
Drive init stage 4, phasing, current position : 859133
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Regain SMBUS : 1
State: Regaining SMBus : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
Drive init stage 1, position : 859565
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 859565
Drive init stage 4, phasing, current position : 859566
Drive init stage 4, phasing, current position : 859569
Drive init stage 4, phasing, current position : 859501
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Request profile number : 0
Command: Request profile name for profile : 0
Command: Request profile byte data for profile : 0
Command: Request profile number : 1
Command: Request profile name for profile : 1
Command: Request profile byte data for profile : 1
Command: Request profile number : 2
Command: Request profile name for profile : 2
Command: Request profile byte data for profile : 2
Command: Request profile number : 3
Command: Request profile name for profile : 3
Command: Request profile byte data for profile : 3
Command: Request profile number : 4
Command: Request profile name for profile : 4
Command: Request profile byte data for profile : 4
Command: Request profile number : 5
Command: Request profile name for profile : 5
Command: Request profile byte data for profile : 5
Command: Request profile number : 6
Command: Request profile name for profile : 6
Command: Request profile byte data for profile : 6
Command: Request profile number : 7
Command: Request profile name for profile : 7
Command: Request profile byte data for profile : 7
Command: Request profile number : 8
Command: Request profile name for profile : 8
Command: Request profile byte data for profile : 8
Command: Request profile number : 9
Command: Request profile name for profile : 9
Command: Request profile byte data for profile : 9
Command: Request profile number : 10
Command: Request profile name for profile : 10
Command: Request profile byte data for profile : 10
Command: Request hardware settings : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 0
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 1
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 2
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 3
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 4
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 5
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 6
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 7
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 8
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 9
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 10
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 11
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 12
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 13
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 14
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 15
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 16
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 17
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 18
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 19
Command: Request analog input settings : 0
Command: Request bytedata for analog profile : 20
Command: Set calibrated analog axis mode : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Regain SMBUS : 1
State: Regaining SMBus : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
Drive init stage 1, position : 860064
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 860062
Drive init stage 4, phasing, current position : 860065
Drive init stage 4, phasing, current position : 860065
Drive init stage 4, phasing, current position : 860001
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Regain SMBUS : 1
State: Regaining SMBus : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
Drive init stage 1, position : 860151
Read MMC value from Drive : 12000
Read Motor Resistance value from Drive : 2880
Read CPR from Drive : 4194304
Read Drive Version ID from drive : 11201
SM Watchdog disabled successfully : 0
Waiting for faults to clear : 0
Waiting for servo to be ready : 0
Drive init stage 3, position after faults cleared : 860149
Drive init stage 4, phasing, current position : 860150
Drive init stage 4, phasing, current position : 860150
Drive init stage 4, phasing, current position : 860098
State: Drive initialization was successful : 0
State: Set baudrate : 0
SM Watchdog enabled successfully : 0
SMBus baudrate initialized successfully : 4500000
State: Before operational - calculating new constant values : 0
State: Operational : 0
Command: Release SMBUS : 0
State: Releasing SM Bus : 0
SM Watchdog enabled successfully : 0
SM Watchdog disabled successfully : 0
SMBus baudrate initialized successfully : 460800
State: SM Bus released successfully : 0
Command: Event log download request : 0

Herve45 · 6 July 2020 15:34

ft230x absent.txt (19.9 KB) ft230x present.txt (21.3 KB)

Mika · 6 July 2020 17:39

Nothing really obvious visible in the logs. Lets see if anyone else is affected when the beta release is officially released.

Herve45 · 6 July 2020 18:22

My tests

I downgraded on 0.11.2 and I have access to granity
I upgraded to 0.50.4 and I have access to granity
I upgraded to 1.0.17 and I have access to granity
I upgraded to 1.0.19 and I have access to granity
I upgraded to 1.0.20 and I have access to granity
I upgraded to 1.0.21 and I have access to granity
I upgraded to 1.0.22 and I have access to granity !!!

i don’t understand what happened

Herve45 · 7 July 2020 07:50

problem again

phillip.vanrensburg · 7 July 2020 07:53

It is possible your comm adapter is faulty, or USB cable /port is suspect. Electrical interference can cause the hassles you are seeing.

Herve45 · 7 July 2020 08:00

your comm adapter is faulty

—> on my card simucube ?

phillip.vanrensburg · 7 July 2020 08:44

Oops, ignore comm-adapter part…I was thinking of Argon

But anyway, try new USB cable and/or onboard cpu-based USB 2 port , not any Asmedia port, for example.

Mika · 7 July 2020 08:44

It might be a dodgy USB cable or something like that. However, is there a good reason on why you need to access Granity?

Herve45 · 7 July 2020 08:48

I did these tests

change of usb cable
change of usb port on my hub
change of usb port on my asus z390-h

the problem is not solved
yes I need to access granity because I am going to change the 48v power supply to a 36v power supply and I have to modify FOV and FUV

Herve45 · 7 July 2020 08:51

would this port be defective ?

Mika · 7 July 2020 08:55

It might, but try with another cable first.

Herve45 · 7 July 2020 09:06

I tried 3 USB port and 2 other cables
no improvement

phillip.vanrensburg · 7 July 2020 09:36

Anyway no need to change the FOV or FUV in your case.

Herve45 · 7 July 2020 09:49

currently with my 48v power supply, I have these values for FOV and FUV
if i install a 36v power supply, can i keep the same values for FOV and FUV ?

I will not burn my simucube system
Thanks

phillip.vanrensburg · 7 July 2020 09:55

I think this should be ok with lower voltage psu, but let us ask Mika to check with Tero/Esa anyway. I do not believe it will be an issue though.

Mika · 7 July 2020 10:39

FOV should be changed so that the regen algorithms work properly, but otherwise it should be fine.

More interesting is the reason why 36V? It will only result in much more sluggish feel, not as crisp FFB.

Herve45 · 7 July 2020 10:46

To test with an engine that runs slower with 36v.

It seems that my simucube card seems defective on this port