PC Ts World Raildriver And Joystick Interface

CobraOne just a heads up, on V2.0.0.6 the wipers control on the Raildriver still isn't working for me, although lights is now fixed.

 

Hi CobraOne, just got around to downloading and installing your program and I love the ease of it and customization, specifically the ability to remap buttons on the Raildriver. The only thing I'm curious about is that there doesn't seem to be a major change in the controls range, specifically the throttle. For the sake of this post, I'll reference the Metrolink F125 and Rotem cabcar. The range of the throttle handle still seems quite off. You have to move the handle pretty far for it to reach notch 1 and then the rest of the range is pretty off. Notches will change on their own without moving the handle and notch 8 is still hard to reach. All the way down on the throttle still only likes notch 7. The notching going down on the throttle isn’t the same as going back up. You can reach notch 1 in the proper spot when decreasing the throttle but if you’re starting out, you need to move it pretty far for it to start registering the throttle notches. These were all things that were apparent in the default TSW Raildriver logic that I hoped might be fixed with your program. Is there something I'm doing wrong? In a way, I'd never know your program is running, with the exception of some of the buttons I remapped.

In addition, the brake handle likes to twitch back and north a little bit now. I’ve tried calibrating everything again and using a 2nd Raildriver unit for comparison but the minor twitching in the brake handle remains.

I tried searching for a profile for the Metrolink F125 and Rotem cabcar but there doesn't appear to be one unless I missed it. I'm just trying to find a way to better adjust the values so the Metrolink DLC works better with Raildriver.

 

Hi amtraknick1993
1. If you haven't done so already, can you calibrate your Raildriver in my program using the menu Settings\Calibrate Raildriver.
2. Make sure neither my program or TSW is running.
3. Next, download this default calibration file
https://www.dropbox.com/scl/fi/5yze...ey=3y98fdk4hx63uitjmpdhxwpm0&st=m8sp6me8&dl=1
4. copy it to C:\Users\YOUR_USER_NAME\Documents\My Games\TrainSimWorld4\Saved\Config\WindowsNoEditor replacing YOUR_USER_NAME with your actual user name. If your using TSW 2 or 3 then replace TrainSimWorld4 with the relevant version number.
5. Run my program and select ThrottleAndBrake in the Enabled Assets and finally, run TSW.
6. Do not calibrate your Raildriver in TSW or you will lose the settings in the downloaded calibration file.

I have tried this with my Raildriver and it works perfectly.
I am working on V2.0.0.7 which will automatcally replace any TSW calibration with this one as well as other improvments to the notches calculations.
Chris

P.S. The wipers are also fixed in the next version

 

https://www.facebook.com/groups/alanthomsonsim/permalink/8169724843055326/ CobraOne post on ATS group

 

ajpardy
I tried the link, but as I don't have a Facebook account, I couldn't view it. I then created a Facebook account and asked to join the group but got the following responce:-
Your request to join Alan Thomson Simulation was automatically declined based on criteria admins added to this group.

New account
Person has had their Facebook account for at least a certain number of months.

To save me waiting months to be able to view the post, are you able to elaborate on what it refers to.
Chris.

 

