Thanks! I was just thinking of all the other programs out there like SDR's and other scanner programs. I for one follow the rolling log because I'm sitting here with my fat butt right in front of the equipment and computer! (hahaha)
Scanner Screen software for 436 and 536
- Thread starter Vonskie
- Start date
- Status
Thanks! I was just thinking of all the other programs out there like SDR's and other scanner programs. I for one follow the rolling log because I'm sitting here with my fat butt right in front of the equipment and computer! (hahaha)
When you click the devices drop down it will give you a list of all /dev/tty.* ports it finds. Normally it will say /dev/tty.usb something.
To get a list of all ports you can go to the console and type ls /dev/tty.*
Hope that helps
Should change it to /dev/cu.* instead.. Won't get confused with the ttyp terminals..
Sent from my iPhone using Tapatalk
What is cu?
http://stackoverflow.com/questions/8632586/macos-whats-the-difference-between-dev-tty-and-dev-cu
Sent from my iPhone using Tapatalk
Sent from my iPhone using Tapatalk
You might notice that each serial device shows up twice in /dev, once as a tty.* and once as a cu.*. So, what's the difference? Well, TTY devices are for calling into UNIX systems, whereas CU (Call-Up) devices are for calling out from them (eg, modems). We want to call-out from our Mac, so /dev/cu.* is the correct device to use.
The technical difference is that /dev/tty.* devices will wait (or listen) for DCD (data-carrier-detect), eg, someone calling in, before responding. /dev/cu.* devices do not assert DCD, so they will always connect (respond or succeed) immediately.
i will test the program with cu and see what happens.
The technical difference is that /dev/tty.* devices will wait (or listen) for DCD (data-carrier-detect), eg, someone calling in, before responding. /dev/cu.* devices do not assert DCD, so they will always connect (respond or succeed) immediately.
i will test the program with cu and see what happens.
New version .55 MAC CU uses the CU devices thanks for the tip salvation
Took this version off line so I could test it first.
Have not tested it yet let me know if it works or not if not just use the 54 version above.
Happy Scanning!
Took this version off line so I could test it first.
Have not tested it yet let me know if it works or not if not just use the 54 version above.
Happy Scanning!
Last edited:
Please test CU version 55 and let me know.
New version .56MACCU
Uses the CU devices
https://drive.google.com/file/d/0B_Jndzk4GdzJRURIZ0l1TTU3NVU/edit?usp=sharing
Please test.
Uses the CU devices
https://drive.google.com/file/d/0B_Jndzk4GdzJRURIZ0l1TTU3NVU/edit?usp=sharing
Please test.
So, future versions are going to be Mac only?
No there will be both the code is mostly portable. So changes in one can be moved to the other. Mac is the new one right now so it's getting the attention trying to get it optimized.
Only two things come up in the drop down something DEV/modem and something Dev/bluetooth something or other. ???
Ever think of having the program do a probe to find the scanner? Just connect to each port and do an MDL and make sure it returns whatever models you are supporting and then autopick it. I would still leave an option to select a different port if needed
Sent from my iPhone using Tapatalk
New Version .57MAC CU
Cleaned up some code.
https://drive.google.com/file/d/0B_Jndzk4GdzJdFVUci1sSVU2UEk/edit?usp=sharing
Cleaned up some code.
https://drive.google.com/file/d/0B_Jndzk4GdzJdFVUci1sSVU2UEk/edit?usp=sharing
LIScanner101
Completely Banned for the Greater Good
FreeSCAN works that way. When you connect your scanner to your PC and have FreeSCAN open and want to upload a file, you can query the COM port and when it finds your scanner it tells you what kind you have.
If your not getting a USB modem to show up for some reason your mac is not reading the serial port is it possible that parallels has taken control of it or maybe you need to restart you scanner
Not sure
kd7eir
Member
Working fine on Mavericks 10.9.2 My scanner showed up as /dev/cu.usbmodem14511
- Status
