A320 FMGS Compatible with Cockpitsonic FCU/EFIS/AUTOBRAKES/ RADIO.......

[Jerec]

Good morning,

thx for the fix! It works now with configuration of all axis and takeoverbutton / AP disc is working too. What a new feeling with the FBW with correct force on Joystick.
Many thanks for that!
But on my testflight yesterday the hardwareconnect module crashed in the background with an exception error, so i coiuldnt complete the flight. Maybe there is a small bug left inside the dll?


Best regards Henrik

[jeehell]

Hi,


Please report again after testing for a while if you still get this error.
When it happens, it should be sufficient to manually restart hardware connect to restore the flight controls.

Regards,
JL

[Jerec]

Good morning JL,

after some testflights, the error appears after roundabout 30min flying in multiple times:

1. Access violation in different adresses
2. Out of memory error

In that case, the flightcontrols get stuck and autopilot/ATHR is disconnected. After switching AP/ATHR on, the FMGC takes over control and it seems to be ok, but when manually dic, the aircraft is flying away with throttle setting before error. Damn, i just read, that restart of hardwareconnect should solve it for the flight, i will test it next time.
Can i help you anyway to find the error by sending logs? Just tell me and i will do.

Regards Henrik

[jeehell]

Hi Henrik,

Ok I iwll look at that ASAP. I may need to put extra logging feature in it to catch the issue, as so far I haven't had any issue with the module. Could you determine if it is the stick addition which causes issue? Or did you have that with the rudder-only setup as well?

Regards,
JL

[jeehell]

Hi,

Please download those:
http://www.jeehell.org/HardwareConnect.exe
http://www.jeehell.org/EHIDmodule.dll

hardwareConnect will output a log file called HClog.txt. Next time it crashes, send me the log (DO NOT restart Hardware Connect before copying the log to a safe place, it will be overwritten otherwise!).

Regards,
JL

[Jerec]

Good morning JL,

thx for the update. I will check it this evening and keep you informed at once, as i have a log with error.
Regarding to your question about error with only rudder-setup, i cant remember the error in that configuration did occur in that way, but when we cannot find the error with the log, i can test with only stick / only rudder configs. Just tell me, what i have to do to help you.

Regards Henrik

[Jerec]

Good morning,

just took a short flight yesterday with the report tool and here is, what the log says:

HardwareConnect Launched
ComplexJoy.dll loaded
EHIDmodule.dll loaded
FSUIPCmodule.dll loaded
SkalarkiIO.dll loaded
SkalarkiIO.dll:Starting server at (null):25253...
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client connected: 127.0.0.1:49183
SkalarkiIO.dll:Waiting for client...
EHID:Connected version5
SkalarkiIO.dll:Client connected: 127.0.0.1:49185
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49185
SkalarkiIO.dll:Client connected: 127.0.0.1:49186
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49186
SkalarkiIO.dll:Client connected: 127.0.0.1:49187
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49187
SkalarkiIO.dll:Client connected: 127.0.0.1:49188
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49188
SkalarkiIO.dll:Client connected: 127.0.0.1:49189
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49189
SkalarkiIO.dll:Client connected: 127.0.0.1:49190
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49190
SkalarkiIO.dll:Client connected: 127.0.0.1:49191
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49191
SkalarkiIO.dll:Client connected: 127.0.0.1:49192
SkalarkiIO.dll:Waiting for client...
SkalarkiIO.dll:Client disconnected: 127.0.0.1:49192
SkalarkiIO.dll:Client connected: 127.0.0.1:49195
SkalarkiIO.dll:Waiting for client...
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
EHID:analog input failed
Fast Timer failed

Regards Henrik

[jeehell]

Hi,

First thing, you have skalarkiIO.dll inside your hardware modules folder. Do you have any hardware from Skalarki? because it tries to connect to skalarki interface software but fails. It could be a cause of crash. Can you try again after deleting skalarkiIO.dll?

Please also download again http://www.jeehell.org/EHIDmodule.dll

Best regards,
JL

[Jerec]

Hi JL,

yes, yesterday my cockpithardware from SKALARKI arrived. First of all its the FCU unit, which i connected for testing. But at next testing, i will only connect the CS-Hardware and remove skarlarki.dll.
By the way, just for understanding. You said, that the dll was not connecting, but i could fly with the FCU. But it is correct, that i start The SkarlarkiIO.dll on Hardwareconnect and the IO-Profilersoftware from Skalarki itself to handle the hardware? Or is this action doubled. As far, as i understand, your dll only provides the connection to the FMGS with the IO-Profilersoftware. Together, they build the Interface for Hardware, right? In case of no, i have to remove one of the Interfaces.

I will keep you informed with new testdata witout any other hardware connected.

[jeehell]

Hi,

I do not know exactly how skalarki interface works. But judging from the log, there seems to be frequent connections/disconnections from his module software. I guess it is the connection between skalarki module and skalarki IO profiler, I do not know.
But it would be best to make sure his module is ruled out, this way I'll concentrate on the cockpitsonic module which I developed myself.

Regards,
JL