oof. ok i've copied it:https://easyupload.io/m/05pogf CobraOne
"
My step son has bought the FLIRT and we have a big problem:
He's been using the Cobra One "TS Controller and Rail Driver Interface" since 2017 when it came out. In that 7 years, I have never, ever failed to get any train in TSC's power levers/brake levers working with the interface (he uses a Saitek Throttle Quad with the interface). Most work out of the box, some need a lot of manual tweaking (eg. the input mapper may state "VirtualThrottle" and this is copied into the interface but you then find that the command needs to be "vthrottle" etc, etc. But I have ALWAYS got every single train in TSC working with the interface............. Even all AP trains that state "this will not work with ANY hardware controllers" - we get every single one working. Until today! with the FLIRT I'm not exaggerating when I say I have spent upwards of 5 hours trying to get the FLIRT's PBL working with the interface. When the interface loads up the scripts from the FLIRT, it picks up a couple of things to note; one is that the word "error" appears in the entry for the brake notches (instead of numbers). This generates an error in the interface, but this word "error" can be deleted from the interface's brake notch field. There are three different entries importing for the "Throttle and Brake" field; one is shown as being linked to a script entry called "Regulator" and the other to an entry called "ThrottleAndBrake". I've tried assigning both, each one and none but nothing will make that darned PBL in the cab move when he moves the hardware! I've assigned his hardware to the interface's "Throttle and Brake" assignment, the "Throttle" (only) assignment, everything.
So, am I right in thinking that - due to some sort of custom set up - this is THE only train in TSC history that simply cannot be used with TSC's joystick API? Other than this issue, the train seems gorgeous. But this is an absolute showstopper for us. Neither me nor my step son have used the keyboard to drive trains in TSC for 7 years.
Does the FLIRT work with the TS Controllers PBC? out of interest?
PLEASE HELP! "

 

Wow, that's one angry man.
It sounds like there is an error in the engine.bin file which is stopping the program extracting the control values.

 

CobraOne I for one am not an angry man. I went ahead and follow your instructions from your previous post above and I can say it works great now! Everything is working smoothly, much better now than before. Throttle even has notches! And I was able to custom map some buttons. The only thing I did for myself was set the sensitivity setting to 3 as I found the controls seem to like this a little better. I’ve found is the headlights and wiper switches both still don’t work. I know you said the wipers was being fixed in the next version but currently, my headlights switch doesn’t work either.

Thank you for the wonderful program and mod!

 

I have just tried the headlights and wipers on both a raildriver and joystick and they work fine for me
The only problem I have is that as the raildriver switches are only 3 position, if you drive a loco that has more than 3 positions, you won't get them all working, just 3.
This is built into the sim as it is only expecting 3 positions from the raildriver and I can't change that.
Chris

 

Hi Matt, I have just replied to your DM
Chris

 

Hello Chris,

I've built my own train control panel and now I want to use it for TSW. I have a throttle and brake lever in the form of a potentiometer connected to an Arduino. Your program also detects it, and I was able to assign my lever to the Throttle and Brake Assignment, but the issue of the lever's midpoint arose: When I bring my lever to the middle position, the lever in TSW is set to 5% brake power (Your program sends the value Throttle and Brake: 0.466666). If I then move my lever slightly forward, the lever in the game returns to the middle position (Your program sends the value Throttle and Brake: 0.6196079). I calibrated my potentiometer using the standard Windows Controller program, but I can't calibrate my lever in your program, right?. I don't understand why this isn't working, and I would appreciate it if you or others who have encountered this problem could help me.

Thanks,
Jo

 

Hi Jo
Can you this:-
1. Make sure neither my program or TSW is running.
2. Next, download this default calibration file
https://www.dropbox.com/scl/fi/5yze...ey=3y98fdk4hx63uitjmpdhxwpm0&st=m8sp6me8&dl=1
3. copy it to C:\Users\YOUR_USER_NAME\Documents\My Games\TrainSimWorld4\Saved\Config\WindowsNoEditor replacing YOUR_USER_NAME with your actual user name. If your using TSW 2 or 3 then replace TrainSimWorld4 with the relevant version number.
4. Run my program and select ThrottleAndBrake in the Enabled Assets and finally, run TSW.
5. Do not calibrate your controller in TSW or you will lose the settings in the downloaded calibration file.

Chris

 

Hi Chris,

thanks for your quick response. I followed all the steps as you described, but unfortunately, it didn't change anything. I replaced the file in the destination folder, so there was already one that I replaced.

Jo

 

Hi Jo
If you are happy to give the next version a go, you can download it from here
https://www.dropbox.com/scl/fi/aps5...ey=z50mihv5x2bybbnovw1lp433p&st=bcchzvcc&dl=1

I'm not officialy announcing its release yet as it's still going through final testing but all seems stable, if it still does not fix your problem, look at the Using Notches.pdf in the Manuals folder, in particular the section on Advanced notches which has been completely revamped in this version.

Chris

 

Hi Chris,

I'm sorry to you again, but it just won't work. I have now used the version you sent me. Unfortunately, the error still hasn't been fixed with this version. To make sure the error isn't coming from my homemade train control panel, I connected my steering wheel. Unfortunately, the error still occurred with this as well. I've also attached some photos showing the condition with the steering wheel (Joystick = Steering Wheel). On the right, you can see that when my steering wheel is in the middle position, 5% brake power comes up. Maybe I did something else wrong that you can see in the video. I haven't made any other settings except for calibrating my joystick through your app. You also mentioned something about the Notches-Manual, but I didn't understand where I should change or set these settings.

Thank you very much for your efforts, Jo

 

Hi Jo
I tried the BR442 using the original PieHid64.dll and the Raildriver had the same problem
Thanks to SGTDRE further research show a fix you can install from here
https://www.trainsimcommunity.com/mods/c3-train-sim-world/c109-other/i3790-db-raildriver-remapping

Make sure you download the TSW4 versions
MOD_TSW4_KAH_DB_BR442_RailDriver.PAK

See the instructions further down the page, to see where to place them
I have tried them with the BR422 and the lever reports 0% when in the mid position
Chris

 

Can this software be used to custom assign the 28 programmable keys on the Raildriver?

Also, I'd like to hack the Raildriver so the dynamic brake and throttle are on separate levers as is prototypical for 2nd gen North American diesels (e.g., EMD SD40-2). If it is not possible to due to the sharing of internal sensors (I don't have Raildriver yet to know if it is yet), is it possible to use Raildriver for almost everything and then assign just the seperated dynamic brake or throttle lever to an Arduino and use both simultaneously for full control?

 

