Port Com7 error with EMXP3.05.5 under Wine 1.8-rc4 Mac

[am.syn]

Hello to the Forum
I try to open the Port Com7 with EMXP under Wine OS X.
I set the Port via Terminal in OS X and it seems this port was set proper.
When i try to set the prefs in EMXP i get this error:
Port Com7
can`t be used because it can be opened.
Error 978
COM port 7 can be opened. Reasoncode is 2.

Here is the OS X terminal verification:
Mac-Mini:~ Jan$ ls /dev/tty.*
/dev/tty.Bluetooth-Modem   /dev/tty.Bluetooth-Serial-2
/dev/tty.Bluetooth-PDA-Sync   /dev/tty.JansiPhone-WirelessiAP
/dev/tty.Bluetooth-Serial-1   /dev/tty.usbmodem1441
Mac-Mini:~ Jan$ cd "Wine Files"
Mac-Mini:Wine Files Jan$ cd dosdevices
Mac-Mini:dosdevices Jan$ ls
c:   com7      d::      z:
Mac-Mini:dosdevices Jan$ ln -s /dev/tty.usbmodem1421 com7
ln: com7: File exists
Mac-Mini:dosdevices Jan$

My Emuser has the latest Firmware installed. My OS Version OS X 10.8.5
I hope there is any advice for me ....
Thanks in advance

[esynthesist]

From the terminal output I assume that the EmuSer is device /dev/tty.usbmodem1441
Are you sure com7 is linked to that device ?
(in your example com7 seems already to be defined, and when you try to link com7 again, you try to link it to /dev/tty.usbmodem1421 instead of /dev/tty.usbmodem1441)
You can enter the "ls -l" command to see to which device com7 is currently linked.
If it's linked to another device already, just use another com port number for the EmuSer.
If it's linked to the wrong device, remove the link and re-assign com7 to the correct device.

[am.syn]

This is what i get back with ls - l :
Mac-Mini:dosdevices Jan$ ls -l
total 32
lrwxr-xr-x  1 Jan  staff  10 13 Jun 16:56 c: -> ../drive_c
lrwxr-xr-x  1 Jan  staff  21 14 Jun 14:11 com7 -> /dev/tty.usbmodem1421
lrwxr-xr-x  1 Jan  staff  13 13 Jun 16:56 d:: -> /dev/rdisk1s1
lrwxr-xr-x  1 Jan  staff   1 13 Jun 16:56 z: -> /
Mac-Mini:dosdevices Jan$

This looks ok for me.

[esynthesist]

I'm not sure that's OK.

It depends on the device name that OS X has assigned to the EmuSer.
You currently have linked com7 to device /dev/tty.usbmodem1421, as shown in the output of the "ls -l" command.

But according to your initial post, the EmuSer is device /dev/tty.usbmodem1441, not device /dev/tty.usbmodem1421
(see the output of the ls /dev/tty.* command you have entered previously... unless you have mistyped something in that original post of course ;-)

If the EmuSer is /dev/tty.usbmodem1441 and not /dev/tty.usbmodem1421, you have to remove the current link of com7 and re-assign it with following 2 commands:

unlink com7
ln -s /dev/tty.usbmodem1441 com7

[am.syn]

Great!!!!
Tricky thing that
Now it works.
Many, many thanks esynthesist

[am.syn]

Cool, the com port is working now, but if i try to send or receive data from the Emax1 or Emulator2 then i get this error:
Errorcode 1752
Reasoncode 2-1-980-0

The Emax1 and the E2 are going into the transfer or receive mode and then they are stuck.
If i use EMXP on a Laptop with Windows7 it works.
If i use the SMAX or E2 software on Mac it works too.
I dont think that is a RS-422 problem.
Maybe there are some incorrect values in my EMXP preferences.

[esynthesist]

This error indicates that the "Wine/Mac serial driver" does not accept the baudrate requested by EMXP.
That's quite strange because EMXP version 3.05 has specific support for POSIX compliant baud rates. These baud rates are required by Wine on Mac OS X, and are used in combination with the newest firmware version for the EmuSer which can operate in POSIX compliant mode now as well.
Moreover, EMXP should use these baud rates automatically/by default when using EMXP in Wine for the first time.

The most obvious cause of error 1752 would be that the "external clock" baud rate in the EMXP communication preferences for Emulator-II and for Emax-I has been changed and has been set to a non-POSIX value.
The default setting (if you didn't change anything) is 50 baud and should work fine. But if it has been changed to another values, e.g. 500000, then you get error 1752.

Could you check the External Clock baud rate value by going into EMXP menu option 6.5.1 (for Emulator-II) and 6.5.2 (for Emax-I) and checking setting 4 (=baud rate for setting ext.clock (Posix/Wine mode) ?
It should be 50.

If that's indeed the value in your EMXP setup, then could you:
- go to EMXP menu option 6.8.2 to see if EMXP has detected that it's running under Wine ?
- go to EMXP menu option 6.5.8.4 to see if EMXP is using the Posix serial settings (option 2 or 3 should be selected)

But again, if you simply have downloaded EMXP and started using it under Wine on Mac OS X without having changed any preference in EMXP, it should work fine. Otherwise it would be too complicated for everyone :-)

Note however that I have tested EMXP on Mac OS X El Capitan 10.11.1 and 10.11.4, but not on Mac OS X 10.8.5.
I hope that version also accepts *all* POSIX compliant baud rates, including 50 and 38400... If not, we'll have to check which  alternative value can be used instead of 50.

[am.syn]

Thanks for reply
I check this options, but nothing work in the moment.
EMXP detect Wine.
If i try higher baud rates ( 38400 ) then the Emax1 give this message back:
Abortet-bad ACK for Header

And EMXP:
Errorcode 1085

Then i try lower rates but without effect. The Emax goes int Transfer/receive mode but no data transfer starts.

Maybe it`s an OS X 10.8.5 feature

[esynthesist]

The firmware of the EmuSer only switches to external clocking with baud rates 50 or 500000.
So it's perfectly normal dat e.g. 38400 for external clocking does not work, and that you get another error.

What error do you get if you use a Posix/Wine baud rate for the external clock of 150 instead of 50 ? 
Do you get the 1752 error or the 1085 error ?
And what if you use 75 instead of 50 ?

If you get the 1085 error but not the 1752 error, it means there's a specific issue with the value of 50 on Mac OS X 10.8
In that case I will send you a new firmware version for the EmuSer, just for doing a test.
And if that test will be successful, I will release a new version of EMXP and the new firmware which solves the problem ;-)

[am.syn]

At baud rate 150 i get the error 1085 and Emax:
Abortet-bad ACK for Header

At baud rate 75 i get Error 1046

Maybe a new firmware fix that problem
best form Hamburg

[esynthesist]

OK thanks.
I have sent you a PM with a new test version of the firmware.

[petrm2007]

Hi, could you please let us know the test results? Thank you.

[esynthesist]

We're still working on this.
For some reason the EmuSer seems to not switch to the external clock, so I'm trying to find a solution.