Beiträge von gazz292

ahhh, it makes sense to me now, saves having to start omsi a million times whilst making changes to get a script running.

The kind of thing i am looking for is a way to read what variables omsi is executing when the mouse is clicked on an item, i.e. if i click on one of the tickets on the pay table, it can tell me what the [mouseevent]' trigger name is, and i can try and make a script that can trigger that mouseevent with a key bind trigger.

Or try and find a way to read variables that omsi does not let you have access to, like the red information text that displays what ticket the passenger wants, how much it costs and how much money they have given you.

But as you can guess, coding is something i really struggle with, which is why i love the idea of your omsi script generator.

thankyou for taking the time to explain the script console to me.

I am really bad with command line type stuff, so i'm not sure how to use the Script Console,

would it be possible to use it whilst Omsi is running, and read out things like the variable names / triggers for 'Mouseevents' ?

or have i got the wrong idea of what this program can do.

Wow, the Omsi script generator looks amazing, just the kind of thing someone like me needs, i really struggle with coding, so having something that can show me how to write the code properly will be a massive help.

yeah, but i don't get replies to emails, and his site has stuff stopping middle of 2020 it seems, i bought quite a few things off him in past years, and sent all english people who asked where to get german bus parts for simulators to him,

Glad you got it sorted, it is a special kind of switch because you have to pull it upwards to allow it to then be moved into position,

Has anyone bought anything from Homburg's scrapyard recently? he's not replying to emails, and the site dosent seem to have been updated for a while (16% vat and that which has changed )

Can you take a photo of the switch?

the bus stop brake switch on my dashboard is a pull switch, and the knob just unscrews, and a nut underneath it is then removed, but different dashboards have different stitch types,

i think the 20H brake switch is a strange one to remove too due to how it works.

Rather than use someone elses thread (sorry) i have started my own about using Komsi with a mas3 style ibis: Here

It's a shame that Komsi isn't being developed any more,

i totally understand tho, omsi is no longer being developed, komsi works as it is, and Lars is busy developing his new software that will work with Lotus,

plus everyone want's 'just one more feature' added to it, and some people are not appreciative of just how much hard work goes into programming something like komsi.

I had a little play with the komsi OPL file, changing one of the ibis entries to 'IBIS' and it called that function and sent the 2 line Ibis data to my LCD!!! with the @symbol,
i was just running a simple serial to lcd sketch, so it was showing everything in raw format, and the 2 lines of IBIS data were in the middle of the komsi data,

So it might be possible to get komsi to output the IBIS lcd data by writing an arduino script to just read where the 2 lines of ibis data is injected into the komsi serial output, and ignore the other stuff,

I can't seem to find the end line character on the komsi ibis output tho, the ticket printer output is ';' but it's almost like the new line character isnt used for the komsi ibis output.... i can manually add it to where the bus temperature would be,
tho i have seen some people using komsi and it is outputting the bus temperature,

i downloaded komsi 2.4... it's only the server that is 2.4, the part that runs with omai seems to be 2.3 still.... so i get 'noch nicht mit Leben gefüllt' printed where the temperature should be.

In komsi there are 5 outputs in the OPL creator that you can not change, those are for output numbers 47, 49, 50, 51 and 53.

Those outputs are always

47 : bus stop brake light

49 : door_0

50 : door_2

51 : door_4

53 : cockpit_light_tuerkontrolle

so output 53 is the green light found on mercedes buses that comes on when you can drive off,

and 49, 50 and 51 will show when a door is open,

door_0 being the first wing of the front doors,

door_2 is the rear doors on a bus with 2 sets of doors, or the middle doors on a 3 door bus,

door_4 is the 3rd set of doors on buses which have them,

I believe Lars coded the green 'ready to drive' light in komsi, so even if you are driving a MAN bus that dosent have that light, you will still get that feature on your mercedes dashboard,
As i drive a MAN bus, i've never had output 53 : 'cockpit_light_tuerkontrolle' connected to anything.

I think i have got this right, if not hopefully Lars will see this and correct me.

Ahh cool, the resistor ladder for multiple button input is clever, that's how they do it in cars for things like the steering wheel controls, loads of buttons but only 1 wire needed for them all, i never thought to do that with an Arduino tho.

i wish i was able to do this programming lark, i can do little bits with lots of guidance, but the amount of features things like komsi has in it are way beyond my capabilities,

I'm trying to get the komsi printer sketch working, which uses a 40 x 2 line lcd, and should display ticket printer and ibis text, i even bought an arduino due, but it just doesn't work for me, wont receive any data, i think it's to do with the terminating character, which is ; on the ticket printers output, but not sure what it is on the IBIS only output.

So i have got just the LCD part of that arduino sketch running on an arduino uno, and i have it kinda working, but it'll never display everything that's on the in came IBIS... i wonder if that 'stringvariable IBIS' was added after the final komsi release.

Seem's with komsi, there's V2.4 of the server that connects to the arduino's, but only v2.3 of the actual program that runs with omsi and gets the data out, hence there's no in bus temperature active, and no interior display active,
maybe i am missing the 2.4 version of the actual komsi program,

I had my main arduino mega lock up and need resetting after about 20 minutes of driving,the one that runs my dashboard, i have a feeling the arduino is running out of memory, and i need to add a command to clear the memory, as i've had this with the uno im playing with to get IBIS data, if i add the code to send debugging data to the serial console, i get about 5 minutes before its filled it's memory up and crashes.

Ahhh, so komsi would need updating to read the string 'IBIS', i think, i am not sure exactly what komsi reads for the ibis, but the data it sends out is loads of separate bits of data.

Or i need to find another program just for the ibis maybe? unfortunatley i am useless at programming,

What is running your ibis there?

That IBIS you have looks great, i printed the graphic of the ibis in omsi out once and laminated it, i was going to put switches behind the buttons and a 24 x 2 line lcd, but i managed to buy a real mas 3 ibis,

i have yet to take it apart to interface it with omsi.

About 460mm from the flat floor to the base of the dashboard... that's the height it is in omsi, and it seems to be around the height i want the dashboard on my drivers workplace i am building.

can you post a photo of the connections to the spedometer,

you may have to take the back off the spedometer and show us the markings on the pcb,

What features do you want that komsi does not provide?

I am playing with LCD's for the IBIS display, and notice that it doesn't display the 'falsche route / ziel' or things like that, BUT i believe that is because omsi does not give that data out, so the data for the IBIS display has to be made up by reading about 12 seperate pieces of data from omsi, there is no simple 'output what is showing on the isis display in the simulator' function it seems

What input does the spedometer need?


It might be a stepper motor type, or could be controlled by a can bus system,

The speedometer / tachographs used on the earlier buses just needed a pulsed input to drive it, which is a tone signal from the arduino,

'lights_warnblinkgeber' works for me,

How do you mean height?

Of the actualVÖV dashboard itself, as it's taller at the back than the front,

Or the height the dashboard sits above the floor in a bus? (about knee height)

I have a VöV dashboard here i can measure for you if that's what you need to know,