Yes it can. By editing the Button Map you can assign any button on any Joystick/Raildriver to any in game function that has a keyboard key or key combination allocated to it.

Again, you can assign any lever on any Joystick/Raildriver to any function you wish including separate Dynamic & Throttle on different controllers and they can all be used simultaneously. You can also create your own Joystick using a Arduino and the Joystick Library.
Chris

 

Thank-you for clarifying Chris and for your work making this software possible!

 

Chris,

I downloaded 2.0.0.7 from the link above and can attest that the headlight switch works as expected. (All of the previous versions did not work late.) The wiper switch is still buggy.

I've noticed a few things you may be aware of, but I don't know.

1. In the "Data Sent to TSW" field, I can see updated values for all of the controls except for "Wipers" and "Lights." So, there must be some difference in how these are hooked up in your program compared to the other levers.

2. Since installing the interface (I think), I have noticed a problem with the Horn Sequencer in the EMD F125 Metrolink. The issue is that the Horn Sequencer will not sound the horn when it's button is pressed, either using the interface, or pressing the button within the cab. Today, I noticed that when I use the horn lever to enable the sequencer, the button in the cab is pressed, but not released. Pressing the button in the cab doesn't have that behavior.

The funny thing is that the horn sequencer sometimes eventually sounds, but not until several minutes after pressing the button. It may be Raildriver that's causing this. I started using your interface almost as soon as I started using Raildriver, so I'm unsure if this issue started before or after installing your software.

It's almost as if something is causing the feature to hang, and then it gets unstuck a while later to sound the sequence.

Do you have any idea what might cause this?

-- Edit: I tried replacing the old Piehid.dll and restarting TSW4 to see if the DLL made a difference with the Horn Sequencer. It did not change. The only thing I'm not sure about is if some configuration change has caused the problem.

 

I have worked out some things on my system, and I have TSW4 working nicely with your Raildriver and Joystick Interface. Other than the wiper switch and an issue with the throttle, it all works sweetly. I might be able to work out my throttle issues with notches, but I'm unfamiliar with them. So, I need to do a little study on that. I'll be digging through the docs tonight to learn more about that.

Thanks, Chris, for writing this program. It's something Dovetail should do themselves, for it makes their program a lot better when used with the Raildriver, and as they have set it up, Raildriver just isn't very useful.

I'm now watching the site closely for the wiper switch fix. ;-)

 

