Advanced Search

You can download the support software from Mesa's web store
(specification tab)
 

I apologize, this is my fault, some production 7C80 cards ended up with
the wrong firmware. We can issue you a RMA for reflashing the card with
correct firmware. Sorry for the inconvenience.
 

OK the original attempts were with the official raspbian image. The supplied kernel is not one suitable for Realtime in the way Linuxcnc requires a realtime kernel. There was discussion a few months ago reagrding real time being included in the mainline Linux kernels. When building a real time kernel there are 3 options from memory, if you do not choose the correct type it is not what Linuxcnc expects.
It would depend whether the kernel was pinned (excluded from updates or not) but on further reflection the Raspbian kernel is different to the mainline debian kernel for arm boards.
And honestly when you do an update you should have a look at what is being updated. before proceding.
With the Linuxcnc image did you enable the SPI interfaces in config.txt ?
If you had of clearly stated at the beginning you were using a raspbian image to begin with it would have made life a whole lot easier. It would have been suggested to use the Linuxcnc image from the get go.

Just went back on this, you asked mesaflash to verify is the board has the pwm version and it does not, hence the result.
You would need to flash the board first with the firmware you need, and the files are on the Mesa web page
www.mesanet.com/software/parallel/7i96s.zip

Ah, sorry, my bad. I misinterpreted the options. Exchanged 'verify' with 'write' and it worked like a charm.
Correct version:

mesaflash --addr 192.168.1.121 --device ETHER --write 7i96s_2pwmd.bin

Also, thanks for pointing the location of the support package out. This website looks like they went bust 20 years ago...

It might have been nicer if the max travel was calculated based on the length to probe.
ie probe length = 10, max _over_ travel = 5 then anything that moved 15 would trip.

blazini36 wrote:

Yeah Tommy is pretty much correct in the fact that 1.5Mbaud does not equal 1.5Mbit because there are wasted bits.....start, stop, parity, address, etc
 

That will affect the overall byte rate, not the overall bit rate. If fact Tommy's definition made no mention of of protocols, which stop-start-parity etc would be part of.
When designing hardware for the transmission of serial data any control bits or bytes don't come into the equation.

pushed to master:

myHud.display_on_right()

Leme know if there is any problem.

In a purely digital system, one voltage equaling zero (0v) and another voltage equaling 1 (5v) baud rate with be the same as bit rate. It's when they start using voltage levels other than 0v & 5v, as given as the values (this includes single end voltage converted to differential voltages), that the difference starts happening. This is for simple serial comms, have not studied how manchester encoding for example would affect this.

I noticed your definition seems to be google's AI definition.

Yeah Tommy is pretty much correct in the fact that 1.5Mbaud does not equal 1.5Mbit because there are wasted bits.....start, stop, parity, address, etc

Cant do this anymore bye all wrote:

Something is amiss as the kernel is about 11 months newer than the image you linked to.
Now to clear things up.
1: have all your attempts been with the image you linked to.
2: if so what is causing the discrepancy with the kernel build date.

With the previous driver the kernel driver that was loaded on boot was unloaded by the Linuxcnc driver. I’m not entirely sure if it reloaded on exit.

Everything prior to today, was with the official Raspbian image.

Started with a fresh SD Card for the Debian image linked above today.
Would running system updates have messed with the kernel version?

OK, then usually this is due to old version of mesaflash, see this for latest version
forum.linuxcnc.org/27-driver-boards/5489...-see-the-card#317821

Edit:
Just went back on this, you asked mesaflash to verify is the board has the pwm version and it does not, hence the result.
You would need to flash the board first with the firmware you need, and the files are on the Mesa web page
www.mesanet.com/software/parallel/7i96s.zip

Something is amiss as the kernel is about 11 months newer than the image you linked to.
Now to clear things up.
1: have all your attempts been with the image you linked to.
2: if so what is causing the discrepancy with the kernel build date.

With the previous driver the kernel driver that was loaded on boot was unloaded by the Linuxcnc driver. I’m not entirely sure if it reloaded on exit.

Yeah a bit explained like i usually do
But still valid in both cases, baud rate is the rate of pulses/changes regardless of protocol, bit rate is what changes depending on data/protocol type and the control bits used.

Finally got the connection going. For newbie’s to Linuxcnc the leds on the 7i97t Ethernet port should be flickering while you’re pinging the ip address from the computer’s terminal. 
such a simple piece of information. 
I managed to figure out with my wifi connection ON, the Ethernet connection is dropped so simply disconnecting the WiFi connection allowed the connection with the mesa board.

Thanks vrnf 
I’ll have a look at updating mesaflash tomorrow.

Have you retrofitted your mh600w? Or still running the 432?


 

Actually tommy if you look at a serial transmission waveform the signal doesn’t change for every bit sent. If you send 0x00 or 0xFF you’ll see what l mean. Send a string of either value and it will kind of blow google’s answer out of the water.
By google’s definition baud rate will change depending on the data sent.

And if you read carefully the definition you copied and pasted baud rate is defined twice with different definitions.