Hi all!

In order to enable me to run locomotives from the Mac, I intended to write a small program to listen for messages from the CS2, or at least to use an existing program such as he WinDigiPet to work. I am using a Mac, and the firewall is set up to allow incoming messages.

The connection between the mac and the CS2 works per se, I can connect to the CS2 using the broswer, to take screen shots.



The Central Station 2 is Software version 1.5.2(1) and HW version 3.4, as cen been seen from the following screen shot:



In this later version the set up for IP has changed slightly from previous versions.
It has a
IP address (I understand this)
IP Network Template (I understand this)
IP Gateway (As far as I remember, this used to state Start Gateway, and the purpose was to enable CS2 to broadcast messages, and not only listen), however I do no know what this should be now... Also the DNS Server, when should it be used, and how?



The CAN configuration I assume I have done correctly, but so far I did not manage the computer to receive any messages.



I tried to use WinDiPet demo version through Parallels on the Mac, but I did not get it to work, it claimed the CS2 was not correctly set up. Any ideas on what I need to change on the CS2 side?

Regards

Skjalg

Have you tried with the firewall turned off?

Yes, the firewall was turned off (under OSX), but under Windows it was on, turning it off did not make a difference. As for WinDigiPet, I realized that when runnin Windows on the Mac, it gets its own IP address on a different subnet.
C:\Program Files\Microsoft Visual Studio 10.0\VC>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.211.55.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.211.55.1

C:\Program Files\Microsoft Visual Studio 10.0\VC>

On the same physical machine, but under OSX I get IP address 10.0.1.9:


> ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::223:32ff:fea0:a67e%en0 prefixlen 64 scopeid 0x4
inet 10.0.1.9 netmask 0xffffff00 broadcast 10.0.1.255
ether 00:23:32:a0:a6:7e
media: autoselect (1000baseT <full-duplex,flow-control>) status: active
supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control> none
fw0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 4078
lladdr 00:23:32:ff:fe:2d:5b:7c
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1b:63:c1:e9:75
media: autoselect (<unknown type>) status: inactive
supported media: autoselect
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:1%en3 prefixlen 64 scopeid 0x7
inet 10.211.55.2 netmask 0xffffff00 broadcast 10.211.55.255
ether 00:1c:42:00:00:01
media: autoselect status: active
supported media: autoselect
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::21c:42ff:fe00:0%en2 prefixlen 64 scopeid 0x8
inet 10.37.129.2 netmask 0xffffff00 broadcast 10.37.129.255
ether 00:1c:42:00:00:00
media: autoselect status: active
supported media: autoselect


So if I should get WinDigiPet to work, I might need to change something...?

I have not used WinDigiPe before, and I downloaded the German version, but I will try the English version later. Either way, here is the configuration for CS2:


and here is the message I get when I start the program:

basically saying that the CS2 does not respond, and that the digital system must be re initialized (meaning configured I guess).

What Tom says, is that you should set up (if possible) the "network properties" of Parallells as a "bridging" network connection, not as a separate "Network Address Translation" (NAT) network as it seem to default to.

The CS2 broadcasts the CAN bus UDP traffic to all your 10.0.1.xxx adresses, but not to the 10.211.xxx.xxx adresses since these are not within the network scope of the broadcast. At least that's how I understand it.

Since I only know "something" about Virtual PC & VMWare, I cannot really give advice on the Parallells setup...

Since the CS2 is a Linux box, make sure you connect the cables before starting it, may seem obvious, but just in case...
This holds true for the CS1/CS1R, not sure for the CS2 since I don't have one.

Thanks Thomas, for the iTrain link. I have not seen this before, but since it is cross platform, I will certainly try it out. For my own use, it seems well suited. The reason for my efforts with the WinDigiPet is simply that it is already being used in a club where I am about to become a member, so I thought I better learn how to operate it, as well as having an informed opinion about its abilities compared to other alternatives.

_Skjalg

The windows stuff has to be on the same network address range as the Mac & CS2 as Tom and myself mentioned - Have you found any network settings in Parallells that can support that scenario?

Skjalg,

Just to confirm you installed the Mac OS version of iTrain, and you also downloaded the user manual?

You could also post on the iTrain forum about iTrain - CS2 connection.

http://berros.eu/itrain/forum/


Can you post screenshots of the iTrain connection?


r/Thomas

Have you tried to ping the CS2 from the Windows partition? If the Windows machine can't see the CS2, then WDP won't either..

Are you using WinDigiPet 2009 - earlier versions don't work with the CS2? The English Demo version is at http://www.windigipet.de/cgi-bin/download/download.pl?setup_demo_2009_e

Yes, I had.

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : ...
IP Address. . . . . . . . . . . . : 10.0.1.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.1.1

C:>ping 10.0.1.10

Pinging 10.0.1.10 with 32 bytes of data:

Reply from 10.0.1.10: bytes=32 time=1ms TTL=64
Reply from 10.0.1.10: bytes=32 time=1ms TTL=64
Reply from 10.0.1.10: bytes=32 time=2ms TTL=64
Reply from 10.0.1.10: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms

OK, so time for a little update.

I downgraded my version of the CS2 software, using the USB stick approach.



I did the setup of the Network:



I then started up the iTrain software running under the Mac OSX, and as can be observed on the below image, this gave a better result.



The Go and Stop button works, but so far I did not manage to control the locomotive, but I have only tried a few minutes so far. Maybe time to read the documentation... I will also try the WinDigiPet software, and give you an update later (not sure if I manage today).

But based on my findings thus far, stay with the 1.4 USB upgrade if you want to control your trains from software.

_Skjalg

Interesting, even though I dont have neither a Mac nor a CS2

Skjalg,

glad to see you got it all working, thanks for the pictures.


r/Thomas