Hi Jack
Your wish is my command, I have uploaded a new v2.0.0.7 with, hopefully the wiper & lights now fixed (they work ok for me) you can download it from here again and overwrite your previous version
https://www.dropbox.com/scl/fi/aps5...ey=z50mihv5x2bybbnovw1lp433p&st=bcchzvcc&dl=1

With regards the Horn Sequencer, are you aware that it will not come into effect until you are doing 45 mph I believe.
Chris

 

I am now, but it took some work to understand. But it works after a sort below 45. If you hit the button for the sequence below 45 mph, it doesn't sound immediately, but it does eventually sound. I think it's calculated to delay the horn from when it is activated at a whistle board so that the sound is timed with the actual crossing. I haven't verified that yet, but it worked for one crossing I made.

Thanks btw for the updated software. I'll try it out soon.

 

No joy, Chris. In this update, neither headlights nor wipers work for me in the EMD F125. When I rolled it back to the earlier 2.0.0.7 version, the headlight switch worked again.

Those switches are troublesome little things, aren't they?

 

Hi Jack
Can you try this version (2.0.0.8)
https://www.dropbox.com/scl/fi/8qh3...ey=y28j41v1002trj53n43a4n9f1&st=ppjuls9n&dl=1

You will either need to completely delete V2.0.0.7 and start again, or, copy this version over v2.0.0.7 and then delete the following 2 files before running the new version.
1. Settings\LeverSettings.xml
2. KeyMaps\Master Levers\LeverSettings.xml

Then, when you run the new version, it will tell you that the program has been updated, and it will automatically close itself.
On the next run, the wipers and lights should now be working.
Chris

 

Chris, version 2.0.0.8 works well, but I have a question or two. Both switches are working correctly! Thank you.

First question: Is there a way to have a different button map load up by default when the program starts? I created "MyDefault_ButtonMapper.xml" to set the Raildriver buttons for the EMD F125, but I must load it manually each time I start your program. My lever map, called "EMDF125," loads up automatically each time, but I haven't found a way to get the button map to load automatically.

Second question: Could your program produce this behavior WRT the horn sequencer? I have the horn lever to click the horn sequencer button when the lever is moved down. At an early point of a run, it seems to work to start the sequence, but after a run from LA to Glendale, it stops working. Moving the lever down doesn't even produce the button click sound in the cab, and this happens whether or not I'm going over 45 mph.

 

Jack
1. You can assign the currently loaded button map to a loco by going to the menu KeyMaps\Button Map\Assign To Loco's This will bring up a window with all your lever maps. Simply select one or more loco's you wish to assign the button map to. Next time you run the program and select one of those loco's the assigned button map will be loaded automatically.
2. I don't think that is a problem with my program, I have just had TSW sat running a session for 90 minutes and the horn sequencer button still worked OK. If it happens again, can you try pressing both Ctrl and the Space Bar together to see if the button works, if it doesn't, then it's not my program.
Chris

 

Thank you, Chris. I thought I saw a way to associate the two maps, but I couldn't find it alone.

You are likely right about the horn sequencer. TSW4 seems to do some funny things like that now and then. The alerter buzzer stopped sounding for me again yesterday. When that happens in the F125, I only know the alert is "sounding" when I see the yellow light in the HUD. There isn't anything else in the cab that shows up right now.

 

I think I figured out why the horn sequencer wasn't working correctly. It had to do with a dumb mistake on my part.

Before I found Chris' TSW interface, I installed MacroWorks from PI Engineering. This program loads automatically when the computer starts, so it was running in the background all the time.

I suspect it was sending keystrokes to TSW4 at the same time that Chris' program was, and with the Horn Sequencer, the sequencer button was sometimes getting stuck in the down position. When that happens, you cannot sound the horn again from Raildriver, though you can clear the error by clicking the button in the cab.

I don't know, but this might have been causing some of the problems with the headlights and wiper switches. Sorry, Chris, if my goof caused you unnecessary work.

Getting rid of MacroWorks should resolve the horn sequencer problem, if not a few others.

 

I should have thought about Macroworks myself, as with my TS Classic version, I always advised removal of Macroworks as it did indeed compete with my program.
The problem with the wipers was my fault, I had them named as wiper and not wipers in the lever maps, so they were not being picked up when you moved the switch. We both made a goof
Chris

 

