Hi Chris,
I am currently setting up Michael Schmids lab in Fribourg.
Here, we are using the ISCAN system in combination with mworks. Following instructions I found here ISCAN Device — MWorks 0.12.dev documentation
I managed to connect the ISCAN computer with the mworks computer (mini mac) without any complaints.
I am now trying to run a calibration file (xml, see attached) while the ISCAN software is running (see image attached). Basically I decided to go for output_01 and output_02 in ISCANs auxiliary output controls and try to import them using the the ISCAN IO Device in mworks.
Unfortunately, mworks does not show the eye traces or run the file (even with an eye window of 100000000) and seems to be crashing while the calibration file is running, which results in me having to restart he mini mac as the mwserver is unresponsive up to the point that I cannot even force quit it.
Do you by any chance have a running xml file resolving the issue I mentioned or can fix the attached one?
Thanks for your help with this,
Marcus
Hi Marcus,
I don’t see any issues with your XML file. In the ISCAN software, I see that you’ve correctly selected a binary format for the auxiliary outputs.
It sounds like MWServer is freezing, not crashing. Is that correct? If so, then I suspect it’s blocked trying to read from the serial port, which suggests that ISCAN isn’t sending data.
Have you tried using the alternate start/stop codes mentioned in the docs? As I recall, the only ISCAN manual I could find listed those values (132 and 136) as the correct ones. However, the one and only ISCAN device I’ve tested on expected 128 and 129, which is why those are the defaults.
Cheers,
Chris
Hi Chris,
yes, you`re right. MWServer is freezing, so I have to restart the PC.
I now also tried the alternate command bytes 132 and 136, which unfortunately resulted in the same issue.
Is there an easy way to read out the correct start and stop signal as provided by the ISCAN PC (windows 7).
Thanks for your help with this,
Marcus
Hi Marcus,
Is there an easy way to read out the correct start and stop signal as provided by the ISCAN PC (windows 7).
I’m not aware of any. I got the 128/129 values from the user who asked me to implement MWorks’ ISCAN interface. I don’t know where he got them.
Have you tried contacting ISCAN? Presumably someone there could tell you.
Chris
Hi Marcus,
Have you managed to resolve this issue? Were you able to find start/stop codes that worked for your ISCAN device?
Cheers,
Chris
Hi Chris,
Thanks for asking. For now we decided to proceed by connecting the iscan pc with the minimac using an ni card. Since this is not the most elegant solution we eventually will try to get the connection going via serial to usb. At the moment the most likely reason for the failure was that we did not use a null modem cable for the connection.
I’ll keep you posted.
Thanks,
Marcus
Hi Marcus,
Thanks for the update. FYI, I used a FTDI US232R-100 cable to connect the ISCAN PC to the Mac running MWorks.
Chris
