Might be stating the obvious but have you tried using the [hi] object? Sometimes it works anyway for devices without the protocol, often with strange results which require conversion.
Depending on what platform you are on, the operating system should look for devices and their drivers when plugged in, as you may be able to get one from the product's website, then do some tweaking to get it to work.
I opened the serial help patch and here is the result:
for "print" message, serial object return -
"port c: COM3"
I put the argument "c" to serial for receiving messages, but there are no data after bang and the only result is from right output (Status Signal):
Maybe its important to know that spectrometer is don't send data when you plug it in USB port. You have put button "start" in spectrometer software and after the spectrometer is sending data. it is possible that spetromeer software receive data form USB port but Max doesn't?
It's hard to guess what's going on. Many devices register themselves as a virtual COM port when plugged in. At that point, any app could have two-way communication with the port. But, it seems like this device is doing something more unusual. I'm not sure they were designing with third party software in mind.
I think it's beyond my expertise to reverse engineer their communication protocol. I'd try to get some clues from the manufacturer. I think I found it online, but the website doesn't offer much.