Hi Chris, I downloaded v2.0.0.8 and now the light switch is activating the wipers on the class 801. It even shows in "data sent to TSW" that the wipers value is changing when I turn the lights switch. I deleted those two "LeverSettings.xml" files and then ran v2.0.0.8 and it doesn't fix the issue.

I rolled back to version 2.0.0.7 and then to 2.0.0.6. I got it to recognize the light switch, but then it would no longer recognize the wiper switch at all. This was the case with both TSW4 and TSW3.

I finally rolled-back to v2.0.0.2 and the lights and wipers switches finally worked for both TSW3 and TSW4 again. (I never downloaded versions 2.0.0.3-5, so I couldn't test those.)

 

I can confirm on my side that assigning a control to the wipers activates the light switch in TSW. Assigning a lever to the light switch doesn't do anything. (Win10, v2.0.0.8)

 

Conductor B Isaak
Can you, and anyone else experiencing the problem with the wipers controlling the lights, redownload V2.0.0.8 and try again.

 

This seems to be an issue with the game as a whole, I understand this info I posted here has nothing to do with the Program that you created CobraOne I spent about a month or so checking, and this and it did filter/transfer/migrate down to TSW2 & 3, this leads me to believe that TSW2,3,4 share the same file(s) for the advanced control settings within the game. Also, this was never an issue in TSW2 & 3 nor was it an issue with TSW4, well until several updates/Patches were pushed out for TSW4 after release, and the last update which was pushed out for TSW3.
If Isaak is reporting lights and wipers switch crisscross where one activates the other, I'm no coder or scriptwriter, but it would seem that info is being pulled from within the game, so as to cause one switch to do multiple actions. If that even made sense.

 

Hi SGTDRE
I have just watched your video and tried the AC4400CW, Class 801 and the Class 323 and the horn works fine on all 3 without affecting the lights.
It may be that you have the Horn Down assigned to the lights in your button map as well as the horn.
Open the menu option 'KeyMaps\Button Maps\Edit Button Map' and look for the HornDown, make sure it looks like this.

Look through the whole button map to see if you also Have HornDown assigned to anything else, if so, delete the assignment by right clicking on it and selecting Delete Currently Assigned Button/Lever.
Chris

 

I believe there is a misunderstanding, I thank you for taking the time to look at the video, and If my post here led you to believe, I was using your program, I do apologize, the video was about the rail driver and the in-game calibration for the advanced controls - rail driver. While I do have macroworks 3.1 installed it is used for other Train sim games. I changed nothing for TSW__ and I do not use macroworks for either TSW game.
I do have your program but I did not install it, I thought that just maybe the info that is being read? from the in-game calibration could be a cause.

 

It works, thank you Chris!

 

Hi Chris,
Is it possible for your interface to show MFD data on separate monitors? Like on the GE AC4400 or newer locomotives.
Possibly using Adrino.

 

As TSW stands at the moment, no, but look at post #303 and #306 on page 7.

 

With this API would you be able to get access to the MFD data?

 

I can't answer that as no details have been released.

 

Hi
Will this current version be compatible with TSW5?

 

I’ve copied it (the interface folder, pie….dll and the raildriver.ini to the appropriate places) to tsw5 so far it’s working fine.

 

Can anyone give me (a RailDriver newb) a summary of the benefit of using this software over the in-game calibration in TSW5? Much appreciated and thanks!

 

Not sure what i've done wrong then, copied the dll to tsw5 and made sure there was the raildriver.ini but all im getting is "Unable to connect to TSW".

 

Did you copy the pie dll into the binaries folder (rename the original first maybe)?

 

yeah, I copied PIEHid64Net.dll into the binaries folder which i believe is the correct file. When you say rename the original do you mean change the name of the PieHid64.dll thats already in there?

 

Welp was just my own stupidity haha, was using the wrong file, copied the dll from the default settings folder and now it works. Get what you mean by rename the original. Thanks for your help!

 

You're not the first to do that, glad it’s sorted! Yeah, I tend to rename and keep just in case things dont work.